linux-toradex.git/drivers/mfd/lm3533-core.c, branch v3.8.13

mfd: remove use of __devexit

2012-11-28T20:22:27+00:00

CONFIG_HOTPLUG is going away as an option so __devexit is no
longer needed.

Signed-off-by: Bill Pemberton 
Cc: Srinidhi Kasagar 
Cc: Peter Tyser 
Cc: Daniel Walker 
Cc: Bryan Huntsman 
Acked-by: David Brown 
Acked-by: Linus Walleij 
Acked-by: Mark Brown 
Signed-off-by: Greg Kroah-Hartman

mfd: remove use of __devinit

2012-11-28T20:20:19+00:00

CONFIG_HOTPLUG is going away as an option so __devinit is no longer
needed.

Signed-off-by: Bill Pemberton 
Cc: Srinidhi Kasagar 
Cc: Peter Tyser 
Cc: Daniel Walker 
Cc: Bryan Huntsman 
Acked-by: David Brown 
Acked-by: Mark Brown 
Signed-off-by: Greg Kroah-Hartman

mfd: remove use of __devexit_p

2012-11-28T20:16:42+00:00

CONFIG_HOTPLUG is going away as an option so __devexit_p is no longer
needed.

Signed-off-by: Bill Pemberton 
Cc: Srinidhi Kasagar 
Cc: Peter Tyser 
Cc: Daniel Walker 
Cc: Bryan Huntsman 
Acked-by: David Brown 
Acked-by: Linus Walleij 
Acked-by: Mark Brown 
Signed-off-by: Greg Kroah-Hartman

mfd: core: Push irqdomain mapping out into devices

2012-09-15T21:22:04+00:00

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

mfd: Mark two lm3533 zone registers as volatile

2012-05-20T15:27:14+00:00

Mark the two currently unused zone registers as volatile in regmap for
completeness.

Signed-off-by: Johan Hovold 
Signed-off-by: Samuel Ortiz

mfd: Fix return type of lm533 attribute is_visible

2012-05-20T15:27:14+00:00

Since commit 587a1f1659 ("switch ->is_visible() to returning umode_t")
the return type of is_visible is umode_t rather than mode_t.

This silences a compiler warning on some architectures where these types
are not compatible.

Reported-by: Andrew Morton 
Signed-off-by: Johan Hovold 
Signed-off-by: Samuel Ortiz

mfd: Convert lm3533 to use devres

2012-05-20T15:27:08+00:00

Use devres to manage core driver data and regmap.

Signed-off-by: Johan Hovold 
Signed-off-by: Samuel Ortiz

mfd: Silence an lm3533 gcc warning

2012-05-20T15:27:04+00:00

This is supposed to be umode_t.  It causes a GCC warning:
drivers/mfd/lm3533-core.c:440:2: warning: initialization from incompatible pointer type [enabled by default]
drivers/mfd/lm3533-core.c:440:2: warning: (near initialization for ‘lm3533_attribute_group.is_visible’) [enabled by default]

Signed-off-by: Dan Carpenter 
Signed-off-by: Samuel Ortiz

mfd: Fix lm3533 regmap_update_bits() call

2012-05-20T15:27:02+00:00

Current code calls regmap_update_bits() with mask and val arguments swapped.

Signed-off-by: Axel Lin 
Acked-by: Johan Hovold 
Signed-off-by: Samuel Ortiz

mfd: Remove lm3533 boost attributes

2012-05-20T15:27:01+00:00

Remove boost-frequency and ovp attributes, which can be set through
platform data, from sysfs.

Signed-off-by: Johan Hovold 
Signed-off-by: Samuel Ortiz