linux-toradex.git/drivers/mfd/htc-pasic3.c, branch v4.10

mfd: Constify struct mfd_cell where possible

2014-01-06T09:13:29+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: htc-pasic3: Convert to managed resources for allocating memory

2013-06-13T10:11:44+00:00

Signed-off-by: Lee Jones 
Signed-off-by: Samuel Ortiz

mfd: htc-pasic3: use module_platform_driver_probe()

2013-04-05T16:08:45+00:00

This patch uses module_platform_driver_probe() macro which makes
the code smaller and simpler.

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

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

w1: ds1wm: add a reset recovery parameter

2011-07-09T04:14:44+00:00

This fixes a regression in 3.0 reported by Paul Parsons regarding the
removal of the msleep(1) in the ds1wm_reset() function:

: The linux-3.0-rc4 DS1WM 1-wire driver is logging "bus error, retrying"
: error messages on an HP iPAQ hx4700 PDA (XScale-PXA270):
:
: 
: Driver for 1-wire Dallas network protocol.
: DS1WM w1 busmaster driver - (c) 2004 Szabolcs Gyurko
: 1-Wire driver for the DS2760 battery monitor  chip  - (c) 2004-2005, Szabolcs Gyurko
: ds1wm ds1wm: pass: 1 bus error, retrying
: ds1wm ds1wm: pass: 2 bus error, retrying
: ds1wm ds1wm: pass: 3 bus error, retrying
: ds1wm ds1wm: pass: 4 bus error, retrying
: ds1wm ds1wm: pass: 5 bus error, retrying
: ...
:
: The visible result is that the battery charging LED is erratic; sometimes
: it works, mostly it doesn't.
:
: The linux-2.6.39 DS1WM 1-wire driver worked OK.  I haven't tried 3.0-rc1,
: 3.0-rc2, or 3.0-rc3.

This sleep should not be required on normal circuitry provided the
pull-ups on the bus are correctly adapted to the slaves.  Unfortunately,
this is not always the case.  The sleep is restored but as a parameter to
the probe function in the pdata.

[akpm@linux-foundation.org: coding-style fixes]
Reported-by: Paul Parsons 
Tested-by: Paul Parsons 
Signed-off-by: Jean-François Dagenais 
Cc: Evgeniy Polyakov 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

mfd: Pass htc-pasic3 led platform data through the cell platform_data

2011-05-26T17:45:01+00:00

Cc: Philipp Zabel 
Signed-off-by: Samuel Ortiz

w1: Use device platform_data to retrieve ds1wm platform bits

2011-05-26T17:45:00+00:00

With the addition of the platform device mfd_cell pointer, we can now
cleanly pass the sub device drivers platform data pointers through the
regular device platform_data one, and get rid of mfd_get_data().

Cc: Matt Reimer 
Cc: Philipp Zabel 
Signed-off-by: Samuel Ortiz

w1: Use mfd_data instead of driver_data for dsw1wm.c

2011-03-23T09:41:56+00:00

Use mfd_data for passing information from mfd drivers to mfd
clients.  The mfd_cell's driver_data field is being phased out.

Clients that were using driver_data now access .mfd_data
via mfd_get_data().  This changes ds1wm only; mfd drivers with
other cells are not modified, with the exception of led_cell.

The led_cell.driver_data line is dropped from htc-pasic3.c in this
patch as well.  It's not used in mainline (there's no leds-pasic3
platform driver), so it should be safe to take care of that here.

Signed-off-by: Andres Salomon 
Signed-off-by: Samuel Ortiz

mfd: mfd_cell is now implicitly available to htc-pasic3 drivers

2011-03-23T09:41:52+00:00

No need to explicitly set the cell's platform_data/data_size.

Signed-off-by: Andres Salomon 
Signed-off-by: Samuel Ortiz