From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6 v12] gpio: Add block GPIO
Date: Sat, 29 Dec 2012 15:10:07 +0100 [thread overview]
Message-ID: <50DEF9BF.6020301@antcom.de> (raw)
In-Reply-To: <20121229121356.GB7360@game.jcrosoft.org>
On 29/12/12 13:13, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 13:01 Sat 29 Dec , Roland Stigge wrote:
>> On 29/12/12 11:20, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>> On 17:49 Sun 23 Dec , Roland Stigge wrote:
>>>> This set of patches adds:
>>>>
>>>> * Block GPIO API to gpiolib
>>>> * Sysfs support for GPIO API, to provide userland access
>>>> * Device interface for userland access (alternative to sysfs)
>>>> * Devicetree support to instantiate GPIO blocks via DT
>>>> * Example implementations in several gpio drivers since they need
>>>> special accessor functions for block wise GPIO access (only for some
>>>> selected drivers since the feature is optional and not suitable for
>>>> all GPIO hardware)
>>>> * Fix for race condition in gpiolib on device creation
>>>>
>>>> Signed-off-by: Roland Stigge <stigge@antcom.de>
>>>> Tested by: Wolfgang Grandegger <wg@grandegger.com>
>>>> --
>>>>
>>>> Testing branch available at: git://git.antcom.de/linux-2.6.git blockgpio
>>>>
>>>> Changes since v11:
>>>> * Removed support for at91, since this one is currently in the migration
>>>> process to pinctrl implementation
>>> already done for 3.8
>>>
>>> in Linus tree
>>
>> Good, thanks for the note! So we include support for block GPIO in
>> pinctrl-at91.c now.
>>
>> I guess the redundant code in arch/arm/mach-at91/gpio.c will be removed?
> no we keep for non DT platform
So would it be helpful it to maintain/mainline Wolfgang's patch for this
one regarding block GPIO? (Besides patching pinctrl-at91.c?)
Thanks,
Roland
WARNING: multiple messages have this Message-ID (diff)
From: Roland Stigge <stigge@antcom.de>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: gregkh@linuxfoundation.org, grant.likely@secretlab.ca,
linus.walleij@linaro.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, w.sang@pengutronix.de,
jbe@pengutronix.de, highguy@gmail.com,
broonie@opensource.wolfsonmicro.com, daniel-gl@gmx.net,
rmallon@gmail.com, sr@denx.de, wg@grandegger.com,
tru@work-microwave.de, mark.rutland@arm.com
Subject: Re: [PATCH 0/6 v12] gpio: Add block GPIO
Date: Sat, 29 Dec 2012 15:10:07 +0100 [thread overview]
Message-ID: <50DEF9BF.6020301@antcom.de> (raw)
In-Reply-To: <20121229121356.GB7360@game.jcrosoft.org>
On 29/12/12 13:13, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 13:01 Sat 29 Dec , Roland Stigge wrote:
>> On 29/12/12 11:20, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>> On 17:49 Sun 23 Dec , Roland Stigge wrote:
>>>> This set of patches adds:
>>>>
>>>> * Block GPIO API to gpiolib
>>>> * Sysfs support for GPIO API, to provide userland access
>>>> * Device interface for userland access (alternative to sysfs)
>>>> * Devicetree support to instantiate GPIO blocks via DT
>>>> * Example implementations in several gpio drivers since they need
>>>> special accessor functions for block wise GPIO access (only for some
>>>> selected drivers since the feature is optional and not suitable for
>>>> all GPIO hardware)
>>>> * Fix for race condition in gpiolib on device creation
>>>>
>>>> Signed-off-by: Roland Stigge <stigge@antcom.de>
>>>> Tested by: Wolfgang Grandegger <wg@grandegger.com>
>>>> --
>>>>
>>>> Testing branch available at: git://git.antcom.de/linux-2.6.git blockgpio
>>>>
>>>> Changes since v11:
>>>> * Removed support for at91, since this one is currently in the migration
>>>> process to pinctrl implementation
>>> already done for 3.8
>>>
>>> in Linus tree
>>
>> Good, thanks for the note! So we include support for block GPIO in
>> pinctrl-at91.c now.
>>
>> I guess the redundant code in arch/arm/mach-at91/gpio.c will be removed?
> no we keep for non DT platform
So would it be helpful it to maintain/mainline Wolfgang's patch for this
one regarding block GPIO? (Besides patching pinctrl-at91.c?)
Thanks,
Roland
next prev parent reply other threads:[~2012-12-29 14:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-23 16:49 [PATCH 0/6 v12] gpio: Add block GPIO Roland Stigge
2012-12-23 16:49 ` Roland Stigge
2012-12-23 16:49 ` [PATCH 1/6 v12] gpio: Add a block GPIO API to gpiolib Roland Stigge
2012-12-23 16:49 ` Roland Stigge
2012-12-23 16:49 ` [PATCH 2/6 v12] gpio: Add sysfs support to block GPIO API Roland Stigge
2012-12-23 16:49 ` Roland Stigge
2012-12-23 16:49 ` [PATCH 3/6 v12] gpio: Add userland device interface to block GPIO Roland Stigge
2012-12-23 16:49 ` Roland Stigge
2012-12-23 16:49 ` [PATCH 4/6 v12] gpiolib: Fix default attributes for class Roland Stigge
2012-12-23 16:49 ` Roland Stigge
2012-12-23 16:49 ` [PATCH 5/6 v12] gpio: Add device tree support to block GPIO API Roland Stigge
2012-12-23 16:49 ` Roland Stigge
2012-12-23 16:49 ` [PATCH 6/6 v12] gpio: Add block gpio to several gpio drivers Roland Stigge
2012-12-23 16:49 ` Roland Stigge
2012-12-29 10:20 ` [PATCH 0/6 v12] gpio: Add block GPIO Jean-Christophe PLAGNIOL-VILLARD
2012-12-29 10:20 ` Jean-Christophe PLAGNIOL-VILLARD
2012-12-29 12:01 ` Roland Stigge
2012-12-29 12:01 ` Roland Stigge
2012-12-29 12:13 ` Jean-Christophe PLAGNIOL-VILLARD
2012-12-29 12:13 ` Jean-Christophe PLAGNIOL-VILLARD
2012-12-29 14:10 ` Roland Stigge [this message]
2012-12-29 14:10 ` Roland Stigge
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=50DEF9BF.6020301@antcom.de \
--to=stigge@antcom.de \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.