1. 13 5月, 2015 3 次提交
  2. 12 5月, 2015 4 次提交
    • P
      i2c: omap: Add calls for pinctrl state select · 096ea30c
      Pascal Huerst 提交于
      This adds calls to pinctrl subsystem in order to switch pin states
      on suspend/resume if you provide a "sleep" state in DT.
      
      If no "sleep" state is provided in the DT, these calls turn
      to NOPs, so we don't need error checking here.
      Signed-off-by: NPascal Huerst <pascal.huerst@gmail.com>
      Reviewed-by: NSekhar Nori <nsekhar@ti.com>
      Signed-off-by: NWolfram Sang <wsa@the-dreams.de>
      096ea30c
    • G
      i2c: Allow compile test of GPIO consumers if !GPIOLIB · 7e5cd69a
      Geert Uytterhoeven 提交于
      The GPIO subsystem provides dummy GPIO consumer functions if GPIOLIB is
      not enabled. Hence drivers that depend on GPIOLIB, but use GPIO consumer
      functionality only, can still be compiled if GPIOLIB is not enabled.
      
      Relax the dependency on GPIOLIB if COMPILE_TEST is enabled, where
      appropriate.
      Signed-off-by: NGeert Uytterhoeven <geert@linux-m68k.org>
      Signed-off-by: NWolfram Sang <wsa@the-dreams.de>
      7e5cd69a
    • S
      i2c: xiic: Fix kerneldoc warnings · bea6ff02
      Shubhrajyoti Datta 提交于
      info(drivers/i2c/busses/i2c-xiic.c:55): Scanning doc for struct xiic_i2c
      Warning(drivers/i2c/busses/i2c-xiic.c:79): No description found for parameter 'endianness'
      Signed-off-by: NShubhrajyoti Datta <shubhraj@xilinx.com>
      Signed-off-by: NWolfram Sang <wsa@the-dreams.de>
      bea6ff02
    • D
      i2c: rk3x: Increase wait timeout to 1 second · 4489750f
      Doug Anderson 提交于
      Although unlikely, it is remotely possible for an i2c command to need
      more than 200ms complete. Unlike smbus, i2c devices can clock stretch
      for an unspecified amount of time. The longest time I've seen
      specified for a device is 144ms (bq27541 battery gas), but one could
      imagine a device taking a bit slower. 1 second "ought to be enough for
      anyone."
      
      The above is not the only justifcation for going above 200ms for a
      timeout, though.  It turns out that if you've got a large number of
      printks going out to a serial console, interrupts on a CPU can be
      disabled for hundreds of milliseconds. That's not a great situation to
      be in to start with (maybe we should put a cap in vprintk_emit()) but
      it's pretty annoying to start seeing unexplained i2c timeouts.
      
      Note that to understand why we can timeout when printk has interrupts
      disabled, you need to understand that on current Linux ARM kernels
      interrupts are routed to a single CPU in a multicore system. Thus,
      you can get:
      
      1. CPU1 is running rk3x_i2c_xfer()
      2. CPU0 calls vprintk_emit(), which disables all IRQs on CPU0.
      3. I2C interrupt is ready but is set to only run on CPU0, where IRQs
         are disabled.
      4. CPU1 timeout expires. I2C interrupt is still ready, but CPU0 is
         still sitting in the same vprintk_emit()
      5. CPU1 sees that no interrupt happened in 200ms, so timeout.
      
      A normal system shouldn't see i2c timeouts anyway, so increasing the
      timeout should help people debugging without hurting other people
      excessively.
      Signed-off-by: NDoug Anderson <dianders@chromium.org>
      Tested-by: NCaesar Wang <wxt@rock-chips.com>
      Acked-by: NUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      Signed-off-by: NWolfram Sang <wsa@the-dreams.de>
      4489750f
  3. 24 4月, 2015 7 次提交
  4. 16 4月, 2015 1 次提交
    • M
      i2c: core: Export bus recovery functions · c1c21f4e
      Mark Brown 提交于
      Current -next fails to link an ARM allmodconfig because drivers that use
      the core recovery functions can be built as modules but those functions
      are not exported:
      
      ERROR: "i2c_generic_gpio_recovery" [drivers/i2c/busses/i2c-davinci.ko] undefined!
      ERROR: "i2c_generic_scl_recovery" [drivers/i2c/busses/i2c-davinci.ko] undefined!
      ERROR: "i2c_recover_bus" [drivers/i2c/busses/i2c-davinci.ko] undefined!
      
      Add exports to fix this.
      
      Fixes: 5f9296ba (i2c: Add bus recovery infrastructure)
      Signed-off-by: NMark Brown <broonie@kernel.org>
      Signed-off-by: NWolfram Sang <wsa@the-dreams.de>
      c1c21f4e
  5. 15 4月, 2015 1 次提交
    • G
      i2c: jz4780: Fix build for m68k and sparc64 · c7f94520
      Guenter Roeck 提交于
      Fix:
      
      drivers/i2c/busses/i2c-jz4780.c: In function 'jz4780_i2c_readw':
      drivers/i2c/busses/i2c-jz4780.c:181:2: error:
      		implicit declaration of function 'readw'
      drivers/i2c/busses/i2c-jz4780.c: In function 'jz4780_i2c_writew':
      drivers/i2c/busses/i2c-jz4780.c:187:2: error:
      		implicit declaration of function 'writew'
      
      seen with sparc64:allmodconfig and m68k:allmodconfig.
      
      The driver has to include linux/io.h.
      
      Fixes: ba92222e ("i2c: jz4780: Add i2c bus controller driver
      	for Ingenic JZ4780")
      Signed-off-by: NGuenter Roeck <linux@roeck-us.net>
      Signed-off-by: NWolfram Sang <wsa@the-dreams.de>
      c7f94520
  6. 11 4月, 2015 1 次提交
  7. 10 4月, 2015 3 次提交
  8. 04 4月, 2015 2 次提交
  9. 27 3月, 2015 5 次提交
  10. 22 3月, 2015 1 次提交
  11. 18 3月, 2015 1 次提交
  12. 17 3月, 2015 2 次提交
  13. 15 3月, 2015 9 次提交