An error occurred fetching the project authors.
  1. 13 Sep, 2017 1 commit
  2. 29 Aug, 2017 1 commit
  3. 13 Aug, 2017 1 commit
  4. 27 Jun, 2017 1 commit
  5. 23 Jun, 2017 2 commits
  6. 19 Jun, 2017 1 commit
  7. 20 Feb, 2017 1 commit
  8. 25 Jan, 2017 1 commit
  9. 01 Dec, 2016 1 commit
  10. 24 Nov, 2016 1 commit
  11. 25 Aug, 2016 3 commits
  12. 23 Oct, 2015 2 commits
  13. 24 Aug, 2015 1 commit
    • Joachim Eastwood's avatar
      i2c: lpc2k: add driver · 3f9c37a0
      Joachim Eastwood authored
      Add support for the I2C controller found on several NXP devices
      including LPC2xxx, LPC178x/7x and LPC18xx/43xx. The controller
      is implemented as a state machine and the driver act upon the
      state changes when the bus is accessed.
      
      The I2C controller supports master/slave operation, bus
      arbitration, programmable clock rate, and speeds up to 1 Mbit/s.
      Signed-off-by: default avatarJoachim Eastwood <manabian@gmail.com>
      Signed-off-by: default avatarWolfram Sang <wsa@the-dreams.de>
      3f9c37a0
  14. 10 Aug, 2015 1 commit
  15. 10 Jun, 2015 1 commit
  16. 31 May, 2015 1 commit
  17. 12 May, 2015 1 commit
  18. 10 Apr, 2015 1 commit
  19. 03 Apr, 2015 1 commit
  20. 22 Mar, 2015 1 commit
  21. 17 Feb, 2015 1 commit
  22. 26 Jan, 2015 1 commit
  23. 14 Dec, 2014 1 commit
  24. 18 Nov, 2014 1 commit
  25. 17 Nov, 2014 1 commit
  26. 10 Nov, 2014 1 commit
  27. 16 Oct, 2014 1 commit
  28. 03 Oct, 2014 1 commit
  29. 16 Jul, 2014 2 commits
  30. 11 Jun, 2014 2 commits
  31. 03 Jun, 2014 1 commit
    • Doug Anderson's avatar
      i2c: ChromeOS EC tunnel driver · 9d230c9e
      Doug Anderson authored
      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: default avatarVincent Palatin <vpalatin@chromium.org>
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      Signed-off-by: default avatarDoug Anderson <dianders@chromium.org>
      Reviewed-by: default avatarWolfram Sang <wsa@the-dreams.de>
      Signed-off-by: default avatarLee Jones <lee.jones@linaro.org>
      9d230c9e
  32. 02 Jun, 2014 1 commit
    • Wolfram Sang's avatar
      i2c: nuc900: remove driver · 7da62cb1
      Wolfram Sang authored
      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: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarWolfram Sang <wsa@the-dreams.de>
      Cc: Wan ZongShun <mcuos.com@gmail.org>
      Acked-by: default avatarArnd Bergmann <arnd@arndb.de>
      7da62cb1
  33. 06 Apr, 2014 1 commit
  34. 28 Mar, 2014 1 commit