Factor out reading of specific device tree bindings into seperate
functions in preperation for adding more of them. Whilst we are at is
fixup a couple of small issues in the existing binding documentation.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
Documentation
Add device tree bindings for the pdata needed to configure the MICBIAS
generators.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
Documentation/devicetree/bindings/mfd/arizona.txt | 15
drivers/mfd/arizona-core.c| 25
Add device tree bindings for several of simpler microphone detection
pdata fields.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
Documentation/devicetree/bindings/mfd/arizona.txt | 23 +
drivers/mfd/arizona-core.c| 22
On Mon, Sep 23, 2013 at 03:36:36PM -0600, Stephen Warren wrote:
On 09/23/2013 12:30 PM, Charles Keepax wrote:
- - AVDD1-supply, DBVDD1-supply, DBVDD2-supply, DBVDD3-supply,
CPVDD-supply,
+ - AVDD-supply, DBVDD1-supply, DBVDD2-supply, DBVDD3-supply, CPVDD-supply,
That looks like
On Tue, Sep 24, 2013 at 12:28:32AM +0100, Mark Brown wrote:
On Mon, Sep 23, 2013 at 03:38:10PM -0600, Stephen Warren wrote:
On 09/23/2013 12:30 PM, Charles Keepax wrote:
+ - wlf,max-channels-clocked : The maximum number of channels to be
clocked on
+each AIF, useful for I2S
here using the of_compatible field on the mfd_cell.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
Hi,
Another issue with the Arizona bindings, I am not sure
exactly what the best approach is this patch seems like the
correct fix, but it does require a change to the binding
Mark,
What are your thoughts on this approach? I basically add a way to
specify in the DAPM regulator supply widget that the supply lives
on the parent rather than the current device. If you like it I
will send it in as a proper patch.
I had considered adding something like a recursive regulator
in the extcon driver.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/extcon/extcon-arizona.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/drivers/extcon/extcon-arizona.c b/drivers/extcon/extcon-arizona.c
index ec9a14e..178454d 100644
On Thu, Sep 26, 2013 at 06:58:43PM +0100, Mark Brown wrote:
I don't see why this would only be an issue for ASoC - it happens to
have more helpers for this right now than anything else but I'd hope
that at some point in the future we can get some of the common patterns
for holding regulators
On Sat, Sep 28, 2013 at 11:55:35PM +0100, Mark Brown wrote:
No, having the supplies bound to the parent is desired (especially given
that there isn't a child node) - it's the fact that you're bodging this
in the framework by just randomly peering at the parent device and
hoping it's an MFD
On Sun, Sep 29, 2013 at 06:52:36PM +0100, Mark Brown wrote:
On Sun, Sep 29, 2013 at 03:11:37PM +0100, Charles Keepax wrote:
There is currently only one other MFD driver (tps65910) which defines
the GPIOs on the main MFD node as we do in the Arizona driver and it
uses the 'hack' that I
We need to use the of_node from the main Arizona device as that
holds our configuration.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/gpio/gpio-arizona.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/gpio/gpio-arizona.c b
On Mon, Sep 30, 2013 at 08:37:30AM +0900, Chanwoo Choi wrote:
No, extcon-arizona driver don't currently support DT to get platform data.
I cannot find some dt function to parse data from dts file.
You have to implement extcon-arizona driver by using DT binding style
to get platform data. I
On Tue, Oct 01, 2013 at 08:04:09AM +0900, Chanwoo Choi wrote:
On 09/30/2013 06:52 PM, Charles Keepax wrote:
On Mon, Sep 30, 2013 at 08:37:30AM +0900, Chanwoo Choi wrote:
No, extcon-arizona driver don't currently support DT to get platform data.
I cannot find some dt function to parse data
of
function 'of_parse_phandle' [-Werror=implicit-function-declaration]
drivers/regulator/arizona-ldo1.c:213:2: error: implicit declaration of
function 'of_node_put' [-Werror=implicit-function-declaration]
Signed-off-by: Arnd Bergmann a...@arndb.de
Cc: Charles Keepax ckee
a...@arndb.de
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/regulator/arizona-micsupp.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/regulator/arizona-micsupp.c
b/drivers/regulator/arizona-micsupp.c
index b80ebbe..ce9aca5 100644
On Mon, Jun 09, 2014 at 04:03:14PM +0100, Richard Fitzgerald wrote:
-#define WM_ADSP2(wname, num) \
+#define WM_ADSP2_E(wname, num, event_fn) \
{.id = snd_soc_dapm_dai_link, .name = wname Preloader, \
- .reg = SND_SOC_NOPM, .shift = num, .event = wm_adsp2_early_event, \
+
On Mon, Jun 09, 2014 at 07:43:14PM +0100, Mark Brown wrote:
On Mon, Jun 09, 2014 at 04:04:35PM +0100, Richard Fitzgerald wrote:
Using the driver for the internal regulator to also control
the clock frequency of blocks inside the codec is an
unexpected side-effect for a regulator, and also
On Mon, May 19, 2014 at 08:47:05AM +0100, Lee Jones wrote:
We cannot register supply alias in mfd_add_device before calling
platform_add_device, for 2 reasons:
1) devm resources may not be registered before the (platform) drivers probe
method runs
2) The platform-dev's name must be
On Sun, May 18, 2014 at 03:49:13PM +0200, Hans de Goede wrote:
The mfd-core no longer registers the supply aliases, instead the platform
driver probe method must now call mfd_register_supply_aliases().
Signed-off-by: Hans de Goede hdego...@redhat.com
---
Acked-by: Charles Keepax ckee
On Mon, May 19, 2014 at 10:18:11AM +0200, Hans de Goede wrote:
Hi,
On 05/19/2014 09:48 AM, Charles Keepax wrote:
On Mon, May 19, 2014 at 08:47:05AM +0100, Lee Jones wrote:
We cannot register supply alias in mfd_add_device before calling
platform_add_device, for 2 reasons:
1) devm
Some output configurations can require a 50Mhz SYSCLK which requires
DCVDD to be 1.8V. This patch adds the registers necessary for
supporting this operational mode.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/wm8997-tables.c |2 ++
1 files changed, 2
on the CODEC device where as the MICVDD consumer is on
the Arizona device. Add a mapping as we do for the other regulators.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/arizona-core.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/arizona-irq.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mfd/arizona-irq.c b/drivers/mfd/arizona-irq.c
index 88758ab..17102f5 100644
--- a/drivers/mfd/arizona-irq.c
+++ b
We can use the bypass mode on the MICVDD reg for button detection, as
the comment in the code states, however the code was mistakenly
disabling bypass. This patch corrects this and allows bypass mode during
button detection.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
devm_input_allocate_device already sets the parent device to be that
passed to it, we also set this manually in arizona_extcon_probe. This
patch removes the redundant set from arizona_extcon_probe.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/extcon/extcon
From: Nikesh Oswal nikesh.os...@wolfsonmicro.com
Use extcon cable API instead of state API as it is much more
idiomatic.
Signed-off-by: Nikesh Oswal nikesh.os...@wolfsonmicro.com
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/extcon/extcon-arizona.c | 15
The higher levels of impedance have a higher minimum value than the
first level. As the same value was used for all levels, higher impedances
were reported with a very low level of accuracy. This patch applies the
approriate lower threshold for each level.
Signed-off-by: Charles Keepax ckee
-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
Cc: Charles Keepax ckee...@opensource.wolfsonmicro.com
Cc: Mark Brown broo...@kernel.org
Cc: Graeme Gregory g...@slimlogic.co.uk
Cc: Kishon Vijay Abraham I kis...@ti.com
Cc: Krzysztof Kozlowski k.kozlow...@samsung.com
---
drivers/extcon/extcon
On Fri, May 30, 2014 at 10:27:35AM +0900, Chanwoo Choi wrote:
Hi Charles,
On 05/30/2014 12:27 AM, Charles Keepax wrote:
The higher levels of impedance have a higher minimum value than the
first level. As the same value was used for all levels, higher impedances
were reported with a very
a define for the maximum value at each level to improve readability.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
Changes since v1:
- Added define for range maximum as per review comments
drivers/extcon/extcon-arizona.c | 15 ++-
1 files changed, 10 insertions
On Fri, May 30, 2014 at 06:49:03PM +0900, Chanwoo Choi wrote:
Hi Charles,
OK, Let me know about test result.
Thanks,
Chanwoo Choi
Yeah that seems to work fine here. For the Arizona bit you can
add:
Tested-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
Thanks,
Charles
.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/arizona-core.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c
index 7678e84..51c0110 100644
--- a/drivers/mfd/arizona-core.c
+++ b
As DCVDD is probably supplied by a child of the MFD device move its
disable to before we destroy the MFD children as the regulator likely
won't exist after that.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/arizona-core.c |4 +++-
1 files changed, 3
We don't want to trigger any PM runtime operations whilst we are tearing
down the driver, as things the suspend and resume callbacks rely on
might already have been destroyed. So disable PM runtime for the device
as the first step arizona_dev_exit.
Signed-off-by: Charles Keepax ckee
There are no Arizona devices with 3 core supplies but we define a fix
array with space for 3 core supplies. Lower the ARIZONA_MAX_CORE_SUPPLIES
define to 2, to save a few bytes.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
include/linux/mfd/arizona/core.h |2 +-
1
round although that will obviously require me to resend the
interrupt series.
Thanks,
Charles
Charles Keepax (5):
mfd: arizona: Disable PM runtime at start of driver removal
mfd: arizona: Disable DCVDD before we destroy the MFD
mfd: arizona: Don't use devres for DCVDD
mfd: arizona: Use
without devres to avoid
this issue.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/arizona-core.c |9 ++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c
index 48acac6..7678e84
-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/mfd-core.c | 33 +
include/linux/mfd/core.h |3 +++
2 files changed, 32 insertions(+), 4 deletions(-)
diff --git a/drivers/mfd/mfd-core.c b/drivers/mfd/mfd-core.c
index 2676492
Several of the cells depend on the regulators provided by the
arizona-micsupp and arizona-ldo1 cells. As such use the new remove_level
feature of the MFD core to ensure the regulators are destroyed after all
the other cells.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
The DCS_DAC_DONE and DCS_HP_DONE interrupts do not exist on the wm5110
version of the IP. This patch removes them from the regmap IRQ
structure.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/wm5110-tables.c |6 --
1 files changed, 0 insertions(+), 6
Some parts have a third ISRC, this patch adds handling for the under and
overclocked interrupts from this ISRC.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/arizona-core.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers/mfd
,
Charles
Charles Keepax (5):
mfd: wm5110: Remove non-existant interrupts
mfd: wm5110: Add in the output done interrupts
mfd: arizona: Rename thermal shutdown interrupt
mfd: wm5110: Add new interrupt register definitions
mfd: arizona: Add missing handling for ISRC3 under/overclocked
drivers
Newer versions of the IP introduce short circuit protection which will
also shutdown the speaker. Rename the interrupt and associated register
bits associated with thermal events to better fit the function and avoid
conflict with future interrupt additions.
Signed-off-by: Charles Keepax ckee
wm5110 has interrupts to signal that an output has fully enabled. This
patch adds in these interrupts although use is not made of them yet.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/wm5110-tables.c | 18 +
include/linux/mfd/arizona/core.h
=implicit-function-declaration]
drivers/regulator/arizona-ldo1.c:213:2: error: implicit declaration of function
'of_node_put' [-Werror=implicit-function-declaration]
Signed-off-by: Arnd Bergmann a...@arndb.de
Acked-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
Cc: Mark Brown broo
=implicit-function-declaration]
drivers/regulator/arizona-ldo1.c:213:2: error: implicit declaration of function
'of_node_put' [-Werror=implicit-function-declaration]
Signed-off-by: Arnd Bergmann a...@arndb.de
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
Hi,
Sorry forgot I
On Tue, May 13, 2014 at 12:58:45PM +0200, Krzysztof Kozlowski wrote:
mfd_add_devices() expects array of struct mfd_cell to be const.
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
Cc: Mark Brown broo...@linaro.org
Cc: patc...@opensource.wolfsonmicro.com
---
Acked-by: Charles
...@gmx.at
---
Acked-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
Thanks,
Charles
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
On Mon, Jun 16, 2014 at 05:42:42PM +0100, Lee Jones wrote:
On Mon, 09 Jun 2014, Richard Fitzgerald wrote:
Moving this control from being a side-effect of the LDO1
regulator driver to a specific exported function.
Signed-off-by: Richard Fitzgerald r...@opensource.wolfsonmicro.com
---
On Mon, Jun 16, 2014 at 05:48:58PM +0100, Mark Brown wrote:
On Mon, Jun 16, 2014 at 05:42:42PM +0100, Lee Jones wrote:
On Mon, 09 Jun 2014, Richard Fitzgerald wrote:
+ if (arizona-subsys_max_rq != new_flags) {
I don't really get this. What's the point in passing the mask
parameter -
.
This patch corrects the situation, by adding the missing
readables/defaults.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/wm8994-regmap.c | 64 +++
1 file changed, 64 insertions(+)
diff --git a/drivers/mfd/wm8994
On Tue, Jun 17, 2014 at 03:54:20PM +0100, Lee Jones wrote:
On Mon, 02 Jun 2014, Charles Keepax wrote:
Several of the cells depend on the regulators provided by the
arizona-micsupp and arizona-ldo1 cells. As such use the new remove_level
feature of the MFD core to ensure the regulators
On Tue, Jun 17, 2014 at 03:36:10PM +0100, Lee Jones wrote:
On Mon, 02 Jun 2014, Charles Keepax wrote:
Currently the Arizona core uses a devm_regulator_get against its own
device node to obtain DCVDD. The Arizona core is an MFD device and DCVDD
is usually supplied by a child node (arizona
-by: Jingoo Han jg1@samsung.com
---
For the Arizona bit:
Acked-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
Thanks,
Charles
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
, this needs further debugging but the hookup here
should be correct and the problem should be else where.
The USBCLK case has been dropped because this requires the USB PHY to be
enabled.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/clk/samsung/clk-s3c64xx.c |6
On Mon, Jun 02, 2014 at 10:01:17PM +0100, Mark Brown wrote:
On Mon, Jun 02, 2014 at 10:01:43AM +0100, Charles Keepax wrote:
Sometimes MFD children will have interdependancies. For example an MFD
device might contain a regulator cell and another cell which requires
that regulator to function
Expose some DSP registers which are useful for DSP users to be able to
access whilst debugging their firmware.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/wm5110-tables.c | 168 +
include/linux/mfd/arizona
Expose some DSP registers which are useful for DSP users to be able to
access whilst debugging their firmware.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/wm5102-tables.c | 34 +
include/linux/mfd/arizona
@samsung.com
Cc: Russell King li...@arm.linux.org.uk
Cc: patc...@opensource.wolfsonmicro.com
Cc: linux-arm-ker...@lists.infradead.org
Signed-off-by: Paul Gortmaker paul.gortma...@windriver.com
---
Tested-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
Thanks,
Charles
--
To unsubscribe from
Evaluation of revision D of WM5110 suggests updates to the register
patch for optimal performance. For the sake of clarity rev C of the chip
does not require a register patch.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/wm5110-tables.c | 30
Add controls to enable/disable the headphone short circuit protection of
the headphone outputs.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
sound/soc/codecs/wm5110.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/sound/soc/codecs/wm5110.c
Add the registers necessary to enable/disable the headphone short
circuit protection.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/wm5110-tables.c |6 ++
include/linux/mfd/arizona/registers.h | 27 +++
2 files
On Wed, Jan 08, 2014 at 10:36:53PM +0100, Daniel Matuschek wrote:
Signed-off-by: Daniel Matuschek dan...@matuschek.net
snip
pll_div-freqmode = post_table[i].freqmode;
- pll_div-mclkdiv = post_table[i].mclkdiv;
- target *=
Add the registers necessary to enable/disable the headphone short
circuit protection.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/wm5110-tables.c |6 ++
include/linux/mfd/arizona/registers.h | 27 +++
2 files
Add controls to enable/disable the headphone short circuit protection of
the headphone outputs.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
sound/soc/codecs/wm5110.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/sound/soc/codecs/wm5110.c
. e.g.
192kHz and 96kHz use 24.576MHz master clock. The only
difference is the MCLK divider.
Signed-off-by: Daniel Matuschek dan...@matuschek.net
Acked-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
Sorry about the slight delay travelling with limited internet at
the mo.
Thanks
...@linaro.org
---
Acked-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
Thanks,
Charles
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
Certain use-cases require the DRE to be disabled so expose registers
necessary to control the DRE enables.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/wm5110-tables.c |2 ++
include/linux/mfd/arizona/registers.h |4
2 files changed, 6
Certain use-cases require the DRE to be disabled so expose controls for
the enables.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
sound/soc/codecs/wm5110.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/sound/soc/codecs/wm5110.c b/sound
structure.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/regulator/of_regulator.c |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/of_regulator.c b/drivers/regulator/of_regulator.c
index ea4f36f..c58c8d1 100644
the regulator is
registered and an of_node_put when it is unregistered in the core. This
means individual drivers are free to put their of_node references at the
end of probe letting the regulator core handling it from there. This
simplifies code on the driver side.
Signed-off-by: Charles Keepax ckee
As of_regulator_match will take an of_node reference to each matched
regulator, it makes sense to provide a helper to put all those
references. This patch does that.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/regulator/of_regulator.c | 21
On Thu, Apr 03, 2014 at 10:50:27PM +0100, Mark Brown wrote:
On Thu, Apr 03, 2014 at 03:32:15PM +0100, Charles Keepax wrote:
Currently, of_regulator_match does not increment the reference count of
the of_nodes it takes new references to. This could cause the node
pointer held to be invalid
Fix a typo from my patch adding of_regulator_put_match in the patch:
regulator: core: Add helper to put of_nodes from matches
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
include/linux/regulator/of_regulator.h |2 +-
1 files changed, 1 insertions(+), 1 deletions
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/arizona-irq.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mfd/arizona-irq.c b/drivers/mfd/arizona-irq.c
index 88758ab..17102f5 100644
--- a/drivers/mfd/arizona-irq.c
+++ b
in mfd_remove_devices_fn.
Reported-by: Carlo Caione ca...@caione.org
Reported-by: Mark Brown broo...@kernel.org
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/mfd-core.c | 11 +++
1 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/drivers/mfd
Some of the OF handling functions do not have empty alternatives defined
if CONFIG_OF is not defined. This patch ifdefs out the offending code.
Reported-by: Randy Dunlap rdun...@infradead.org
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/regulator/arizona
Some of the OF handling functions do not have empty alternatives defined
if CONFIG_OF is not defined. This patch ifdefs out the offending code.
Reported-by: Randy Dunlap rdun...@infradead.org
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/regulator/arizona-ldo1.c
On Fri, Apr 25, 2014 at 05:11:38PM +0100, Mark Brown wrote:
On Fri, Apr 25, 2014 at 04:55:40PM +0100, Charles Keepax wrote:
Some of the OF handling functions do not have empty alternatives defined
if CONFIG_OF is not defined. This patch ifdefs out the offending code.
Which functions
On Mon, Apr 21, 2014 at 09:02:20PM +0900, Chanwoo Choi wrote:
This patch use devm_extcon_dev_allocate() to simplify the memory control
of extcon device.
Cc: Charles Keepax ckee...@opensource.wolfsonmicro.com
Cc: Mark Brown broo...@kernel.org
Cc: patc...@opensource.wolfsonmicro.com
Signed
.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/regulator/of_regulator.c | 47 +--
include/linux/regulator/of_regulator.h |7 -
2 files changed, 26 insertions(+), 28 deletions(-)
diff --git a/drivers/regulator
On Tue, Apr 15, 2014 at 11:25:27AM +0100, Lee Jones wrote:
On Tue, 01 Apr 2014, Charles Keepax wrote:
This patch factors out the reading of GPIOs for the Arizona devices
into a helper function.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd
On Tue, Apr 15, 2014 at 11:12:00AM +0100, Lee Jones wrote:
On Tue, 01 Apr 2014, Charles Keepax wrote:
It is more idiomatic to process things relating to the regulator in its
driver. This patch moves both processing of device tree relating to the
regulator and checking if the regulator
This patch factors out the reading of GPIOs for the Arizona devices
into a helper function.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/arizona-core.c | 31 ++-
include/linux/mfd/arizona/core.h |3 +++
2 files changed
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
Documentation/devicetree/bindings/mfd/arizona.txt |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt
b/Documentation/devicetree/bindings/mfd
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/regulator/arizona-micsupp.c | 37 +++
1 files changed, 37 insertions(+), 0 deletions(-)
diff --git a/drivers/regulator/arizona-micsupp.c
b/drivers/regulator/arizona-micsupp.c
index
on comments by Lee Jones
Thanks,
Charles
Charles Keepax (6):
mfd: arizona: Factor out read of device tree GPIOs
regulator: arizona-ldo1: Move setup processing from arizona-core
regulator: arizona-ldo1: Add processing of init_data from device tree
mfd: arizona: Update DT binding to support LDO1
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/regulator/arizona-ldo1.c | 34 --
1 files changed, 32 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/arizona-ldo1.c b/drivers/regulator/arizona-ldo1.c
index 2248733
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
Documentation/devicetree/bindings/mfd/arizona.txt |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt
b/Documentation/devicetree/bindings/mfd
It is more idiomatic to process things relating to the regulator in its
driver. This patch moves both processing of device tree relating to the
regulator and checking if the regulator is external from arizona-core
into the regulator driver.
Signed-off-by: Charles Keepax ckee
The isolation control register is required when DCVDD is externally
supplied add this in as a readable register.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/wm5110-tables.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/mfd
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
Documentation/devicetree/bindings/mfd/arizona.txt |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt
b/Documentation/devicetree/bindings/mfd
binding documention factored out into a seperate
patch as requested.
Thanks,
Charles
Charles Keepax (6):
mfd: arizona: Factor out read of device tree GPIOs
regulator: arizona-ldo1: Move setup processing from arizona-core
regulator: arizona-ldo1: Add processing of init_data from device tree
This patch factors out the reading of GPIOs for the Arizona devices
into a helper function.
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/mfd/arizona-core.c | 33 -
include/linux/mfd/arizona/core.h |3 +++
2 files
It is more idiomatic to process things relating to the regulator in its
driver. This patch moves both processing of device tree relating to the
regulator and checking if the regulator is external from arizona-core
into the regulator driver.
Signed-off-by: Charles Keepax ckee
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
Documentation/devicetree/bindings/mfd/arizona.txt |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/mfd/arizona.txt
b/Documentation/devicetree/bindings/mfd
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/regulator/arizona-ldo1.c | 47 +++--
1 files changed, 44 insertions(+), 3 deletions(-)
diff --git a/drivers/regulator/arizona-ldo1.c b/drivers/regulator/arizona-ldo1.c
index 211af83
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/regulator/arizona-micsupp.c | 53 +++
1 files changed, 53 insertions(+), 0 deletions(-)
diff --git a/drivers/regulator/arizona-micsupp.c
b/drivers/regulator/arizona-micsupp.c
index
Signed-off-by: Charles Keepax ckee...@opensource.wolfsonmicro.com
---
drivers/regulator/arizona-micsupp.c | 53 +++
1 files changed, 53 insertions(+), 0 deletions(-)
diff --git a/drivers/regulator/arizona-micsupp.c
b/drivers/regulator/arizona-micsupp.c
index
201 - 300 of 3151 matches
Mail list logo
