An error occurred fetching the project authors.
  1. 29 Dec, 2010 2 commits
  2. 22 Nov, 2010 1 commit
  3. 22 Oct, 2010 2 commits
  4. 21 Oct, 2010 1 commit
  5. 11 Aug, 2010 1 commit
  6. 02 Aug, 2010 1 commit
  7. 19 May, 2010 2 commits
  8. 18 May, 2010 2 commits
  9. 30 Mar, 2010 1 commit
    • Tejun Heo's avatar
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo authored
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      Guess-its-ok-by: default avatarChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  10. 26 Feb, 2010 5 commits
  11. 16 Dec, 2009 3 commits
  12. 05 Dec, 2009 8 commits
  13. 26 Nov, 2009 1 commit
  14. 19 Sep, 2009 4 commits
  15. 15 Sep, 2009 1 commit
  16. 12 Sep, 2009 5 commits
    • Mauro Carvalho Chehab's avatar
      V4L/DVB (12713): em28xx: Cleanups at ir_i2c handler · 7e8e16ca
      Mauro Carvalho Chehab authored
      There are some extra parenthesis at the clauses, and some switch() tests
      for boards that don't have i2c ir. Remove those extra code.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      7e8e16ca
    • Mauro Carvalho Chehab's avatar
      V4L/DVB (12712): em28xx: properly load ir-kbd-i2c when needed · ac07bb73
      Mauro Carvalho Chehab authored
      Currently, the logic to load ir i2c ancillary module is broken. It is
      associated to Hauppauge devices with IR flag on their eeprom, no matter
      if the device uses i2c or em28xx direct IR support. That's wrong.
      
      Instead, add a flag to the boards that use i2c IR chips and load the
      module only for those devices and if ir is not disabled.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      ac07bb73
    • Mauro Carvalho Chehab's avatar
      V4L/DVB (12698): em28xx: ir-kbd-i2c init data needs a persistent object · d2ebd0f8
      Mauro Carvalho Chehab authored
      ir-kbd-i2c's ir_probe() function can be called much later (i.e. at
      ir-kbd-i2c module load), than the lifetime of a struct IR_i2c_init_data
      allocated off of the stack in cx18_i2c_new_ir() at registration time.
      Make sure we pass a pointer to a persistent IR_i2c_init_data object at
      i2c registration time.
      
      Thanks to Brian Rogers, Dustin Mitchell, Andy Walls and Jean Delvare to
      rise this question.
      
      Before this patch, if ir-kbd-i2c were probed after em28xx, trash data
      were used. After the patch, no matter what order, it is properly
      reported as tested by me:
      
      input: i2c IR (i2c IR (EM2840 Hauppaug as /class/input/input10
      ir-kbd-i2c: i2c IR (i2c IR (EM2840 Hauppaug detected at i2c-4/4-0030/ir0 [em28xx #0]
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      d2ebd0f8
    • Mauro Carvalho Chehab's avatar
      V4L/DVB (12595): common/ir: use a struct for keycode tables · 715a2233
      Mauro Carvalho Chehab authored
      Currently, V4L uses a scancode table whose index is the scancode and
      the value is the keycode. While this works, it has some drawbacks:
      
      1) It requires that the scancode to be at the range 00-7f;
      
      2) keycodes should be masked on 7 bits in order for it to work;
      
      3) due to the 7 bits approach, sometimes it is not possible to replace
      the default keyboard to another one with a different encoding rule;
      
      4) it is different than what is done with dvb-usb approach;
      
      5) it requires a typedef for it to work. This is not a recommended
      Linux CodingStyle.
      
      This patch is part of a larger series of IR changes. It basically
      replaces the IR_KEYTAB_TYPE tables by a structured table:
      struct ir_scancode {
             u16     scancode;
             u32     keycode;
      };
      
      This is very close to what dvb does. So, a further integration with DVB
      code will be easy.
      
      While we've changed the tables, for now, the IR keycode handling is still
      based on the old approach.
      
      The only notable effect is the redution of about 35% of the ir-common
      module size:
      
         text    data     bss     dec     hex filename
         6721   29208       4   35933    8c5d old/ir-common.ko
         5756   18040       4   23800    5cf8 new/ir-common.ko
      
      In thesis, we could be using above u8 for scancode, reducing even more the size
      of the module, but defining it as u16 is more convenient, since, on dvb, each
      scancode has up to 16 bits, and we currently have a few troubles with rc5, as their
      scancodes are defined with more than 8 bits.
      
      This patch itself shouldn't be doing any functional changes.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      715a2233
    • Mauro Carvalho Chehab's avatar
      V4L/DVB (12591): em28xx: Add entry for GADMEI UTV330+ and related IR keymap · 6d888a66
      Mauro Carvalho Chehab authored
      [mchehab@redhat.com: Fix a few wrong IR keymaps]
      Signed-off-by: default avatarShine Liu <shinel@foxmail.com>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      6d888a66