From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND v9 1/2] gpio: Adjust of_xlate API to support multiple GPIO chips
Date: Fri, 18 May 2012 10:03:22 +0200 [thread overview]
Message-ID: <4FB6024A.5010002@antcom.de> (raw)
In-Reply-To: <20120517203706.6B8223E0621@localhost>
Hi Grant,
On 05/17/2012 10:37 PM, Grant Likely wrote:
> On Wed, 16 May 2012 22:40:31 +0200, Roland Stigge <stigge@antcom.de> wrote:
>> This patch changes the of_xlate API to make it possible to manipulate the
>> actual used gc. This way, multiple GPIO banks can be supported with the same DT
>> registered GPIO controller.
>>
>> The issue was discussed upon the integration of LPC32xx's DT support for its
>> GPIO (see separate patch).
>>
>> Signed-off-by: Roland Stigge <stigge@antcom.de>
>
> I still wasn't happy with this approach, so I bugged Arnd and we
> discussed some options. So, I think I've got a better solution that
> doesn't change the signature of of_xlate. Instead it allows of_xlate
> to return an error code and still have multiple banks referring to the
> same gpio_chip.
>
> I've just posted the series. Can you try it out and make sure it
> works for you?
Works fine, just consider the little compile error bugfix, see next mail.
Thanks,
Roland
WARNING: multiple messages have this Message-ID (diff)
From: Roland Stigge <stigge@antcom.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: glikely@secretlab.ca, arm@kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linus.walleij@stericsson.com, kevin.wells@nxp.com,
srinivas.bakki@nxp.com, devicetree-discuss@lists.ozlabs.org,
rob.herring@calxeda.com
Subject: Re: [PATCH RESEND v9 1/2] gpio: Adjust of_xlate API to support multiple GPIO chips
Date: Fri, 18 May 2012 10:03:22 +0200 [thread overview]
Message-ID: <4FB6024A.5010002@antcom.de> (raw)
In-Reply-To: <20120517203706.6B8223E0621@localhost>
Hi Grant,
On 05/17/2012 10:37 PM, Grant Likely wrote:
> On Wed, 16 May 2012 22:40:31 +0200, Roland Stigge <stigge@antcom.de> wrote:
>> This patch changes the of_xlate API to make it possible to manipulate the
>> actual used gc. This way, multiple GPIO banks can be supported with the same DT
>> registered GPIO controller.
>>
>> The issue was discussed upon the integration of LPC32xx's DT support for its
>> GPIO (see separate patch).
>>
>> Signed-off-by: Roland Stigge <stigge@antcom.de>
>
> I still wasn't happy with this approach, so I bugged Arnd and we
> discussed some options. So, I think I've got a better solution that
> doesn't change the signature of of_xlate. Instead it allows of_xlate
> to return an error code and still have multiple banks referring to the
> same gpio_chip.
>
> I've just posted the series. Can you try it out and make sure it
> works for you?
Works fine, just consider the little compile error bugfix, see next mail.
Thanks,
Roland
next prev parent reply other threads:[~2012-05-18 8:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 20:40 [PATCH RESEND v9 1/2] gpio: Adjust of_xlate API to support multiple GPIO chips Roland Stigge
2012-05-16 20:40 ` Roland Stigge
2012-05-16 20:40 ` [PATCH RESEND v9 2/2] gpio: Device tree support for LPC32xx Roland Stigge
2012-05-16 20:40 ` Roland Stigge
2012-05-17 20:37 ` [PATCH RESEND v9 1/2] gpio: Adjust of_xlate API to support multiple GPIO chips Grant Likely
2012-05-17 20:37 ` Grant Likely
2012-05-17 20:37 ` Grant Likely
2012-05-18 8:03 ` Roland Stigge [this message]
2012-05-18 8:03 ` 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=4FB6024A.5010002@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.