1. 03 6月, 2014 2 次提交
    • D
      i2c: ChromeOS EC tunnel driver · 9d230c9e
      Doug Anderson 提交于
      On ARM Chromebooks we have a few devices that are accessed by both the
      AP (the main "Application Processor") and the EC (the Embedded
      Controller).  These are:
      * The battery (sbs-battery).
      * The power management unit tps65090.
      
      On the original Samsung ARM Chromebook these devices were on an I2C
      bus that was shared between the AP and the EC and arbitrated using
      some extranal GPIOs (see i2c-arb-gpio-challenge).
      
      The original arbitration scheme worked well enough but had some
      downsides:
      * It was nonstandard (not using standard I2C multimaster)
      * It only worked if the EC-AP communication was I2C
      * It was relatively hard to debug problems (hard to tell if i2c issues
        were caused by the EC, the AP, or some device on the bus).
      
      On the HP Chromebook 11 the design was changed to:
      * The AP/EC comms were still i2c, but the battery/tps65090 were no
        longer on the bus used for AP/EC communication.  The battery was
        exposed to the AP through a limited i2c tunnel and tps65090 was
        exposed to the AP through a custom Linux driver.
      
      On the Samsung ARM Chromebook 2 the scheme is changed yet again, now:
      * The AP/EC comms are now using SPI for faster speeds.
      * The EC's i2c bus is exposed to the AP through a full i2c tunnel.
      
      The upstream "tegra124-venice2" uses the same scheme as the Samsung
      ARM Chromebook 2, though it has a different set of components on the
      other side of the bus.
      
      This driver supports the scheme used by the Samsung ARM Chromebook 2.
      Future patches to this driver could add support for the battery tunnel
      on the HP Chromebook 11 (and perhaps could even be used to access
      tps65090 on the HP Chromebook 11 instead of using a special driver,
      but I haven't researched that enough).
      Signed-off-by: NVincent Palatin <vpalatin@chromium.org>
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      Signed-off-by: NDoug Anderson <dianders@chromium.org>
      Reviewed-by: NWolfram Sang <wsa@the-dreams.de>
      Signed-off-by: NLee Jones <lee.jones@linaro.org>
      9d230c9e
    • W
      i2c: nuc900: remove driver · 7da62cb1
      Wolfram Sang 提交于
      Arnd said in another patch:
      
      "As far as I can tell, this driver must have produced this
      error for as long as it has been merged into the mainline kernel, but
      it was never part of the normal build tests:
      
      drivers/i2c/busses/i2c-nuc900.c: In function 'nuc900_i2c_probe':
      drivers/i2c/busses/i2c-nuc900.c:601:17: error: request for member
      'apbfreq' in something not a structure or union
        ret = (i2c->clk.apbfreq)/(pdata->bus_freq * 5) - 1;
                       ^
      This is an attempt to get the driver to build and possibly
      work correctly, although I do wonder whether we should just
      remove it, as it has clearly never worked."
      
      I agree with removing it since nobody showed interest in Arnd's fixup
      patch.
      Reported-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NWolfram Sang <wsa@the-dreams.de>
      Cc: Wan ZongShun <mcuos.com@gmail.org>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      7da62cb1
  2. 06 4月, 2014 1 次提交
  3. 29 3月, 2014 1 次提交
  4. 28 3月, 2014 1 次提交
  5. 13 1月, 2014 1 次提交
  6. 02 1月, 2014 1 次提交
  7. 16 11月, 2013 1 次提交
  8. 15 11月, 2013 1 次提交
  9. 01 11月, 2013 1 次提交
  10. 01 7月, 2013 1 次提交
  11. 15 6月, 2013 1 次提交
  12. 06 6月, 2013 1 次提交
  13. 12 2月, 2013 1 次提交
  14. 11 2月, 2013 1 次提交
  15. 20 11月, 2012 1 次提交
  16. 19 11月, 2012 1 次提交
  17. 29 10月, 2012 1 次提交
  18. 08 10月, 2012 1 次提交
  19. 12 9月, 2012 2 次提交
  20. 10 9月, 2012 1 次提交
    • A
      i2c-designware: Fix build error if CONFIG_I2C_DESIGNWARE_PLATFORM=y && CONFIG_I2C_DESIGNWARE_PCI=y · e68bb91b
      Axel Lin 提交于
      This patch adds config I2C_DESIGNWARE_CORE in Kconfig, and let
      I2C_DESIGNWARE_PLATFORM and I2C_DESIGNWARE_PCI select I2C_DESIGNWARE_CORE.
      
      Because both I2C_DESIGNWARE_PLATFORM and I2C_DESIGNWARE_PCI can be built as
      built-in or module, we also need to export the functions in i2c-designware-core.
      
      This fixes below build error when CONFIG_I2C_DESIGNWARE_PLATFORM=y &&
      CONFIG_I2C_DESIGNWARE_PCI=y:
      
        LD      drivers/i2c/busses/built-in.o
      drivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_clear_int':
      i2c-designware-core.c:(.text+0xa10): multiple definition of `i2c_dw_clear_int'
      drivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x928): first defined here
      drivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_init':
      i2c-designware-core.c:(.text+0x178): multiple definition of `i2c_dw_init'
      drivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x90): first defined here
      drivers/i2c/busses/i2c-designware-pci.o: In function `dw_readl':
      i2c-designware-core.c:(.text+0xe8): multiple definition of `dw_readl'
      drivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x0): first defined here
      drivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_isr':
      i2c-designware-core.c:(.text+0x724): multiple definition of `i2c_dw_isr'
      drivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x63c): first defined here
      drivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_xfer':
      i2c-designware-core.c:(.text+0x4b0): multiple definition of `i2c_dw_xfer'
      drivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x3c8): first defined here
      drivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_is_enabled':
      i2c-designware-core.c:(.text+0x9d4): multiple definition of `i2c_dw_is_enabled'
      drivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x8ec): first defined here
      drivers/i2c/busses/i2c-designware-pci.o: In function `dw_writel':
      i2c-designware-core.c:(.text+0x124): multiple definition of `dw_writel'
      drivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x3c): first defined here
      drivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_xfer_msg':
      i2c-designware-core.c:(.text+0x2e8): multiple definition of `i2c_dw_xfer_msg'
      drivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x200): first defined here
      drivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_enable':
      i2c-designware-core.c:(.text+0x9c8): multiple definition of `i2c_dw_enable'
      drivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x8e0): first defined here
      drivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_read_comp_param':
      i2c-designware-core.c:(.text+0xa24): multiple definition of `i2c_dw_read_comp_param'
      drivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x93c): first defined here
      drivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_disable':
      i2c-designware-core.c:(.text+0x9dc): multiple definition of `i2c_dw_disable'
      drivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x8f4): first defined here
      drivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_func':
      i2c-designware-core.c:(.text+0x710): multiple definition of `i2c_dw_func'
      drivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x628): first defined here
      drivers/i2c/busses/i2c-designware-pci.o: In function `i2c_dw_disable_int':
      i2c-designware-core.c:(.text+0xa18): multiple definition of `i2c_dw_disable_int'
      drivers/i2c/busses/i2c-designware-platform.o:i2c-designware-platdrv.c:(.text+0x930): first defined here
      make[3]: *** [drivers/i2c/busses/built-in.o] Error 1
      make[2]: *** [drivers/i2c/busses] Error 2
      make[1]: *** [drivers/i2c] Error 2
      make: *** [drivers] Error 2
      Signed-off-by: NAxel Lin <axel.lin@gmail.com>
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Tested-by: NJiri Slaby <jslaby@suse.cz>
      Cc: stable@vger.kernel.org [3.2+]
      e68bb91b
  21. 12 5月, 2012 1 次提交
  22. 08 3月, 2012 1 次提交
  23. 25 2月, 2012 2 次提交
  24. 29 10月, 2011 2 次提交
  25. 21 3月, 2011 1 次提交
  26. 17 3月, 2011 1 次提交
  27. 23 2月, 2011 2 次提交
  28. 27 1月, 2011 1 次提交
  29. 04 1月, 2011 1 次提交
  30. 28 10月, 2010 1 次提交
    • A
      i2c-intel-mid: support for Moorestown and Medfield platform · aa62f85d
      Alan Cox 提交于
      (Updated to address Ben's comments. With regard to the message segment
       restriction it's not something we hit on the actual platform so while
       I will investigate that further I don't think its a blocker to submission.
       At worst its a spot over-restrictive)
      
      From: Wen Wang <wen.w.wang@intel.com>
      
      Initial release of the driver. Updated and verified on hardware.
      
      Cleaned up as follows
      
      Alan Cox:
         Squash down the switches into tables, and use the PCI ident field. We
         could perhaps take this further and put the platform and port number into
         this.
         uint32t -> u32
         bracketing of case statements
         spacing and '!' usage
         Check the speed (which is now 0/1/2) is valid and ignore otherwise.
         Fix remaining problems/suggestions from Jean's review
         Fix items from Ben's review
      
      Arjan van de Ven:
         Initial power management hooks
      
      Yong Wang <youg.y.wang@intel.com>:
         Shared IRQ support
      
      Wen Wang <wen.w.wang@intel.com>:
         D3 support
         Fixes for OCT test runs
         Interrupt optimisations
      
      Hong Liu <hong.liu@intel.com>
         The runtime PM code is working on the wrong device (i2c_adapter->dev).
         The correct one should be pci_dev->dev. This breaks attached i2c
         slave devices with runtime PM enabled. Slave device needs to runtime
         resume parent device before runtime resuming itself, but we always get
         error since we don't have pm_runtime callback for i2c_adapter->dev.
      
      Bin Yang <bin.yang@intel.com>:
         Update speed table
      
      Saadi Maalem <saadi.maalem@intel.com>:
         Clear all interrupts in the hardware init
      
      Celine Chotard <celinex.chotard@intel.com>:
         Correct ordering of clear/disable of IRQs
      Signed-off-by: NWen Wang <wen.w.wang@intel.com>
      Signed-off-by: NYong Wang <yong.y.wang@intel.com>
      Signed-off-by: NHong Liu <hong.liu@intel.com>
      Signed-off-by: NBin Yang <bin.yang@intel.com>
      Signed-off-by: NArjan van de Ven <arjan@linux.intel.com>
      Signed-off-by: NAlan Cox <alan@linux.intel.com>
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      aa62f85d
  31. 25 10月, 2010 1 次提交
  32. 11 8月, 2010 1 次提交
  33. 03 6月, 2010 1 次提交
  34. 08 3月, 2010 2 次提交