27 May, 2011
6 commits
-
Avoid to use constraint name in regulator driver. So use regulator id is used
instead in platform driver.Signed-off-by: Haojian Zhuang
Cc: Liam Girdwood
Acked-by: Mark Brown
Signed-off-by: Samuel Ortiz -
i2c_client parameter isn't used in some functions. Just remove it.
Signed-off-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz -
Maybe multiple PMIC devices are installed into one board. Static variable
can only make driver logic mess. So remove these variable, and use
platform data from platform driver instead.Signed-off-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz -
Enable rtc function in 88pm860x PMIC.
Signed-off-by: Haojian Zhuang
Cc: Alessandro Zummo
Signed-off-by: Samuel Ortiz -
WARNING: vmlinux.o(.devinit.text+0x6c4): Section mismatch in reference
from the function device_onkey_init() to the (unknown reference)
.init.data:(unknown)
The function __devinit device_onkey_init() references a (unknown reference)
__initdata (unknown).
If (unknown) is only used by device_onkey_init then annotate (unknown)
with a matching annotation.It's caused by using __initdata on mfd cell resources. Replace __initdata
with __devinitdata.Signed-off-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz -
With the addition of a platform device mfd_cell pointer, MFD drivers
can go back to passing platform back to their sub drivers.
This allows for an mfd_cell->mfd_data removal and thus keep the
sub drivers MFD agnostic. This is mostly needed for non MFD aware
sub drivers.Cc: Mark Brown
Cc: Liam Girdwood
Cc: Richard Purdie
Acked-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz
27 Mar, 2011
2 commits
-
Converted with coccinelle.
Signed-off-by: Thomas Gleixner
Acked-by: Mark Brown
Signed-off-by: Samuel Ortiz -
Signed-off-by: Thomas Gleixner
Signed-off-by: Samuel Ortiz
23 Mar, 2011
4 commits
-
Copy 88pm860x platform data into different mfd_data structure for
onkey/touch/codec/power driver. So move the identification of
device node from those drivers to mfd driver.Signed-off-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz -
Copy 88pm860x platform data into different mfd_data structure for
regulator driver. So move the identification of device node from
regulator driver to mfd driver.Signed-off-by: Haojian Zhuang
Acked-by: Mark Brown
Signed-off-by: Samuel Ortiz -
Copy 88pm860x platform data into different mfd_data structure for
led driver. So move the identification of device node from led
driver to mfd driver.Signed-off-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz -
Copy 88pm860x platform data into different mfd_data structure for
backlight driver. So move the identification of device node from
backlight driver to mfd driver.Signed-off-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz
14 Jan, 2011
1 commit
-
The interrupt controller APIs are being updated to pass a struct irq_data
rather than the interrupt number.Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz
29 Oct, 2010
2 commits
-
Chipid of 88pm8607 is 0x40 or 0x50.
Signed-off-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz -
Add codec IRQ resources that are used in 88pm860x codec driver.
Signed-off-by: Haojian Zhuang
Acked-by: Mark Brown
Signed-off-by: Samuel Ortiz
12 Aug, 2010
2 commits
-
The original code had a compile warning:
drivers/mfd/88pm860x-core.c:431: warning: ‘ret’ may be used
uninitialized in this function
It seems like the warning is valid if either pdata or pdata->touch is
NULL.This patch checks pdata and pdata->touch at the beginning of the
function. That means everything can be pulled in one indent level.
Now all the statements fit within the 80 character limit.Also at that point the "use_gpadc" variable isn't needed and removing
it simplifies the logic.Signed-off-by: Dan Carpenter
Acked-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz -
Fix typo error in LED resource of 88pm860x.
Signed-off-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz
28 May, 2010
1 commit
-
This patch fixes three section mismatches.
WARNING: drivers/mfd/88pm860x.o(.text+0x12): Section mismatch in
reference from the function pm860x_device_exit() to the function
.devexit.text:device_irq_exit()
The function pm860x_device_exit() references a function in an exit
section.
Often the function device_irq_exit() has valid usage outside the exit
section
and the fix is to remove the __devexit annotation of device_irq_exit.WARNING: drivers/mfd/88pm860x.o(.text+0xb0): Section mismatch in
reference from the function pm860x_device_init() to the function
.devinit.text:device_8606_init()
The function pm860x_device_init() references
the function __devinit device_8606_init().
This is often because pm860x_device_init lacks a __devinit
annotation or the annotation of device_8606_init is wrong.WARNING: drivers/mfd/88pm860x.o(.text+0xbe): Section mismatch in
reference from the function pm860x_device_init() to the function
.devinit.text:device_8607_init()
The function pm860x_device_init() references
the function __devinit device_8607_init().
This is often because pm860x_device_init lacks a __devinit
annotation or the annotation of device_8607_init is wrong.Signed-off-by: Henrik Kretzschmar
Signed-off-by: Samuel Ortiz
25 May, 2010
2 commits
-
A lot of condition comparision statements are used in original driver. These
statements are used to check the boundary of voltage numbers since voltage
number isn't linear.Now use array of voltage numbers instead. Clean code with simpler way.
Signed-off-by: Haojian Zhuang
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
Remove a lot of driver structures in 88pm860x driver. Make regulators share
one driver structure.Signed-off-by: Haojian Zhuang
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood
08 Mar, 2010
5 commits
-
Use genirq to simplify IRQ handling in 88pm860x. Remove the interface of
mask/free IRQs on 88pm860x. All these work is taken by genirq. Update the
touchscreen driver of 88pm860x since IRQ handling is changed.Signed-off-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz -
Append backlight, led & touch subdevs into 88pm860x driver.
Signed-off-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz -
88PM860x is a complex PMIC device. It contains touch, charger, sound, rtc,
backlight, led, and so on.Host communicates to 88PM860x by I2C bus. Use thread irq to support this
usage case.Signed-off-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz -
88PM8606 and 88PM8607 are two discrete chips used for power management.
Hardware designer can use them together or only one of them according to
requirement.There's some logic tightly linked between these two chips. For example, USB
charger driver needs to access both chips by I2C interface.Now share one driver to these two devices. Only one I2C client is identified
in platform init data. If another chip is also used, user should mark it in
companion_addr field of platform init data. Then driver could create another
I2C client for the companion chip.All I2C operations are accessed by 860x-i2c driver. In order to support both
I2C client address, the read/write API is changed in below.reg_read(client, offset)
reg_write(client, offset, data)The benefit is that client drivers only need one kind of read/write API. I2C
and MFD driver can be shared in both 8606 and 8607.Since API is changed, update API in 8607 regulator driver.
Signed-off-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz -
Create 88pm8607-i2c driver to support all I2C operation of 88PM8607.
Signed-off-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz