04 Jan, 2009
10 commits
-
Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz -
The WM8351 is a WM8350 variant. As well as register default changes the
WM8351 has fewer voltage and current regulators than the WM8350.Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz -
Some WM8350 variants have fewer DCDCs and ISINKs. Identify these at
probe and refuse to use the absent DCDCs when running on these chips.Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz -
Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz -
The WM8352 is a variant of the WM8350. Aside from the register defaults
there are no software visible differences to the WM8350.Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz -
Since the WM8350 driver was originally written the semantics for the
identification registers of the chip have been clarified, allowing
us to do an exact match on all the fields. This avoids mistakenly
running on unsupported hardware.Also change to using the datasheet names more consistently for
legibility and fix a printk() that should be dev_err().Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz -
Rather than check for chip revisions in the WM8350 drivers have the core
code set flags for relevant differences.Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz -
The auxiliary ADC in the WM8350 is shared between several subdevices
so access to it needs to be arbitrated by the core driver.Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz -
No other software changes are required.
Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz -
Hopefully this will make the purpose of these functions a bit clearer,
it's not immediately obvious that the lock is a hardware feature.Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz
22 Oct, 2008
2 commits
-
This makes the contents of the cache clearer and fixes incorrect
initialisation of the cache for partially volatile registers.Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz -
October 10th linux-next build (powerpc allyesconfig) failed like this:
drivers/mfd/wm8350-core.c:1131: error: __ksymtab_wm8350_create_cache causes a section type conflict
Caused by commit 89b4012befb1abca5e86d232bc0e2a797b0d9825 ("mfd: Core
support for the WM8350 AudioPlus PMIC"). wm8350_create_cache is not used
elsewhere, so remove the EXPORT_SYMBOL.Signed-off-by: Stephen Rothwell
Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz
20 Oct, 2008
1 commit
-
NO_IRQ is only defined on some architectures - the general way to test
for an invalid IRQ in the modern kernel is by comparing with zero.Reported-by: Stephen Rothwell
Signed-off-by: Mark Brown
Signed-off-by: Samuel Ortiz
14 Oct, 2008
7 commits
-
Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz
Signed-off-by: Liam Girdwood -
In order to avoid merge problems further down the line add placeholders
for several of the WM8350 client devices and register them, otherwise
the patches adding the client devices will all try to update the same
code.Also remove redundant checks for null regulator platform devices while
we're at it.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz
Signed-off-by: Liam Girdwood -
Most of the subdevices for the WM8350 code are registered in the same
fashion so factor out the code to do the initial registration.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz
Signed-off-by: Liam Girdwood -
The WM8350 features six DCDC convertors (four buck and two boost), four
LDO voltage regulators and two constant current sinks. This driver adds
support for these through the regulator API.This driver was written by Liam Girdwood with updates for submission
from Mark Brown.Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
The WM8350 has an interrupt line to the CPU which is shared by the
devices on the CPU. This patch adds support for the interrupt
controller within the WM8350 which identifies which identifies the
interrupt cause. In common with other similar chips this is done
outside the standard interrupt framework due to the need to access
the interrupt controller over an interrupt-driven bus.This code was all originally written by Liam Girdwood with updates for
submission by me.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz
Signed-off-by: Liam Girdwood -
Some functions of the WM8350 require board-specific initialisation on
startup. Provide a callback to the WM8350 driver in platform data
for platforms to use to configure the chip. Use of a callback allows
platforms to control the ordering of initialisation which can be
important.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz
Signed-off-by: Liam Girdwood -
The WM8350 is an integrated audio and power management subsystem
intended for use as the primary PMIC in mobile multimedia applications.
The WM8350 can be controlled via either I2C or SPI - the control
interface is provided by a separate module in order to allow greatest
flexibility in configuring the kernel.This driver was originally written by Liam Girdwood and has since been
updated to current kernel APIs and split up for submission by me. All
the heavy lifting here was done by Liam.Signed-off-by: Mark Brown
Acked-by: Samuel Ortiz
Signed-off-by: Liam Girdwood