1. 23 11月, 2009 2 次提交
  2. 06 10月, 2009 1 次提交
  3. 18 9月, 2009 2 次提交
  4. 17 9月, 2009 1 次提交
  5. 28 8月, 2009 1 次提交
  6. 19 6月, 2009 1 次提交
  7. 16 5月, 2009 1 次提交
  8. 07 4月, 2009 1 次提交
  9. 03 4月, 2009 1 次提交
  10. 31 3月, 2009 1 次提交
    • D
      regulator: twl4030 regulators · fa16a5c1
      David Brownell 提交于
      Support most of the LDO regulators in the twl4030 family chips.
      In the case of LDOs supporting MMC/SD, the voltage controls are
      used; but in most other cases, the regulator framework is only
      used to enable/disable a supplies, conserving power when a given
      voltage rail is not needed.
      
      The drivers/mfd/twl4030-core.c code already sets up the various
      regulators according to board-specific configuration, and knows
      that some chips don't provide the full set of voltage rails.
      
      The omitted regulators are intended to be under hardware control,
      such as during the hardware-mediated system powerup, powerdown,
      and suspend states.  Unless/until software hooks are known to
      be safe, they won't be exported here.
      
      These regulators implement the new get_status() operation, but
      can't realistically implement get_mode(); the status output is
      effectively the result of a vote, with the relevant hardware
      inputs not exposed.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Acked-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      Signed-off-by: NLiam Girdwood <lrg@slimlogic.co.uk>
      fa16a5c1
  11. 07 1月, 2009 1 次提交
  12. 04 1月, 2009 5 次提交
    • D
      mfd: dm355evm msp430 driver · 0931a4c6
      David Brownell 提交于
      Basic MFD framework for the MSP430 microcontroller firmware used
      on the dm355evm board:
      
       - Provides an interface for other drivers: register read/write
         utilities, and register declarations.
      
       - Directly exports:
           * Many signals through the GPIO framework
               + LEDs
               + SW6 through gpio sysfs
      	 + NTSC/nPAL jumper through gpio sysfs
      	 + ... more could be added later, e.g. MMC signals
           * Child devices:
      	+ LEDs, via leds-gpio child (and default triggers)
      	+ RTC, via rtc-dm355evm child device
      	+ Buttons and IR control, via dm355evm_keys
      
       - Supports power-off system call.  Use the reset button to power
         the board back up; the power supply LED will be on, but the
         MSP430 waits to re-activate the regulators.
      
       - On probe() this:
           * Announces firmware revision
           * Turns off the banked LEDs
           * Exports the resources noted above
           * Hooks the power-off support
           * Muxes tvp5146 -or- imager for video input
      
      Unless the new tvp514x driver (tracked for mainline) is configured,
      this assumes that some custom imager driver handles video-in.
      
      This completely ignores the registers reporting the output voltages
      on the various power supplies.  Someone could add a hwmon interface
      if that seems useful.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NSamuel Ortiz <sameo@openedhand.com>
      0931a4c6
    • D
      mfd: twl4030 regulator bug fixes · b73eac78
      David Brownell 提交于
      This contains two bugfixes to the initial twl4030 regulator
      support patch related to USB:
      
       (a) always overwrite the old list of consumers ... else
           the regulator handles all use the same "usb1v5" name;
       (b) don't set up the "usbcp" regulator, which turns out
           to be managed through separate controls, usually ULPI
           directly from the OTG controller.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NSamuel Ortiz <sameo@openedhand.com>
      b73eac78
    • D
      mfd: twl4030: create some regulator devices · dad759ff
      David Brownell 提交于
      Initial code to create twl4030 voltage regulator devices, using
      the new regulator framework.  Note that this now starts to care
      what name is used to declare the TWL chip:
      
       - TWL4030 is the "old" chip; newer ones have a bigger variety
         of VAUX2 voltages.
      
       - TWL5030 is the core "new" chip; TPS65950 is its catalog version.
      
       - The TPS65930 and TPS65920 are cost-reduced catalog versions of
         TWL5030 parts ... fewer regulators, no battery charger, etc.
      
      Board-specific regulator configuration should be provided, listing
      which regulators are used and their constraints (e.g. 1.8V only).
      
      Code that could ("should"?) leverage the regulator stuff includes
      TWL4030 USB transceiver support and MMC glue, LCD support for the
      3430SDP and Labrador boards, and S-Video output.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NSamuel Ortiz <sameo@openedhand.com>
      dad759ff
    • D
      mfd: twl4030: cleanup symbols and OMAP dependency · 67460a7c
      David Brownell 提交于
      Finish removing dependency of TWL driver stack on platform-specific
      IRQ definitions ... and remove the build dependency on OMAP.
      
      This lets the TWL4030 code be included in test builds for most
      platforms, and will make it easier for non-OMAP folk to update
      most of this code for new APIs etc.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NSamuel Ortiz <sameo@openedhand.com>
      67460a7c
    • D
      mfd: allow reading entire register banks on twl4030 · 3fba19ec
      David Brownell 提交于
      Minor change to the TWL4030 utility interface:  support reads
      of all 256 bytes in each register bank (vs just 255).  This
      can help when debugging, but is otherwise a NOP.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NSamuel Ortiz <sameo@openedhand.com>
      3fba19ec
  13. 20 12月, 2008 1 次提交
  14. 22 10月, 2008 1 次提交
    • D
      mfd: twl4030 IRQ handling update · a30d46c0
      David Brownell 提交于
      - Move it into a separate file; clean and streamline it
       - Restructure the init code for reuse during secondary dispatch
       - Support both levels (primary, secondary) of IRQ dispatch
       - Use a workqueue for irq mask/unmask and trigger configuration
      
      Code for two subchips currently share that secondary handler code.
      One is the power subchip; its IRQs are now handled by this core,
      courtesy of this patch.  The other is the GPIO module, which will
      be supported through a later patch.
      
      There are also minor changes to the header file, mostly related
      to GPIO support; nothing yet in mainline cares about those.  A
      few references to OMAP-specific symbols are disabled; when they
      can all be removed, the TWL4030 support ceases being OMAP-specific.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NSamuel Ortiz <sameo@openedhand.com>
      a30d46c0
  15. 20 10月, 2008 1 次提交
    • D
      mfd: TWL4030 core driver · a603a7fa
      David Brownell 提交于
      This patch adds the core of the TWL4030 driver, which supports
      chips including the TPS65950.  These chips are multi-function; see
      
        http://focus.ti.com/docs/prod/folders/print/tps65950.html
      
      Public specs are in the works.  For now, the block diagram on
      the second page of the datasheet is fairly informative.
      
      There are some known issues with this core code.  Most notably,
      the IRQ dispatching needs simplification (to use more of genirq),
      generalization (integrating support for secondary IRQ dispatch
      as well as primary, and removing the build dependency on OMAP),
      and then probably updating to leverage threaded IRQ support
      (expected to arrive in mainline "soon").
      
      Once the core is in mainline, drivers for other parts of this
      chip can follow its lead and start swimming upstream too.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NSamuel Ortiz <sameo@openedhand.com>
      a603a7fa
  16. 26 7月, 2008 1 次提交
  17. 15 7月, 2008 1 次提交
  18. 19 5月, 2008 1 次提交
  19. 15 4月, 2008 1 次提交
  20. 07 2月, 2008 2 次提交
  21. 06 2月, 2008 2 次提交
    • E
      gpiolib: pca9539 i2c gpio expander support · 9e60fdcf
      eric miao 提交于
      This adds a new-style I2C driver with basic support for the sixteen bit
      PCA9539 GPIO expanders.  These chips have multiple registers, push-pull output
      drivers, and (not supported in this patch) pin change interrupts.
      
      Board-specific code must provide "pca9539_platform_data" with each chip's
      "i2c_board_info".  That provides the GPIO numbers to be used by that chip, and
      callbacks for board-specific setup/teardown logic.
      
      Derived from drivers/i2c/chips/pca9539.c (which has no current known users).
      This is faster and simpler; it uses 16-bit register access, and cache the
      OUTPUT and DIRECTION registers for fast access
      Signed-off-by: Neric miao <eric.miao@marvell.com>
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Acked-by: NJean Delvare <khali@linux-fr.org>
      Cc: Sam Ravnborg <sam@ravnborg.org>
      Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>
      Cc: Philipp Zabel <philipp.zabel@gmail.com>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Cc: Ben Gardner <bgardner@wabtec.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      9e60fdcf
    • D
      gpiolib: pcf857x i2c gpio expander support · 15fae37d
      David Brownell 提交于
      This is a new-style I2C driver for most common 8 and 16 bit I2C based
      "quasi-bidirectional" GPIO expanders: pcf8574 or pcf8575, and several
      compatible models (mostly faster, supporting I2C at up to 1 MHz).
      
      The driver exposes the GPIO signals using the platform-neutral GPIO
      programming interface, so they are easily accessed by other kernel code.  The
      lack of such a flexible kernel API has been a big factor in the proliferation
      of board-specific drivers for these chips...  stuff that rarely makes it
      upstream since it's so ugly.  This driver will let such boards use standard
      calls.
      
      Since it's a new-style driver, these devices must be configured as part of
      board-specific init.  That eliminates the need for error-prone manual
      configuration of module parameters, and makes compatibility with legacy
      drivers (pcf8574.c, pc8575.c) for these chips easier (there's a clear
      either/or disjunction).
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Acked-by: NJean Delvare <khali@linux-fr.org>
      Cc: Eric Miao <eric.miao@marvell.com>
      Cc: Sam Ravnborg <sam@ravnborg.org>
      Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>
      Cc: Philipp Zabel <philipp.zabel@gmail.com>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Cc: Ben Gardner <bgardner@wabtec.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      15fae37d
  22. 28 1月, 2008 1 次提交