linux-toradex.git/drivers/mfd/mfd-core.c, branch PD13.0.0alpha

mfd: Add platform data pointer back

2011-05-26T17:44:56+00:00

Now that we have a way to pass MFD cells down to the sub drivers,
we can gradually get rid of mfd_data by putting the platform pointer
back in place.

Signed-off-by: Samuel Ortiz

mfd: Fetch cell pointer from platform_device->mfd_cell

2011-04-12T09:13:00+00:00

In order for MFD drivers to fetch their cell pointer but also their
platform data one, an mfd cell pointer is added to the platform_device
structure.
That allows all MFD sub devices drivers to be MFD agnostic, unless
they really need to access their MFD cell data. Most of them don't,
especially the ones for IPs used by both MFD and non MFD SoCs.

Cc: Grant Likely 
Acked-by: Greg KH 
Signed-off-by: Samuel Ortiz

mfd: Add mfd_clone_cell(), convert cs5535-mfd/olpc-xo1 to it

2011-03-26T23:09:30+00:00

Replace mfd_shared_platform_driver_register with mfd_clone_cell.  The
former was called by an mfd client, and registered both a platform driver
and device.  The latter is called by an mfd driver, and registers only a
platform device.

The downside of this is that mfd drivers need to be modified whenever
new clients are added that share a cell; the upside is that it fits
Linux's driver model better.  It's also simpler.

This also converts cs5535-mfd/olpc-xo1 from the old API.  cs5535-mfd
now creates the olpc-xo1-{acpi,pms} devices, while olpc-xo1 binds to
them via platform drivers.

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

mfd: Rename mfd_shared_cell_{en,dis}able to drop the "shared" part

2011-03-23T09:42:03+00:00

As requested by Samuel, there's not really any reason to have "shared"
in the name.

This also modifies the only user of the function, as well.

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

mfd: add platform_device sharing support for mfd

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

This adds functions to enable platform_device sharing for mfd clients.

Each platform driver (mfd client) that wants to share an mfd_cell's
platform_device uses the mfd_shared_platform_driver_{un,}register()
functions instead of platform_driver_{un,}register().  Along with
registering the platform driver, these also register a new platform
device with the same characteristics as the original cell, but a different
name.  Given an mfd_cell with the name "foo", drivers that want to
share access to its resources can call mfd_shared_platform_driver_register
with platform drivers named (for example) "bar" and "baz".  This
will register two platform devices and drivers named "bar" and "baz"
that share the same cell as the platform device "foo".  The drivers
can then call "foo" cell's enable hooks (or mfd_shared_cell_enable)
to enable resources, and obtain platform resources as they normally
would.

This deals with platform handling only; mfd driver-specific details,
hardware handling, refcounting, etc are all dealt with separately.

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

mfd: Add refcounting support to mfd_cells

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

This provides convenience functions for sharing of cells across
multiple mfd clients.  Mfd drivers can provide enable/disable hooks
to actually tweak the hardware, and clients can call
mfd_shared_cell_{en,dis}able without having to worry about whether
or not another client happens to have enabled or disabled the
cell/hardware.

Note that this is purely optional; drivers can continue to use
the mfd_cell's enable/disable hooks for their own purposes, if
desired.

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

mfd: Remove driver_data field from mfd_cell

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

All users of this have now been switched over to using mfd_data;
it can go away now.

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

mfd-core: Unconditionally add mfd_cell to every platform_device

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

Previously, one would set the mfd_cell's platform_data/data_size to point
to the current mfd_cell in order to pass that information along to drivers.

This causes the current mfd_cell to always be available to drivers.  It
also adds a wrapper function for fetching the mfd cell from a platform
device, similar to what originally existed for mfd devices.

Drivers who previously used platform_data for other purposes can still
use it; the difference is that mfd_get_data() must be used to
access it (and the pdata structure is no longer allocated in
mfd_add_devices).

Note that mfd_get_data is intentionally vague (in name) about where
the data is stored; variable name changes can come later without having
to touch brazillions of drivers.

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

mfd: Provide pm_runtime_no_callbacks flag in cell data

2011-01-14T11:37:42+00:00

Allow MFD cells to have pm_runtime_no_callbacks() called on them during
registration. This causes the runtime PM framework to ignore them,
allowing use of runtime PM to suspend the device as a whole even if
not all drivers for the MFD can usefully implement runtime PM. For
example, RTCs are likely to run continuously regardless of the power
state of the system.

Signed-off-by: Mark Brown 
Signed-off-by: Samuel Ortiz

mfd: Add devices platform data when the cell data size is not 0

2010-10-28T22:30:03+00:00

When the cell data_size is 0, the resulting platform_data pointer will be
set to ZERO_SIZE_PTR. That could be misleading for device drivers running
a NULL check on thei platform_data pointer before dereferencing it.

Signed-off-by: Brian Harring 
Signed-off-by: Samuel Ortiz