13 Dec, 2011
18 commits
-
Factor out the irq_chip implementation, substantially reducing the code
size for the driver.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz -
…e/regmap into wm8994-mfd
-
For later chip revisions the WM1811 GPIO6 register is always volatile so
store the device revision when initialising the driver and then check at
runtime if we're running on a newer device.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz -
struct wm8994 includes a mutex so we need to include mutex.h before we
declare it. All current users rely on this being done implicitly.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz -
The WM1811A is a variant of the WM1811 with pin configuration changes.
Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz -
As WM1811 revision C was transparent to software the revision IDs for
subsequent revisions are one less than they would normally be. Correct
for this in log messages.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz -
The driver has no need to modify the regulator_init_data so declare it
const to allow machine code to do so.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz -
The different devices handled by the WM8994 can be distinguished using
their ID registers so we don't need to rely on the user having registered
the device correctly. Instead do the initial regmap setup with a minimal
configuration only supporting physical I/O and then configure the cache
once we have identified the device.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz -
As part of this we provide information about the registers that exist in
the device to the regmap core, drop the small amount of cache that the
core had been using and let regmap do the sync.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz -
Describe the register map to the regmap core so that we can use its
diagnostic features and cache support. This is split out from the patch
using it due to the size so that the actual code change is a bit clearer.As the various devices are supersets of each other the access maps are
built up by layering the functions on top of each other, though the
interface for specifying the register defaults isn't currently amenable
to this.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz -
Add a bunch of definitions for wm8994 registers that are not currently
used by software.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz -
Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz -
Disable more pulls by default on WM8994 for a small current saving. Since
some designs do leave SPKMODE floating provide platform data to allow that
to be left enabled.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz -
Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz -
Add a placeholder device tree binding for the wm8994 driver. At present
the binding is essentially null as none of the platform data is supported,
and at least some of that will depend on the pending regulator bindings.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz -
Signed-off-by: Mark Brown
Acked-by: Samuel Oritz
12 Dec, 2011
5 commits
-
This driver can be built as module and the file header indicates that
the driver is published under the GPL.
Thus add MODULE_LICENSE("GPL") for it.Signed-off-by: Axel Lin
Acked-by: Sascha Hauer
Signed-off-by: Mark Brown -
To support advanced system functionality for additional components; the
actively used clocks will remain the same for current components. Also
factor the rate out to a single #define while we're at it.Signed-off-by: Mark Brown
-
Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
Signed-off-by: Jonathan Neuschäfer
Signed-off-by: Mark Brown
11 Dec, 2011
6 commits
-
Conflicts:
sound/soc/mxs/mxs-pcm.c -
The message was obviously copied from soc_init_codec_debugfs()
Signed-off-by: Lothar Waßmann
Signed-off-by: Mark Brown -
Signed-off-by: Lothar Waßmann
Acked-by: Wolfram Sang
Signed-off-by: Mark Brown -
The sound driver refuses to load as module, because of the missing
MODULE_LICENSE("GPL").
The file header indicates that the driver is indeed published under
the GPL.Signed-off-by: Lothar Waßmann
Acked-by: Wolfram Sang
Signed-off-by: Mark Brown -
Record the clock after the divider as that is what all SYSCLK users see.
Without this the other clock configuration in the device comes out at
half rate.Signed-off-by: Mark Brown
Cc: stable@kernel.org
09 Dec, 2011
7 commits
-
Signed-off-by: Mark Brown
-
Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
Signed-off-by: Mark Brown
-
Signed-off-by: Mark Brown
-
The device only supports SPI.
Signed-off-by: Mark Brown
-
Signed-off-by: Mark Brown
-
Transform some loops from:
for_each(x) {
if (f(x)) {
work_on(x);
}
}to new structure:
for_each(x) {
if (!f(x))
continue;work_on(x);
}This will allow future modification of f(x) with less impact to the code.
Signed-off-by: Stephen Warren
Acked-by: Liam Girdwood
Signed-off-by: Mark Brown
08 Dec, 2011
4 commits
-
Move DAS routing setup into the DAS driver itself. This removes the need
to duplicate this in each machine driver, of which we'll soon have three.An added advantage is that the machine drivers no longer call the Tegra20-
specific DAS functions by name, so the machine driver no longer needs to
be split up into Tegra20 and Tegra30 versions.If individual machine drivers need a different routing setup to this
default, they can still call the DAS functions to set that up.Long-term, DAS will be a codec driver, and user-space will be able to
control its routing, possibly within constraints that the machine driver
sets up. Configuring the DAS routing from the DAS driver is a very slight
move in that direction.Signed-off-by: Stephen Warren
Signed-off-by: Mark Brown -
Use snd_soc_update_bits for read-modify-write register access instead of
open-coding it using snd_soc_read and snd_soc_writeSigned-off-by: Axel Lin
Signed-off-by: Mark Brown -
No need to do this in the driver now.
Signed-off-by: Mark Brown
-
As for PCMs take a runtime power management reference to devices that are
in a non-off bias, avoiding the need to do this in individual drivers.Signed-off-by: Mark Brown