* [PATCH v2] mfd: arizona: Correct handling of device tree gpio defaults
@ 2013-10-03 12:30 Charles Keepax
2013-10-03 13:39 ` Lee Jones
0 siblings, 1 reply; 2+ messages in thread
From: Charles Keepax @ 2013-10-03 12:30 UTC (permalink / raw)
To: lee.jones; +Cc: sameo, patches, linux-kernel, Charles Keepax
When settings the gpio defaults from data contained in device tree
all values that fit in 16-bits should be treated literally, any
value greater than 16-bits should cause the chips default to be used
for that gpio pin. A zero value in the gpio default array in pdata
represents that we should leave the default set.
The current code will write zero to the gpio config for all values
greater than 16-bits. Note that this is setting the gpio default to
0x10000, as only the bottom 16-bits will be written to the device, and
zero is treated as don't write anything use chip defaults.
This patch ensure that we handle the gpio default as either an out of
range value or a zero value rather than both one after the other.
Reported-by: Heather Lomond <heather.lomond@wolfsonmicro.com>
Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
---
Hi,
Added a bit more explanation I hope this is a little clearer.
Thanks,
Charles
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 5ac3aa4..e13355b 100644
--- a/drivers/mfd/arizona-core.c
+++ b/drivers/mfd/arizona-core.c
@@ -540,7 +540,7 @@ static int arizona_of_get_core_pdata(struct arizona *arizona)
for (i = 0; i < ARRAY_SIZE(arizona->pdata.gpio_defaults); i++) {
if (arizona->pdata.gpio_defaults[i] > 0xffff)
arizona->pdata.gpio_defaults[i] = 0;
- if (arizona->pdata.gpio_defaults[i] == 0)
+ else if (arizona->pdata.gpio_defaults[i] == 0)
arizona->pdata.gpio_defaults[i] = 0x10000;
}
} else {
--
1.7.2.5
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH v2] mfd: arizona: Correct handling of device tree gpio defaults
2013-10-03 12:30 [PATCH v2] mfd: arizona: Correct handling of device tree gpio defaults Charles Keepax
@ 2013-10-03 13:39 ` Lee Jones
0 siblings, 0 replies; 2+ messages in thread
From: Lee Jones @ 2013-10-03 13:39 UTC (permalink / raw)
To: Charles Keepax; +Cc: sameo, patches, linux-kernel
On Thu, 03 Oct 2013, Charles Keepax wrote:
> When settings the gpio defaults from data contained in device tree
> all values that fit in 16-bits should be treated literally, any
> value greater than 16-bits should cause the chips default to be used
> for that gpio pin. A zero value in the gpio default array in pdata
> represents that we should leave the default set.
>
> The current code will write zero to the gpio config for all values
> greater than 16-bits. Note that this is setting the gpio default to
> 0x10000, as only the bottom 16-bits will be written to the device, and
> zero is treated as don't write anything use chip defaults.
>
> This patch ensure that we handle the gpio default as either an out of
> range value or a zero value rather than both one after the other.
This still doesn't clarify things for me. How about:
When setting GPIO defaults we are required to make a distinction
between writing 0x0000 to the registers and leaving them untouched.
When we receive between 0x0000 and 0xFFFF (inclusive) from either
Platform Data or Device Tree, we should write the provided
configuration to the device. Conversely, when we receive >0xFFFF we
should leave the device configuration at its default setting.
This patch fixes a bug and ensures that configuration 0x0000 isn't
mistakenly written when the intention was to keep the default one.
> Reported-by: Heather Lomond <heather.lomond@wolfsonmicro.com>
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
>
> Hi,
>
> Added a bit more explanation I hope this is a little clearer.
>
> Thanks,
> Charles
>
> 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 5ac3aa4..e13355b 100644
> --- a/drivers/mfd/arizona-core.c
> +++ b/drivers/mfd/arizona-core.c
> @@ -540,7 +540,7 @@ static int arizona_of_get_core_pdata(struct arizona *arizona)
> for (i = 0; i < ARRAY_SIZE(arizona->pdata.gpio_defaults); i++) {
> if (arizona->pdata.gpio_defaults[i] > 0xffff)
> arizona->pdata.gpio_defaults[i] = 0;
> - if (arizona->pdata.gpio_defaults[i] == 0)
> + else if (arizona->pdata.gpio_defaults[i] == 0)
> arizona->pdata.gpio_defaults[i] = 0x10000;
> }
> } else {
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-10-03 13:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-03 12:30 [PATCH v2] mfd: arizona: Correct handling of device tree gpio defaults Charles Keepax
2013-10-03 13:39 ` Lee Jones
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox