1. 19 5月, 2011 1 次提交
    • G
      drivercore: revert addition of of_match to struct device · b1608d69
      Grant Likely 提交于
      Commit b826291c, "drivercore/dt: add a match table pointer to struct
      device" added an of_match pointer to struct device to cache the
      of_match_table entry discovered at driver match time.  This was unsafe
      because matching is not an atomic operation with probing a driver.  If
      two or more drivers are attempted to be matched to a driver at the
      same time, then the cached matching entry pointer could get
      overwritten.
      
      This patch reverts the of_match cache pointer and reworks all users to
      call of_match_device() directly instead.
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      b1608d69
  2. 01 3月, 2011 1 次提交
  3. 14 1月, 2011 1 次提交
  4. 04 1月, 2011 1 次提交
  5. 11 8月, 2010 1 次提交
  6. 06 8月, 2010 1 次提交
  7. 28 5月, 2010 1 次提交
  8. 22 5月, 2010 1 次提交
    • G
      of: Remove duplicate fields from of_platform_driver · 4018294b
      Grant Likely 提交于
      .name, .match_table and .owner are duplicated in both of_platform_driver
      and device_driver.  This patch is a removes the extra copies from struct
      of_platform_driver and converts all users to the device_driver members.
      
      This patch is a pretty mechanical change.  The usage model doesn't change
      and if any drivers have been missed, or if anything has been fixed up
      incorrectly, then it will fail with a compile time error, and the fixup
      will be trivial.  This patch looks big and scary because it touches so
      many files, but it should be pretty safe.
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      Acked-by: NSean MacLennan <smaclennan@pikatech.com>
      4018294b
  9. 19 5月, 2010 1 次提交
  10. 18 12月, 2009 3 次提交
  11. 23 9月, 2009 5 次提交
  12. 08 8月, 2009 1 次提交
  13. 30 7月, 2009 1 次提交
    • A
      sdhci: get rid of "frequency too high" flood when using eSDHC · a9e58f25
      Anton Vorontsov 提交于
      Since commit 8dfd0374 ("MMC core: limit
      minimum initialization frequency to 400kHz") MMC core checks for minimum
      frequency, and that causes following messages flood when using eSDHC
      controllers:
      
        ...
        mmc0: Minimum clock frequency too high for identification mode
        mmc0: Minimum clock frequency too high for identification mode
        ...
      
      The warnings are legitimate, since if we'd use 133 MHz clocks for standard
      SDHCI controllers, we'd not able to scale frequency down to 400 kHz.
      
      But eSDHC controllers have a non-standard SD clock management, so we can
      divide clock by 256 * 16, not just 256.
      
      This patch introduces get_min_clock() callback for sdhci core and
      implements it for sdhci-of driver, and thus fixes the issue.
      Signed-off-by: NAnton Vorontsov <avorontsov@ru.mvista.com>
      Cc: Matt Fleming <matt@console-pimps.org>
      Cc: Ian Molton <ian@mnementh.co.uk>
      Cc: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
      Cc: Pierre Ossman <drzeus@drzeus.cx>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      a9e58f25
  14. 22 6月, 2009 1 次提交
  15. 04 6月, 2009 2 次提交
  16. 25 3月, 2009 1 次提交