From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] GPIO: Extend the cmd_gpio API by gpio_{from, to}_string()
Date: Thu, 2 Aug 2012 13:50:51 -0400 [thread overview]
Message-ID: <201208021350.53076.vapier@gentoo.org> (raw)
In-Reply-To: <201208021205.14821.marek.vasut@gmail.com>
On Thursday 02 August 2012 06:05:14 Marek Vasut wrote:
> Dear Mike Frysinger,
>
> > On Monday 14 May 2012 07:31:35 Marek Vasut wrote:
> > > Dear Mike Frysinger,
> > >
> > > > On Tuesday 01 May 2012 16:50:14 Marek Vasut wrote:
> > > > > The gpio_from_string() call shall parse the incoming GPIO name
> > > > > taken from the command line and return the GPIO number used within
> > > > > U-Boot or return -1 on error.
> > > >
> > > > i.e. the already existing name_to_gpio() func
> > >
> > > You mean blackfin specific macro crap? Let's actually drop that and
> > > switch over to this one. That was my intention from start.
> >
> > don't spout this crap. try reading the actual history on the lists for
> > the background on the naming, and then try actually grepping the tree to
> > see that multiple targets implement it.
>
> So ... it was chosen to be compatible with linux gpio api, that's what I
> understood ... so I grepped the kernel source:
>
> linux-2.6# git grep name_to_gpio drivers/gpio/
> linux-2.6# git grep name_to_gpio include/
> linux-2.6# git grep gpio_to_name include/
> linux-2.6# git grep gpio_to_name drivers/gpio/
>
> Nothing.
the naming convention is inline with the linux naming convention. there is no
concept in linux of stringifying a GPIO number.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120802/eceb27da/attachment.pgp>
prev parent reply other threads:[~2012-08-02 17:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 20:50 [U-Boot] [PATCH 1/2] GPIO: Extend the cmd_gpio API by gpio_{from, to}_string() Marek Vasut
2012-05-01 20:50 ` [U-Boot] [PATCH 2/2] GPIO: Implement gpio_{from, to}_string on M28EVK Marek Vasut
2012-05-09 18:29 ` [U-Boot] [PATCH 1/2] GPIO: Extend the cmd_gpio API by gpio_{from, to}_string() Marek Vasut
2012-05-14 5:51 ` Mike Frysinger
2012-05-14 11:31 ` Marek Vasut
2012-05-14 16:14 ` Mike Frysinger
2012-05-14 18:25 ` Marek Vasut
2012-05-15 5:11 ` Mike Frysinger
2012-05-15 5:53 ` Marek Vasut
2012-05-18 2:53 ` Mike Frysinger
2012-08-02 10:05 ` Marek Vasut
2012-08-02 17:50 ` Mike Frysinger [this message]
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=201208021350.53076.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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