From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: GPIO request failure with PCF pinmux
Date: Wed, 19 Sep 2012 15:33:56 +0000 [thread overview]
Message-ID: <20120919153356.GW13568@linux-sh.org> (raw)
In-Reply-To: <6045802.ynsOILKLIK@avalon>
On Wed, Sep 19, 2012 at 05:19:44PM +0200, Laurent Pinchart wrote:
> On Tuesday 18 September 2012 16:12:08 Paul Mundt wrote:
> > That's a bug, the pin has been reconfigured to a different mux type which
> > we should handle. At first glance, simply handling the input/output types
> > ought to work ok, but we may need more work than that. How does it go
> > with this?
>
> That seems to work, thank you. Will you push a patch ?
>
Yes, I'll send it off with the next batch of fixes. Thanks for testing!
next prev parent reply other threads:[~2012-09-19 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 20:11 GPIO request failure with PCF pinmux Laurent Pinchart
2012-09-14 20:36 ` Laurent Pinchart
2012-09-18 7:12 ` Paul Mundt
2012-09-18 7:22 ` Paul Mundt
2012-09-19 15:19 ` Laurent Pinchart
2012-09-19 15:33 ` Paul Mundt [this message]
2012-10-02 12:24 ` Laurent Pinchart
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=20120919153356.GW13568@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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).