From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Felipe Balbi <balbi@ti.com>,
George Cherian <george.cherian@ti.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: PCF857x and 16-bit GPIO expanders
Date: Wed, 18 Sep 2013 19:18:04 +0200 [thread overview]
Message-ID: <2356541.62QktiIBr5@avalon> (raw)
In-Reply-To: <CACRpkdYn8yaTyFJMaC3vK4kGrQsaZpAX=pyn5y33ers7QhQ_pg@mail.gmail.com>
On Wednesday 18 September 2013 13:16:27 Linus Walleij wrote:
> On Tue, Sep 17, 2013 at 9:07 PM, Felipe Balbi <balbi@ti.com> wrote:
> > has anyone ever successfully using gpio-pcf857x.c driver with 16-bit
> > gpio expanders ? We're having some issues here where toggling the last
> > gpio pin (gpio 15) on a PCF8575 device causes platform to hang and I
> > can't come up with any explanation of why would it hang...
>
> Bouncing the question to George, Laurent and Kuninori...
I've got a board with a PCF8575 chip, but it uses I/Os 8 to 14 only as far as
I know.
I can try toggling I/O 15, but that will need to wait until next week as I'm
currently travelling without access to the hardware.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-09-18 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 19:07 PCF857x and 16-bit GPIO expanders Felipe Balbi
2013-09-18 11:16 ` Linus Walleij
2013-09-18 17:18 ` Laurent Pinchart [this message]
2013-09-18 17:36 ` Felipe Balbi
2013-09-19 8:13 ` George Cherian
2013-09-19 12:07 ` Nishanth Menon
2013-09-19 12:20 ` George Cherian
2013-09-19 12:36 ` Nishanth Menon
2013-09-19 12:49 ` Felipe Balbi
2013-09-19 12:37 ` Mark Jackson
2013-09-19 12:44 ` Felipe Balbi
[not found] ` <523AF73D.5010106@ti.com>
2013-09-19 13:10 ` Felipe Balbi
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=2356541.62QktiIBr5@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=balbi@ti.com \
--cc=george.cherian@ti.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@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;
as well as URLs for NNTP newsgroup(s).