From: Lee Jones <lee.jones@linaro.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: sameo@linux.intel.com, patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] mfd: arizona: Correct handling of device tree gpio defaults
Date: Thu, 3 Oct 2013 16:49:08 +0100 [thread overview]
Message-ID: <20131003154908.GS9048@lee--X1> (raw)
In-Reply-To: <1380813361-15400-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>
On Thu, 03 Oct 2013, Charles Keepax wrote:
> 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,
>
> Sorry, your explanation is certainly fine with me.
>
> Thanks,
> Charles
>
> drivers/mfd/arizona-core.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Applied, thanks Charles.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2013-10-03 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 15:16 [PATCH v3] mfd: arizona: Correct handling of device tree gpio defaults Charles Keepax
2013-10-03 15:49 ` Lee Jones [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131003154908.GS9048@lee--X1 \
--to=lee.jones@linaro.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox