1. 02 9月, 2014 1 次提交
  2. 17 7月, 2014 1 次提交
    • W
      i2c: i2c-mv64xxx: Drop class based scanning to improve bootup time · 8c49086c
      Wolfram Sang 提交于
      This driver has been flagged to drop class based instantiation. The removal
      improves boot-up time and is unneeded for embedded controllers. Users have been
      warned to switch for some time now, so we can actually do the removal. Keep the
      DEPRECATED flag, so the core can inform users that the behaviour finally
      changed now. After another transition period, this flag can go, too.
      Signed-off-by: NWolfram Sang <wsa@the-dreams.de>
      8c49086c
  3. 22 5月, 2014 1 次提交
  4. 28 3月, 2014 2 次提交
    • W
      i2c: i2c-mv64xxx: deprecate class based instantiation · 5fe29d49
      Wolfram Sang 提交于
      Warn users that class based instantiation is going away soon in favour
      of more robust probing and faster bootup times.
      Signed-off-by: NWolfram Sang <wsa@the-dreams.de>
      5fe29d49
    • M
      i2c: mv64xxx: Fix reset controller handling · f2a67d0c
      Maxime Ripard 提交于
      The reset framework recently gained optional stubs when CONFIG_RESET_CONTROLLER
      is not selected. It also introduced a function reset_get_optional, that is also
      dummy-defined whenever the framework isn't enabled, for drivers that needs an
      optional reset controller.
      
      Switch to this function, since the mv64xxx driver is in this case. This also
      fixes a compilation breakage whenever the reset framework wasn't selected:
      
      drivers/i2c/busses/i2c-mv64xxx.c:771:2: error: implicit declaration of function 'devm_reset_control_get'
      
      While we're at it, remove the redundant test on dev.of_node surrounding the
      calls to reset framework functions, since it will either be a valid pointer, an
      error pointer in the case where we called reset_get_optional without an of_node
      pointer or if it failed, or NULL if we're not loaded through DT.
      Signed-off-by: NMaxime Ripard <maxime.ripard@free-electrons.com>
      Signed-off-by: NWolfram Sang <wsa@the-dreams.de>
      f2a67d0c
  5. 11 3月, 2014 3 次提交
  6. 06 3月, 2014 2 次提交
  7. 15 2月, 2014 1 次提交
  8. 14 1月, 2014 1 次提交
  9. 04 10月, 2013 1 次提交
  10. 28 9月, 2013 2 次提交
  11. 23 8月, 2013 3 次提交
  12. 20 8月, 2013 1 次提交
  13. 26 6月, 2013 2 次提交
  14. 15 6月, 2013 3 次提交
  15. 06 6月, 2013 8 次提交
  16. 18 5月, 2013 1 次提交
  17. 02 4月, 2013 1 次提交
  18. 23 12月, 2012 1 次提交
  19. 24 7月, 2012 1 次提交
    • A
      I2C: MV64XYZ: Add Device Tree support · b61d1575
      Andrew Lunn 提交于
      Extends the driver to get properties from device tree. Rather than
      pass the N & M factors in DT, use the more standard clock-frequency
      property. Calculate N & M at run time. In order to do this, we need to
      know tclk. So the driver uses clk_get() etc in order to get the clock
      and clk_get_rate() to determine the tclk rate. Not all platforms
      however have CLK, so some #ifdefery is needed to ensure the driver
      still compiles when CLK is not available.
      Signed-off-by: NAndrew Lunn <andrew@lunn.ch>
      
      [wsa: converted some ints to u32 to match signedness]
      Signed-off-by: NWolfram Sang <w.sang@pengutronix.de>
      b61d1575
  20. 12 7月, 2012 1 次提交
  21. 13 1月, 2012 1 次提交
  22. 04 1月, 2011 1 次提交
    • R
      i2c-mv64xxx: send repeated START between messages in xfer · eda6bee6
      Rodolfo Giometti 提交于
      As stated into file include/linux/i2c.h we must send a repeated START
      between messages in the same xfer groupset:
      
       * Except when I2C "protocol mangling" is used, all I2C adapters implement
       * the standard rules for I2C transactions.  Each transaction begins with a
       * START.  That is followed by the slave address, and a bit encoding read
       * versus write.  Then follow all the data bytes, possibly including a byte
       * with SMBus PEC.  The transfer terminates with a NAK, or when all those
       * bytes have been transferred and ACKed.  If this is the last message in a
       * group, it is followed by a STOP.  Otherwise it is followed by the next
       * @i2c_msg transaction segment, beginning with a (repeated) START.
      Signed-off-by: NRodolfo Giometti <giometti@linux.it>
      Signed-off-by: NMauro Barella <mbarella@vds-it.com>
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      eda6bee6
  23. 22 5月, 2010 1 次提交