1. 30 Aug, 2018 1 commit
  2. 29 Jun, 2018 2 commits
  3. 29 May, 2018 1 commit
  4. 30 Dec, 2017 1 commit
  5. 23 Jun, 2017 1 commit
  6. 11 May, 2016 1 commit
  7. 30 Nov, 2015 1 commit
  8. 31 May, 2015 1 commit
  9. 07 Nov, 2014 1 commit
  10. 29 Jan, 2014 1 commit
  11. 24 Jan, 2014 1 commit
  12. 06 Oct, 2012 1 commit
    • Thomas Kavanagh's avatar
      i2c: algo: pca: Fix chip reset function for PCA9665 · a76e7c68
      Thomas Kavanagh authored
      The parameter passed to pca9665_reset is adap->data (which is bus driver
      specific), not i2c_algp_pca_data *adap. pca9665_reset expects it to be
      i2c_algp_pca_data *adap. All other wrappers from the algo call back to
      the bus driver, which knows to handle its custom data. Only pca9665_reset
      resides inside the algorithm code and does not know how to handle a custom
      data structure. This can result in a kernel crash.
      Fix by re-factoring pca_reset() from a macro to a function handling chip
      specific code, and only call adap->reset_chip() if the chip is not PCA9665.
      Signed-off-by: default avatarThomas Kavanagh <tkavanagh@juniper.net>
      Signed-off-by: default avatarGuenter Roeck <groeck@juniper.net>
      Signed-off-by: default avatarWolfram Sang <w.sang@pengutronix.de>
  13. 14 Sep, 2012 1 commit
  14. 30 May, 2012 1 commit
  15. 26 Mar, 2012 2 commits
  16. 15 Mar, 2012 1 commit
  17. 29 Feb, 2012 1 commit
    • Daniel Vetter's avatar
      i2c: export bit-banging algo functions · b0209b39
      Daniel Vetter authored
      i915 has a hw i2c controller (gmbus) but for a bunch of stupid reasons
      we need to be able to fall back to the bit-banging algo on gpio pins.
      The current code sets up a 2nd i2c controller for the same i2c bus using
      the bit-banging algo. This has a bunch of issues, the major one being
      that userspace can directly access this fallback i2c adaptor behind
      the drivers back.
      But we need to frob a few registers before and after using fallback
      gpio bit-banging, so this horribly fails.
      The new plan is to only set up one i2c adaptor and transparently fall
      back to bit-banging by directly calling the xfer function of the bit-
      banging algo in the i2c core.
      To make that possible, export the 2 i2c algo functions.
      v2: As suggested by Jean Delvare, simply export the i2c_bit_algo
      vtable instead of the individual functions.
      Acked-by: default avatarJean Delvare <khali@linux-fr.org>
      Signed-off-by: Daniel Vetter's avatarDaniel Vetter <daniel.vetter@ffwll.ch>
  18. 23 Nov, 2011 1 commit
  19. 30 Oct, 2011 4 commits
  20. 17 Apr, 2011 1 commit
  21. 31 Mar, 2011 1 commit
  22. 10 Jan, 2011 2 commits
  23. 22 Nov, 2010 2 commits
  24. 24 Oct, 2010 2 commits
  25. 21 May, 2010 1 commit
  26. 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.
      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
      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
      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
      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>
  27. 13 Mar, 2010 1 commit
  28. 02 Mar, 2010 1 commit
  29. 05 Feb, 2010 1 commit
  30. 05 May, 2009 2 commits
    • Enrik Berkhan's avatar
      i2c-algo-pca: Let PCA9564 recover from unacked data byte (state 0x30) · 2196d1cf
      Enrik Berkhan authored
      Currently, the i2c-algo-pca driver does nothing if the chip enters state
      0x30 (Data byte in I2CDAT has been transmitted; NOT ACK has been
      received).  Thus, the i2c bus connected to the controller gets stuck
      I have seen this kind of error on a custom board in certain load
      situations most probably caused by interference or noise.
      A possible reaction is to let the controller generate a STOP condition.
      This is documented in the PCA9564 data sheet (2006-09-01) and the same
      is done for other NACK states as well.
      Further, state 0x38 isn't handled completely, either. Try to do another
      START in this case like the data sheet says. As this couldn't be tested,
      I've added a comment to try to reset the chip if the START doesn't help
      as suggested by Wolfram Sang.
      Signed-off-by: default avatarEnrik Berkhan <Enrik.Berkhan@ge.com>
      Reviewed-by: default avatarWolfram Sang <w.sang@pengutronix.de>
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
    • Dave Airlie's avatar
      i2c-algo-bit: Fix timeout test · 0cdba07b
      Dave Airlie authored
      When fetching DDC using i2c algo bit, we were often seeing timeouts
      before getting valid EDID on a retry. The VESA spec states 2ms is the
      DDC timeout, so when this translates into 1 jiffie and we are close
      to the end of the time period, it could return with a timeout less than
      Change this code to use time_after instead of time_after_eq.
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      Signed-off-by: default avatarJean Delvare <khali@linux-fr.org>
  31. 13 Apr, 2009 1 commit