You need to sign in or sign up before continuing.
  1. 20 2月, 2015 1 次提交
  2. 17 2月, 2015 1 次提交
  3. 06 2月, 2015 1 次提交
  4. 27 1月, 2015 2 次提交
  5. 26 1月, 2015 1 次提交
  6. 18 12月, 2014 1 次提交
  7. 14 12月, 2014 1 次提交
  8. 24 11月, 2014 1 次提交
  9. 19 11月, 2014 1 次提交
  10. 18 11月, 2014 2 次提交
  11. 13 11月, 2014 1 次提交
  12. 11 11月, 2014 1 次提交
  13. 16 10月, 2014 2 次提交
  14. 07 10月, 2014 1 次提交
  15. 03 10月, 2014 2 次提交
  16. 26 9月, 2014 1 次提交
  17. 05 8月, 2014 1 次提交
  18. 18 7月, 2014 1 次提交
  19. 17 7月, 2014 2 次提交
  20. 12 6月, 2014 2 次提交
  21. 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
  22. 22 5月, 2014 1 次提交
  23. 08 4月, 2014 1 次提交
  24. 07 4月, 2014 1 次提交
    • W
      i2c: cadence: fix Kconfig dependency · 1fbeab0b
      Wolfram Sang 提交于
      During development, the driver first really needed to depend on
      COMMON_CLK only. Later, it was switched to writel_relaxed, but it was
      forgotten to update the dependencies, so build errors occured:
      
      config: make ARCH=i386 allyesconfig
      
      All error/warnings:
      
         drivers/i2c/busses/i2c-cadence.c: In function 'cdns_i2c_clear_bus_hold':
      >> drivers/i2c/busses/i2c-cadence.c:168:3: error: implicit declaration
      >> of function 'writel_relaxed' [-Werror=implicit-function-declaration]
      
      Use a very safe dependency for now.
      Signed-off-by: NWolfram Sang <wsa@the-dreams.de>
      1fbeab0b
  25. 06 4月, 2014 1 次提交
  26. 29 3月, 2014 1 次提交
  27. 28 3月, 2014 1 次提交
  28. 14 3月, 2014 1 次提交
  29. 10 3月, 2014 1 次提交
  30. 07 3月, 2014 1 次提交
  31. 06 3月, 2014 1 次提交
  32. 25 1月, 2014 1 次提交
  33. 13 1月, 2014 1 次提交