linux-toradex.git/include/linux/mfd/wm831x, branch T20_LinuxImageV2.0_20130305

mfd: Support software initiated shutdown of WM831x PMICs

2011-09-20T12:02:09+00:00

In systems where there is no hardware signal from the processor to the
PMIC to initiate the final power off sequence we must initiate the
shutdown with a register write to the PMIC. Support such systems in the
driver. Since this may prevent a full shutdown of the system platform
data is used to enable the feature.

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

mfd: Convert WM831x to use regmap API

2011-08-22T11:23:22+00:00

Factor out the register read/write code to use the register map API.  We
still need some wm831x specific code and locking in place to check that
the user key is handled correctly but only on the write side, reads are
not affected by the key.

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

mfd: Add WM831x clock control register definitions

2011-07-31T21:28:24+00:00

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

mfd: Support multiple active WM831x AUXADC conversions

2011-07-31T21:28:20+00:00

The WM831x AUXADC hardware can schedule multiple conversions at once,
allowing higher performance when more than one source is in use as we
can have the hardware start new conversions without having to wait for
a register write.

Take advantage of this in the interrupt driven case, maintaining a list of
callers that are waiting for AUXADC conversions and completing them all
simultaneously. The external interface of the AUXADC is not changed so
there will be limited use of the feature immediately.

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

mfd: Read wm831x AUXADC conversion results before acknowledging interrupt

2011-07-31T21:28:20+00:00

Ensure that there's no possibility of loosing an AUXADC interrupt by reading
the conversion result in the IRQ handler when using interrupts. Otherwise
it's possible that under very heavy load a new conversion could be initiated
before the acknowledgement for a previous interrupt has happened.

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

mfd: Support dynamic allocation of IRQ range for wm831x

2011-07-31T21:28:19+00:00

Use irq_allocate_desc() to get the IRQ range, which turns into a noop on
non-sparse systems. Since all existing users are non-sparse there should
be no compatibility issues.

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

mfd: Allow touchscreen to be disabled on wm831x devices

2011-07-31T21:28:19+00:00

Allow platform data to flag the touchscreen as disabled so that if the
touch driver is built in we don't end up causing lots of work by spuriously
detecting touchscreen activity on systems where it isn't in use.

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

mfd: Fix bus lock interaction for WM831x IRQ set_type() operation

2011-07-31T21:28:19+00:00

The WM831x IRQ set_type() operation is doing a direct register write when
called but since set_type() is called with the bus lock held this isn't
legal and could cause deadlocks in the IRQ core.

Fix this by posting the updates into an array and syncing in the
bus_sync_unlock() callback.

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

mfd: Provide platform data for WM831x GPIO configuration

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

Allow the GPIO mode of WM831x devices to be configured using platform data.
Users may provide a table of GPIO register values in gpio_defaults[]. In
order to allow 0 to be set explicitly out of range values are accepted and
masked off, with a WM831X_GPIO_CONFIGURE define provided to set an out of
range value.

This can be used to configure higher numbered GPIOs or override values set
in OTP for GPIOs configured using OTP.

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

mfd: Remove compatibility interface for WM831x specific IRQ API

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

The last user was removed in the merge window.

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