From: Graeme Smecher <gsmecher@threespeedlogic.com>
To: Grant Likely <grant.likely@linaro.org>
Cc: Haojian Zhuang <haojian.zhuang@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpio: pca953x: Don't flip bits on PCA957x GPIO expanders when probing them.
Date: Mon, 09 Sep 2013 11:14:42 -0700 [thread overview]
Message-ID: <522E1012.7060101@threespeedlogic.com> (raw)
In-Reply-To: <CAN1soZy98mM6aAyASDY8Ra+j-2Jsr8RDvuqU8vHBnVBNgjWx9w@mail.gmail.com>
Hi Grant,
On 04/08/13 05:35 AM, Haojian Zhuang wrote:
> On Sat, Aug 3, 2013 at 5:24 AM, Graeme Smecher
> <gsmecher@threespeedlogic.com> wrote:
>> The pca957x driver supports a handful of I2C GPIO expanders from NXP, Maxim,
>> and TI. For the PCA9574 and PCA9575 devices only, the driver resets the GPIO
>> level and direction in the pca957x_probe function. This seems like the wrong
>> thing to do, since it can cause hardware bit twiddles during warm reboots when
>> the chip state and reset values don't match.
>>
>> This kind of initialization is best left upstream (in a bootloader) or
>> downstream (in userspace). It's also an inconsistency across devices supported
>> by this driver.
>>
>> Signed-off-by: Graeme Smecher<gsmecher@threespeedlogic.com>
>> Cc: Grant Likely<grant.likely@linaro.org>
>> Cc: Haojian Zhuang<haojian.zhuang@marvell.com>
>> ---
>> drivers/gpio/gpio-pca953x.c | 11 -----------
>> 1 file changed, 11 deletions(-)
>>
>> diff --git a/drivers/gpio/gpio-pca953x.c b/drivers/gpio/gpio-pca953x.c
>> index 426c51d..47c08d8 100644
>> --- a/drivers/gpio/gpio-pca953x.c
>> +++ b/drivers/gpio/gpio-pca953x.c
>> @@ -683,17 +683,6 @@ static int device_pca957x_init(struct pca953x_chip *chip, u32 invert)
>> int ret;
>> u8 val[MAX_BANK];
>>
>> - /* Let every port in proper state, that could save power */
>> - memset(val, 0, NBANK(chip));
>> - pca953x_write_regs(chip, PCA957X_PUPD, val);
>> - memset(val, 0xFF, NBANK(chip));
>> - pca953x_write_regs(chip, PCA957X_CFG, val);
>> - memset(val, 0, NBANK(chip));
>> - pca953x_write_regs(chip, PCA957X_OUT, val);
>> -
>> - ret = pca953x_read_regs(chip, PCA957X_IN, val);
>> - if (ret)
>> - goto out;
>> ret = pca953x_read_regs(chip, PCA957X_OUT, chip->reg_output);
>> if (ret)
>> goto out;
>> --
>> 1.7.10.4
>>
> Acked-by: Haojian Zhuang<haojian.zhuang@gmail.com>
Just a quick ping: I think you're the responsible maintainer for this
patch, and I haven't seen it show up on git.secretlab.ca. Do you want me
to resubmit with Haojian's e-mail corrected?
I should also note that this patch is NOT boot-tested. My hardware
containing this part is only supported by the vendor's aging 2.6.37
branch. (It's a custom ARM board using the TI AM3874.) The pca953x
driver has evolved enough that the patches for 2.6.37 and mainline
aren't identical, but they still rhyme.
thanks,
Graeme
prev parent reply other threads:[~2013-09-09 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 21:24 [PATCH] gpio: pca953x: Don't flip bits on PCA957x GPIO expanders when probing them Graeme Smecher
2013-08-04 12:35 ` Haojian Zhuang
2013-09-09 18:14 ` Graeme Smecher [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=522E1012.7060101@threespeedlogic.com \
--to=gsmecher@threespeedlogic.com \
--cc=grant.likely@linaro.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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