linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Graeme Smecher <gsmecher@threespeedlogic.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Aaron Sierra <asierra@xes-inc.com>,
	Gregory CLEMENT <gregory.clement@free-electrons.com>,
	Maxime Ripard <maxime.ripard@free-electrons.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH 1/3] gpio: pca953x: Add devices to Kconfig help
Date: Wed, 12 Feb 2014 09:06:29 -0800	[thread overview]
Message-ID: <52FBAA15.80709@threespeedlogic.com> (raw)
In-Reply-To: <CACRpkdYbeeDi_xRudyyCmi2WLie_jpvhHLKGz5Jbr0a8T1rYLg@mail.gmail.com>

Hi all,

On 12/02/14 07:21 AM, Linus Walleij wrote:
> On Fri, Feb 7, 2014 at 11:35 PM, Aaron Sierra <asierra@xes-inc.com> wrote:
>
>> The pca953x driver supports tca6424 (24-bit) and pca9505 (40-bit)
>> devices. They were the only supported devices not mentioned in the
>> Kconfig help.
>>
>> Signed-off-by: Aaron Sierra <asierra@xes-inc.com>
> Can I get some help from the previous pca953x contributors
> to have a look at these new patches? An ACK or similar
> would be nice.

I've had a quick glance at the relevant datasheets and don't see any 
problems. The XRA1202 (added by patch) is explicitly compatible with the 
PCA9538 (already supported), and the datasheets for the PCA9698 (added 
by patch) and the PCA9505 (already supported) can be read side-by-side.

Acked-by: Graeme Smecher <gsmecher@threespeedlogic.com>

cheers,
Graeme

  reply	other threads:[~2014-02-12 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <972232456.119003.1391812066467.JavaMail.zimbra@xes-inc.com>
2014-02-07 22:35 ` [PATCH 1/3] gpio: pca953x: Add devices to Kconfig help Aaron Sierra
2014-02-12 15:21   ` Linus Walleij
2014-02-12 17:06     ` Graeme Smecher [this message]
2014-02-13 15:06     ` Gregory CLEMENT
2014-02-13 12:58   ` Linus Walleij

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=52FBAA15.80709@threespeedlogic.com \
    --to=gsmecher@threespeedlogic.com \
    --cc=asierra@xes-inc.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.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;
as well as URLs for NNTP newsgroup(s).