1. 25 1月, 2013 1 次提交
  2. 23 12月, 2012 1 次提交
  3. 02 11月, 2012 1 次提交
  4. 14 9月, 2012 3 次提交
  5. 19 8月, 2012 1 次提交
  6. 24 7月, 2012 1 次提交
  7. 12 7月, 2012 5 次提交
  8. 08 7月, 2012 4 次提交
  9. 12 6月, 2012 1 次提交
  10. 12 5月, 2012 2 次提交
  11. 23 4月, 2012 1 次提交
  12. 08 3月, 2012 1 次提交
  13. 07 2月, 2012 1 次提交
  14. 20 12月, 2011 2 次提交
  15. 01 11月, 2011 1 次提交
  16. 29 10月, 2011 1 次提交
    • O
      i2c-tegra: __iomem annotation fix · f533c61e
      Olof Johansson 提交于
      drivers/i2c/busses/i2c-tegra.c:585:7: warning: incorrect type in assignment (different address spaces)
      drivers/i2c/busses/i2c-tegra.c:585:7:    expected void *base
      drivers/i2c/busses/i2c-tegra.c:585:7:    got void [noderef] <asn:2>*
      drivers/i2c/busses/i2c-tegra.c:619:16: warning: incorrect type in assignment (different address spaces)
      drivers/i2c/busses/i2c-tegra.c:619:16:    expected void [noderef] <asn:2>*base
      drivers/i2c/busses/i2c-tegra.c:619:16:    got void *base
      drivers/i2c/busses/i2c-tegra.c:689:10: warning: incorrect type in argument 1 (different address spaces)
      drivers/i2c/busses/i2c-tegra.c:689:10:    expected void volatile [noderef] <asn:2>*addr
      drivers/i2c/busses/i2c-tegra.c:689:10:    got void *base
      Signed-off-by: NOlof Johansson <olof@lixom.net>
      Acked-by; Stephen Warren <swarren@nvidia.com>
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      f533c61e
  17. 07 9月, 2011 3 次提交
  18. 27 7月, 2011 1 次提交
  19. 28 6月, 2011 1 次提交
    • S
      i2c: tegra: Assign unused slave address · 5afa9d35
      Stephen Warren 提交于
      On Tegra, we should always use the "new" I2C slave controller, to avoid
      issues with the old controller. This was implemented in commit 65a1a0ac
      "i2c: tegra: Enable new slave mode."
      
      There is currently no driver for the Tegra I2C slave controller upstream.
      Additionally, the controller cannot be completely disabled. Instead, we
      need to:
      
      a) Set I2C_SL_CNFG_NACK to make the controller automatically NACK any
      incoming transactions.
      
      b) The controller's definition of NACK isn't identical to the I2C
      protocol's definition. Specifically, it will perform a standard NACK, but
      *also* continue to hold the clock line low in expectation of receiving
      more data. This can hang the bus, or at least cause transaction timeouts,
      if something starts a transaction that matches the controller's slave
      address. Since the default address is 0x00, the general call address,
      this does occur in practice.
      
      To avoid this, we explicitly program a slave address that is reserved for
      future expansion. For current boards, this guarantees the address will
      never be used. If a future board ever needs to use this address, we can
      add platform data to determine a board-specific safe address. 0xfc is
      picked by this patch.
      
      This patch is based on a change previously posted by: Wei Ni <wni@nvidia.com>
      http://www.spinics.net/lists/linux-i2c/msg05437.html
      In turned based on internal changes by: Bharat Nihalani <bnihalani@nvidia.com>
      
      A semantically equivalent change has been contained in the various
      ChromeOS kernels for a while.
      
      I tested this change on top of 3.0-rc2 on Harmony, and interacted with
      the WM8903 I2C-based audio codec.
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      5afa9d35
  20. 11 5月, 2011 4 次提交
  21. 31 3月, 2011 1 次提交
  22. 23 2月, 2011 1 次提交