From: Grant Likely <grant.likely@secretlab.ca>
To: Alex Courbot <acourbot@nvidia.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"gnurou@gmail.com" <gnurou@gmail.com>
Subject: Re: [RFC] gpiolib: introduce descriptor-based GPIO interface
Date: Mon, 10 Dec 2012 22:34:25 +0000 [thread overview]
Message-ID: <20121210223425.DC2783E0796@localhost> (raw)
In-Reply-To: <1985305.LiOKDTFPq4@percival>
On Fri, 7 Dec 2012 11:06:34 +0900, Alex Courbot <acourbot@nvidia.com> wrote:
> On Thursday 06 December 2012 22:42:59 Grant Likely wrote:
> > how about "gpio_chip_hwnum()" to somewhat match irqdomain convention?
>
> Sure, matching existing interfaces is better. "git grep hwnum" does not seem
> to reveal much related to irqdomain though?
irqdomain actually uses "hwirq". "hwgpio" would be a closer analog than
'hwnum'. At first I though hwgpio to be too goofy, but on further
reflection it probably has the least likelyhood of getting used
incorrectly.
g.
WARNING: multiple messages have this Message-ID (diff)
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] gpiolib: introduce descriptor-based GPIO interface
Date: Mon, 10 Dec 2012 22:34:25 +0000 [thread overview]
Message-ID: <20121210223425.DC2783E0796@localhost> (raw)
In-Reply-To: <1985305.LiOKDTFPq4@percival>
On Fri, 7 Dec 2012 11:06:34 +0900, Alex Courbot <acourbot@nvidia.com> wrote:
> On Thursday 06 December 2012 22:42:59 Grant Likely wrote:
> > how about "gpio_chip_hwnum()" to somewhat match irqdomain convention?
>
> Sure, matching existing interfaces is better. "git grep hwnum" does not seem
> to reveal much related to irqdomain though?
irqdomain actually uses "hwirq". "hwgpio" would be a closer analog than
'hwnum'. At first I though hwgpio to be too goofy, but on further
reflection it probably has the least likelyhood of getting used
incorrectly.
g.
next prev parent reply other threads:[~2012-12-10 22:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 7:45 [RFC] gpiolib: introduce descriptor-based GPIO interface Alexandre Courbot
2012-12-06 7:45 ` Alexandre Courbot
2012-12-06 7:45 ` Alexandre Courbot
2012-12-06 7:45 ` Alexandre Courbot
2012-12-06 7:45 ` Alexandre Courbot
2012-12-06 7:45 ` Alexandre Courbot
2012-12-06 14:42 ` Grant Likely
2012-12-06 14:42 ` Grant Likely
2012-12-06 14:42 ` Grant Likely
2012-12-06 14:42 ` Grant Likely
2012-12-07 2:06 ` Alex Courbot
2012-12-07 2:06 ` Alex Courbot
2012-12-07 8:24 ` Linus Walleij
2012-12-07 8:24 ` Linus Walleij
2012-12-10 22:34 ` Grant Likely [this message]
2012-12-10 22:34 ` Grant Likely
2012-12-06 20:19 ` Linus Walleij
2012-12-06 20:19 ` Linus Walleij
2012-12-07 2:49 ` Guenter Roeck
2012-12-07 2:49 ` Guenter Roeck
2012-12-07 7:02 ` Alex Courbot
2012-12-07 7:02 ` Alex Courbot
2012-12-07 15:07 ` Guenter Roeck
2012-12-07 15:07 ` Guenter Roeck
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=20121210223425.DC2783E0796@localhost \
--to=grant.likely@secretlab.ca \
--cc=acourbot@nvidia.com \
--cc=arnd@arndb.de \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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 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.