- 13 Dec, 2009 40 commits
-
-
Rajendra Nayak authored
This patch adds initial support for creating twl6030 PMIC specific voltage regulators in the twl mfd driver. Board specific regulator configurations will have to be passed from respective board files. Signed-off-by:
Rajendra Nayak <rnayak@ti.com> Signed-off-by:
Balaji T K <balajitk@ti.com> Acked-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Reviewed-by:
Tony Lindgren <tony@atomide.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Rajendra Nayak authored
This patch updates the regulator driver to add support for TWL6030 PMIC specific LDO regulators. SMPS resources are not yet supported for TWL6030 and also .set_mode and .get_status for LDO's are yet to be implemented for TWL6030. Signed-off-by:
Rajendra Nayak <rnayak@ti.com> Signed-off-by:
Balaji T K <balajitk@ti.com> Acked-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Reviewed-by:
Tony Lindgren <tony@atomide.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Balaji T K authored
This patch adds support for RTC in phoenix TWL6030. Register offset addresses have changed in TWL6030 rtc-twl.c will hence forth support all twl RTC (4030, 5030, 6030 ..) Signed-off-by:
Balaji T K <balajitk@ti.com> Signed-off-by:
Santosh Shilimkar <santosh.shilimkar@ti.com> Reviewed-by:
Tony Lindgren <tony@atomide.com> Reviewed-by:
Kevin Hilman <khilman@deeprootsystems.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Balaji T K authored
This patch adds support for phoenix interrupt framework. New iInterrupt status register A, B, C are introduced in Phoenix and are cleared on write. Due to the differences in interrupt handling with respect to TWL4030, twl6030-irq.c is created for TWL6030 PMIC Signed-off-by:
Rajendra Nayak <rnayak@ti.com> Signed-off-by:
Balaji T K <balajitk@ti.com> Signed-off-by:
Santosh Shilimkar <santosh.shilimkar@ti.com> Reviewed-by:
Tony Lindgren <tony@atomide.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Rajendra Nayak authored
This patch renames all twl4030_ functions to twl so that regulator driver can be reused by Triton - TWL4030 and Phoenix - TWL6030. Signed-off-by:
Rajendra Nayak <rnayak@ti.com> Signed-off-by:
Balaji T K <balajitk@ti.com> Signed-off-by:
Santosh Shilimkar <santosh.shilimkar@ti.com> Acked-by:
Kevin Hilman <khilman@deeprootsystems.com> Acked-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Balaji T K authored
This patch renames all twl4030_ functions to twl_ so that RTC driver can be shared between Triton and Phoenix. Signed-off-by:
Balaji T K <balajitk@ti.com> Signed-off-by:
Nayak Rajendra <rnayak@ti.com> Signed-off-by:
Santosh Shilimkar <santosh.shilimkar@ti.com> Acked-by:
Kevin Hilman <khilman@deeprootsystems.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Balaji T K authored
This patch renames function names like twl4030_i2c_write_u8, twl4030_i2c_read_u8 to twl_i2c_write_u8, twl_i2c_read_u8 and also common variable in twl-core.c Signed-off-by:
Rajendra Nayak <rnayak@ti.com> Signed-off-by:
Balaji T K <balajitk@ti.com> Signed-off-by:
Santosh Shilimkar <santosh.shilimkar@ti.com> Acked-by:
Kevin Hilman <khilman@deeprootsystems.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Santosh Shilimkar authored
The upcoming TWL6030 is companion chip for OMAP4 like the current TWL4030 for OMAP3. The common modules like RTC, Regulator creates opportunity to re-use the most of the code from twl4030. This patch renames few common drivers twl4030* files to twl* to enable the code re-use. Signed-off-by:
Rajendra Nayak <rnayak@ti.com> Signed-off-by:
Balaji T K <balajitk@ti.com> Signed-off-by:
Santosh Shilimkar <santosh.shilimkar@ti.com> Acked-by:
Kevin Hilman <khilman@deeprootsystems.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Amit Kucheria authored
We should be checking if all the messages were tranferred. If not, then we should propagate the i2c core error code or EIO. Currently we return success (0) even if none of messages were transferred successfully. Signed-off-by:
Amit Kucheria <amit.kucheria@verdurent.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Juha Keski-Saari authored
Add all twl4030 regulators to the twl4030 mfd driver and twl4030_platform_data Signed-off-by:
Juha Keski-Saari <ext-juha.1.keski-saari@nokia.com> Acked-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Uwe Kleine-König authored
Setting ADREFMODE is utter nonsense, but that's hard to read out of the spec. Strange enough it's possible to read x and y values even when it's set. When unset you can get values not only for the axes, but also for contact resistance which allows the touch driver to report pressure values. Signed-off-by:
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Antonio Ospite authored
We used these, in a first version of leds-pcap driver, in order to encode gpio enabling and gpio inversion for a led inside the variable used for the gpio number. In the new leds-pcap driver we rely on gpio_is_valid() to derive if a led is gpio enabled and we have a dedicated flag to tell if the gpio value has to be inverted. Signed-off-by:
Antonio Ospite <ospite@studenti.unina.it> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Uwe Kleine-König authored
This fixes several things while still providing the old API: - simplify and fix locking - better error handling - don't ack all irqs making it impossible to detect a reset of the rtc - use a timeout variant to wait for completion of ADC conversion - provide platform-data to regulator subdevice (This allows making struct mc13783 opaque for other drivers after the regulator driver is updated to use its platform_data.) - expose all interrupts - use threaded irq After all users in mainline are converted to the new API, some things (e.g. mc13783-private.h) can go away. Signed-off-by:
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Cc: Sascha Hauer <s.hauer@pengutronix.de> Cc: Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Mark Brown authored
Systems using the WM835x need to choose which of the default register settings are required on the system. Currently there is a compile time warning as well as a runtime error intended to flag up to users that this is required but this also triggers for people building the driver in order to obtain build coverage. Remove the build warning, leaving only the runtime error, in order to reduce noise for people doing generic kernel work. Signed-off-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Mark Brown authored
This works around issues with allmodconfig where it won't propagate the dependency from the WM831x core back to the I2C and MFD cores. When doing allmodconfig this causes WM831x to be omitted and ensures that in normal builds the dependencies get shaken out. Signed-off-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Mark Brown authored
The genirq infrastructure functions aren't currently exported, preventing modular builds. Reported-by:
Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Dan Carpenter authored
It was *pdev which was allocated not pdev. Signed-off-by:
Dan Carpenter <error27@gmail.com> Acked-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Alan Cox authored
Signed-off-by:
Alan Cox <alan@linux.intel.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Mark Brown authored
Signed-off-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Linus Walleij authored
This remove the default 'y' selection of AB4500, currently everyone enabling the SPI subsystem will get a copy of this driver. Signed-off-by:
Linus Walleij <linus.walleij@stericsson.com> Cc: Srinidhi Kasagar <srinidhi.kasagar@stericsson.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Mark Brown authored
Replace the wm831x-local IRQ infrastructure with genirq, allowing access to the diagnostic infrastructure of genirq and allowing us to implement interrupt support for the GPIOs. The switchover is done within the wm831x specific IRQ API, further patches will convert the individual drivers to use genirq directly. Signed-off-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Ilkka Koskinen authored
TWL5031 introduces two new interrupts in PIH. Moreover, BCI has changed remarkably and, thus, it's disabled when TWL5031 is in use. Signed-off-by:
Ilkka Koskinen <ilkka.koskinen@nokia.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Mark Brown authored
Bring the WM8350 IRQ API more in line with the generic IRQ API by masking and unmasking interrupts as they are requested and freed. This is mostly just a case of deleting the mask and unmask calls from the individual drivers. The RTC driver is changed to mask the periodic IRQ after requesting it rather than only unmasking the alarm IRQ. If the periodic IRQ fires in the period where it is reqested then there will be a spurious notification but there should be no serious consequences from this. The CODEC drive is changed to explicitly disable headphone jack detection prior to requesting the IRQs. This will avoid the IRQ firing with no jack set up. Signed-off-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Mark Brown authored
This is done as simple code transformation, the semantics of the IRQ API provided by the core are are still very different to those of genirq (mainly with regard to masking). Signed-off-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Antonio Ospite authored
Abusing subdev drvdata is not needed anymore, as all pcap subdevs are now retrieving the pcap pointer from their parent device. This change removes a leftover coming from early versions of ezx-pcap and its subdevs drivers. Signed-off-by:
Antonio Ospite <ospite@studenti.unina.it> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Ben Dooks authored
Add function to allow the configuation fo the VDCDC2 register by external users, to allow changing of the standard and low-power running modes. This is needed, for example, for the Simtec IM2440D20 where we need to use the low-power mode to shutdown the LDO/DCDC that are not needed during suspend (saving substantial power) and the runtime use of the low-power mode to change VCore. Signed-off-by:
Ben Dooks <ben@simtec.co.uk> Signed-off-by:
Simtec Linux Team <linux@simtec.co.uk> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Ben Dooks authored
If the board does not care where the TPS turns up, then specifiying the value -1 to get gpiolib to dynamically allocate the base for the chip is valid. Change the test to look for != 0, so that any boards specifying zero will not end up with gpio that they didn't want. Signed-off-by:
Ben Dooks <ben@simtec.co.uk> Signed-off-by:
Simtec Liunx Team <linux@simtec.co.uk> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Ilkka Koskinen authored
Allows TWL's 32kHz oscillator to go in low-power mode when main battery voltage is running low. Signed-off-by:
Ilkka Koskinen <ilkka.koskinen@nokia.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Mark Brown authored
This is currently unused by the wm8350 drivers but getting it merged now will reduce merge issues in the future when implementing wm8350 genirq support. Signed-off-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Amit Kucheria authored
Based on Aaro's previous fix, this needs to be fixed for the newly added remap_off and remap_sleep resources as well. The code tries to skip values initialized with -1, but since the values are unsigned the comparison is always true. The patch eliminates the following compiler warnings: drivers/mfd/twl4030-power.c: In function 'twl4030_configure_resource': drivers/mfd/twl4030-power.c:338: warning: comparison is always true due to limited range of data type Signed-off-by:
Amit Kucheria <amit.kucheria@verdurent.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Amit Kucheria authored
The power scripts optimisation was mainly done by: Tero Kristo <tero.kristo@nokia.com> and Arnaud Mandy <ext-arnaud.2.mandy@nokia.com> I'm only refactoring and testing it against the mainline kernel. Signed-off-by:
Amit Kucheria <amit.kucheria@verdurent.com> Cc: Tero Kristo <tero.kristo@nokia.com> Cc: linux-omap@vger.kernel.org Acked-by:
Tony Lindgren <tony@atomide.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Lars-Peter Clausen authored
Currently the child devices were not freed if the irq could not be requested. This patch restructures the function, that in case of an error all previously allocated resources are freed. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
Paul Fertser <fercerpav@gmail.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Mark Brown authored
The function is not exported as the __ indicates. __ Signed-off-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Acked-by:
Michael Hennerich <michael.hennerich@analog.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Aaro Koskinen authored
The code tries to skip values initialized with -1, but since the values are unsigned the comparison is always true. The patch eliminates the following compiler warnings: drivers/mfd/twl4030-power.c: In function 'twl4030_configure_resource': drivers/mfd/twl4030-power.c:338: warning: comparison is always true due to limited range of data type drivers/mfd/twl4030-power.c:358: warning: comparison is always true due to limited range of data type drivers/mfd/twl4030-power.c:363: warning: comparison is always true due to limited range of data type Signed-off-by:
Aaro Koskinen <aaro.koskinen@nokia.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Amit Kucheria authored
The <RESOURCE>_REMAP register allows configuration of the <RESOURCE> in case of a sleep or off transition. Allow this property of resources to be configured (through twl4030_resconfig) and add code to parse these values to program the registers accordingly. Signed-off-by:
Amit Kucheria <amit.kucheria@verdurent.com> Cc: linux-omap@vger.kernel.org Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Amit Kucheria authored
Describe how the resource registers are laid out and the various bit-fields in them. Signed-off-by:
Amit Kucheria <amit.kucheria@verdurent.com> Cc: linux-omap@vger.kernel.org Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Amit Kucheria authored
Stick to the names used in the reference manual Signed-off-by:
Amit Kucheria <amit.kucheria@verdurent.com> Cc: linux-omap@vger.kernel.org Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Lars-Peter Clausen authored
Currently the pcf50633-regulator driver data is set to the pcf50633 core structure, but the pcf50633-regulator remove handler assumes that it is set to the regulator device. This patch fixes the issue by accessing the pcf506533 core structure through its parent device and setting the driver data to the regulator device. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
Paul Fertser <fercerpav@gmail.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Lars-Peter Clausen authored
Platform devices allocated with platform_device_alloc should use platform_device_add_data to set the platform data, because kfree will be called on the platform_data when the device is released. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
Paul Fertser <fercerpav@gmail.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-
Lars-Peter Clausen authored
Since platform_device_add_data copies the passed data, the allocated subdev_pdata is never freed. A simple fix would be to either free subdev_pdata or put it onto the stack. But since the pcf50633 child devices can rely on beeing children of the pcf50633 core device it's much more elegant to get access to pcf50633 core structure through that link. This allows to get completly rid of pcf5033_subdev_pdata. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
Paul Fertser <fercerpav@gmail.com> Signed-off-by:
Samuel Ortiz <sameo@linux.intel.com>
-