From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, Trent Piepho <tpiepho@freescale.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] of_gpio: Return GPIO flags from of_get_gpio()
Date: Thu, 27 Nov 2008 01:31:51 +0300 [thread overview]
Message-ID: <20081126223151.GA1178@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <18733.49643.63081.163437@cargo.ozlabs.ibm.com>
On Thu, Nov 27, 2008 at 08:38:51AM +1100, Paul Mackerras wrote:
[...]
> > > drivers/mtd/nand/fsl_upm.c | 2 +-
> > > drivers/net/fs_enet/fs_enet-main.c | 2 +-
> > > drivers/net/phy/mdio-ofgpio.c | 4 ++--
> > > drivers/of/gpio.c | 13 ++++++++++---
> > > drivers/serial/cpm_uart/cpm_uart_core.c | 2 +-
> > > include/linux/of_gpio.h | 21 +++++++++++++++++----
> > > 6 files changed, 32 insertions(+), 12 deletions(-)
>
> That would need acks from Jeff Garzik and David Woodhouse.
>
> Alternatively you could add a new function (called, for instance,
> of_get_gpio_flags) with the extra parameter to eliminate the need to
> change any drivers at this stage, since they all seem to pass NULL for
> the flags argument.
:-))
This was _exactly_ my initial approach, but Trent and Grant thought
that changing API would be easy. Hah-ha!
Here is my initial patch implementing of_get_gpio_flags():
http://lkml.org/lkml/2008/7/25/236
Trent, are you going to push your patch through all the
maintainers, or should we, after all, revert to my approach
instead?
Thanks,
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2008-11-26 22:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 23:04 OpenFirmware GPIO LED driver Trent Piepho
2008-10-24 23:08 ` [PATCH 1/4] of_gpio: Return GPIO flags from of_get_gpio() Trent Piepho
2008-10-24 23:32 ` Grant Likely
2008-10-28 14:39 ` Anton Vorontsov
2008-10-28 14:53 ` Grant Likely
2008-10-28 15:16 ` Anton Vorontsov
2008-10-28 15:42 ` Grant Likely
2008-10-28 16:56 ` Anton Vorontsov
2008-10-28 17:40 ` Grant Likely
2008-10-30 2:21 ` [PATCH 1/4] of_gpio: Return GPIO flags from of_get_gpio()A Trent Piepho
2008-10-30 11:15 ` Anton Vorontsov
2008-10-31 2:03 ` [PATCH v2] of_gpio: Return GPIO flags from of_get_gpio() Trent Piepho
2008-11-26 16:20 ` Anton Vorontsov
2008-11-26 21:38 ` Paul Mackerras
2008-11-26 22:31 ` Anton Vorontsov [this message]
2008-11-26 22:35 ` Trent Piepho
2008-11-26 22:58 ` Anton Vorontsov
2008-11-26 23:32 ` Paul Mackerras
2008-10-24 23:08 ` [PATCH 2/4] leds: Support OpenFirmware led bindings Trent Piepho
2008-10-24 23:50 ` Grant Likely
2008-10-24 23:09 ` [PATCH 3/4] leds: Add option to have GPIO LEDs start on Trent Piepho
2008-10-24 23:59 ` Grant Likely
2008-10-24 23:09 ` [PATCH 4/4] leds: Let GPIO LEDs keep their current state Trent Piepho
2008-10-25 0:04 ` Grant Likely
2008-11-17 14:50 ` Richard Purdie
2008-11-21 1:05 ` Trent Piepho
2008-11-23 12:31 ` Pavel Machek
2008-12-03 10:04 ` Richard Purdie
2008-12-10 4:33 ` Trent Piepho
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=20081126223151.GA1178@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=tpiepho@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).