An error occurred fetching the project authors.
  1. 01 Oct, 2008 7 commits
  2. 25 Sep, 2008 1 commit
  3. 23 Sep, 2008 1 commit
    • David Brownell's avatar
      twl4030: new-style driver conversion · 3d132266
      David Brownell authored
      More updates preparing for upstream merge of twl4030 driver:
      
       Basic fixes
         -	twl4030-core becomes a new-style I2C driver
         -	declare and use platform_data structure for that core
         -	stop hard-wiring the irq numbers
         -	check functionality that's really used:  I2C, not SMBus
       Cleanup:
         -	remove needless "client string"
         -	remove some fake "bool" types
         -	include catalog part numbers (TPS659{5,3,2}0)
         -	diagnostics should identify the driver!
      
      To use this, all boards with these chips will need to declare this chip
      when they declare their active I2C busses (done in a separate patch).
      
      NOTE:  the TWL4030_IRQ_* symbols still need to vanish, along with other
      global resource assignments associated with these chips.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      3d132266
  4. 12 Sep, 2008 1 commit
    • David Brownell's avatar
      twl4030: improve rtc device setup · 74fcfe9c
      David Brownell authored
      Make the twl4030 RTC initialization follow the driver model better.
      The platform device is created (if needed) as part of twl4030 setup
      instead of as a board-specific thing, and fits properly into the
      driver model tree.
      
      The only minor glitch here is on boards using platform_data to pass
      MSECURE initialization hooks to the RTC driver.  The right solution
      probably just removes that platform_data, and might even make Linux
      follow the principle of "least privilege" (at the hardware level!)
      instead of always holding this signal high.
      
      Pending better handling of MSECURE, this patch just does what the
      RTC init does, but earlier:  MSECURE is always high, so the RTC time
      and calendar registers can be updated (and presumably a bunch of
      non-RTC privileged operations will be allowed too).
      
      Yet to be done:  set up the IRQ resource; make the rtc driver use
      that IRQ resource; and properly issue wakeup alarms.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      74fcfe9c
  5. 06 Aug, 2008 2 commits
  6. 05 Aug, 2008 1 commit
  7. 04 Aug, 2008 8 commits
  8. 23 Jun, 2008 1 commit
  9. 14 May, 2008 1 commit
  10. 06 May, 2008 1 commit
  11. 23 Apr, 2008 1 commit
  12. 11 Apr, 2008 3 commits
  13. 02 Apr, 2008 1 commit
  14. 01 Apr, 2008 1 commit
  15. 31 Mar, 2008 2 commits
  16. 28 Mar, 2008 3 commits
  17. 18 Dec, 2007 2 commits
  18. 23 Nov, 2007 1 commit
  19. 10 Aug, 2007 2 commits