linux.git/drivers/mfd/intel_msic.c, branch v3.14

mfd: intel: Constify struct mfd_cell where possible

2014-01-06T09:13:28+00:00

As of commit 03e361b25ee8dfb1fd9b890072c23c4aae01c6c7 ("mfd: Stop setting
refcounting pointers in original mfd_cell arrays"), the "cell" parameter of
mfd_add_devices() is "const" again. Hence make all cell data passed to
mfd_add_devices() const where possible.

Signed-off-by: Geert Uytterhoeven 
Signed-off-by: Lee Jones

mfd: Use dev_get_platdata()

2013-07-31T12:01:29+00:00

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

mfd: intel_msic: Remove unnecessary platform_set_drvdata()

2013-06-11T17:27:51+00:00

The driver core clears the driver data to NULL after device_release
or on probe failure, since commit 0998d0631001288a5974afc0b2a5f568bcdecb4d
(device-core: Ensure drvdata = NULL when no driver is bound).
Thus, it is not needed to manually clear the device driver data to NULL.

Signed-off-by: Jingoo Han 
Acked-by: Lee Jones 
Acked-by: Mika Westerberg 
Signed-off-by: Samuel Ortiz

drivers/mfd: don't check resource with devm_ioremap_resource

2013-05-18T09:55:53+00:00

devm_ioremap_resource does sanity checks on the given resource. No need to
duplicate this in the driver.

Signed-off-by: Wolfram Sang

mfd: intel_msic: Use devm_gpio_request_one()

2013-04-08T15:25:24+00:00

Use devm_gpio_request_one() to make cleanup paths more simple.

Signed-off-by: Jingoo Han 
Signed-off-by: Samuel Ortiz

mfd: Convert to devm_ioremap_resource()

2013-01-25T20:21:47+00:00

Convert all uses of devm_request_and_ioremap() to the newly introduced
devm_ioremap_resource() which provides more consistent error handling.

devm_ioremap_resource() provides its own error messages so all explicit
error messages can be removed from the failure code paths.

Signed-off-by: Thierry Reding 
Cc: Samuel Ortiz 
Signed-off-by: Greg Kroah-Hartman

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