From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 00/05] sh: GPIO for SuperH using gpiolib
Date: Mon, 29 Sep 2008 11:44:02 +0000 [thread overview]
Message-ID: <20080929114402.GA24836@linux-sh.org> (raw)
In-Reply-To: <20080927181008.11246.53495.sendpatchset@rx1.opensource.se>
On Sun, Sep 28, 2008 at 03:10:08AM +0900, Magnus Damm wrote:
> Pinmuxed GPIO support for SuperH using gpiolib
>
> [PATCH 01/05] sh: Add GPIO and pinmux base code
> [PATCH 02/05] sh: Add sh7722 pinmux tables
> [PATCH 03/05] sh: Use sh7722 GPIO on Migo-R board
> [PATCH 04/05] sh: Add sh7723 pinmux tables
> [PATCH 05/05] sh: Use sh7723 GPIO on AP325RXA board
>
> These patches add support for GPIO to SuperH. The regular GPIO operations
> are all supported for configuring and reading/writing pin data. IRQs are
> not supported at this point.
>
Ok, with a bit of tidying, I've checked this in to the sh/gpiolib topic
branch. I note that this depends on David's request/free hooks, so I'm
not able to merge it until there is a resolution there.
next prev parent reply other threads:[~2008-09-29 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 18:10 [PATCH 00/05] sh: GPIO for SuperH using gpiolib Magnus Damm
2008-09-29 11:44 ` Paul Mundt [this message]
2008-10-20 4:30 ` David Brownell
2008-10-20 4:32 ` David Brownell
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=20080929114402.GA24836@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