31 Jul, 2013
1 commit
-
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly.Signed-off-by: Jingoo Han
Signed-off-by: Lee Jones
13 Jun, 2013
1 commit
-
Signed-off-by: Lee Jones
Signed-off-by: Samuel Ortiz
12 Jun, 2013
1 commit
-
The MAX77686 clock driver has been in-tree for over 6 months, but never
actually enabled through the MFD registration before.Add it to the table so the device will probe and configure properly.
Signed-off-by: Olof Johansson
Signed-off-by: Samuel Ortiz
08 Apr, 2013
1 commit
-
'data' is a pointer and hence use NULL instead of 0.
Silences the following warning:
drivers/mfd/max77686.c:49:50: warning: Using plain integer as NULL pointerSigned-off-by: Sachin Kamat
Cc: Jonghwa Lee
Signed-off-by: Samuel Ortiz
22 Jan, 2013
1 commit
-
Current code uses max77686->dev in the dev_err call before setting it to
&i2c->dev. Fix it.Signed-off-by: Axel Lin
Signed-off-by: Samuel Ortiz
29 Nov, 2012
1 commit
-
CONFIG_HOTPLUG is going away as an option so __devinitdata is no
longer needed.Signed-off-by: Bill Pemberton
Cc: Srinidhi Kasagar
Cc: Peter Tyser
Acked-by: Linus Walleij
Signed-off-by: Greg Kroah-Hartman
16 Sep, 2012
1 commit
-
Currently the MFD core supports remapping MFD cell interrupts using an
irqdomain but only if the MFD is being instantiated using device tree
and only if the device tree bindings use the pattern of registering IPs
in the device tree with compatible properties. This will be actively
harmful for drivers which support non-DT platforms and use this pattern
for their DT bindings as it will mean that the core will silently change
remapping behaviour and it is also limiting for drivers which don't do
DT with this particular pattern. There is also a potential fragility if
there are interrupts not associated with MFD cells and all the cells are
omitted from the device tree for some reason.Instead change the code to take an IRQ domain as an optional argument,
allowing drivers to take the decision about the parent domain for their
interrupts. The one current user of this feature is ab8500-core, it has
the domain lookup pushed out into the driver.Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz
10 Jul, 2012
1 commit
-
This fixes below build warning if CONFIG_OF is not set.
CC drivers/mfd/max77686.o
drivers/mfd/max77686.c:37:42: warning: 'max77686_pmic_dt_match' defined but not used [-Wunused-variable]Signed-off-by: Axel Lin
Signed-off-by: Samuel Ortiz
09 Jul, 2012
4 commits
-
This patch adds device tree support for mfd driver and adds
Documentation/devicetree/bindings/mfd/max77686.txt.
This patch also intialize max77686 pointer to NULL in max77686_i2c_probe
to silent a compile time warning.Signed-off-by: Yadwinder Singh Brar
Reviwed-by: Mark Brown
Signed-off-by: Samuel Ortiz -
Presently driver expects irq_gpio pin in platform data and maps it to irq
itself. But we can also directly specify the interrupt in DT or platform file.Signed-off-by: Yadwinder Singh Brar
Signed-off-by: Samuel Ortiz -
Now this driver is using regmap API, the iolock mutex is not used and
can be removed.Signed-off-by: Axel Lin
Signed-off-by: Samuel Ortiz -
This patch is device driver for MAX77686 chip.
MAX77686 is PMIC and includes regulator and rtc on it.
This driver is core of MAX77686 chip, so provides common support for
accessing on-chip devices. It uses irq_domain to manage irq and regmap
to read/write data to its register with i2c bus.Signed-off-by: Chiwoong Byun
Signed-off-by: Jonghwa Lee
Signed-off-by: Myungjoo Ham
Signed-off-by: Kyungmin Park
Reviewed-by: Mark Brown
Signed-off-by: Samuel Ortiz
