From: Robin Getz <rgetz@blackfin.uclinux.org>
To: uclinux-dist-devel@blackfin.uclinux.org
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Mike Frysinger <vapier@gentoo.org>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [Uclinux-dist-devel] [PATCH] Input: ad7879: support auxiliary GPIOs via gpiolib
Date: Thu, 7 Jan 2010 11:16:19 -0500 [thread overview]
Message-ID: <201001071116.19616.rgetz@blackfin.uclinux.org> (raw)
In-Reply-To: <20100107073114.GC2314@core.coreip.homeip.net>
On Thu 7 Jan 2010 02:31, Dmitry Torokhov pondered:
> Hi Michael,
>
> On Thu, Jan 07, 2010 at 02:18:22AM -0500, Mike Frysinger wrote:
> > From: Michael Hennerich <michael.hennerich@analog.com>
> >
> > Drop the simple fancy sysfs hooks for the aux GPIOs and expose these via
> > the gpiolib interface so that other drivers can use them.
>
> Would not that mess up current users (if any) that may rely on the
> existing sysfs attributes?
We have talked to the existing users of this (that we know of), and they
agreed that doing things the "standard" way with gpiolib is the better way to
move forward on things.
-Robin
next prev parent reply other threads:[~2010-01-07 16:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 7:18 [PATCH] Input: ad7879: support auxiliary GPIOs via gpiolib Mike Frysinger
2010-01-07 7:31 ` Dmitry Torokhov
2010-01-07 16:16 ` Robin Getz [this message]
2010-01-07 16:46 ` [Uclinux-dist-devel] " Mike Frysinger
2010-01-07 17:07 ` Dmitry Torokhov
2010-01-07 17:43 ` Robin Getz
2010-01-10 7:48 ` Dmitry Torokhov
2010-01-12 13:57 ` Hennerich, Michael
2010-01-12 21:04 ` [PATCH v2] " Mike Frysinger
2010-01-13 2:54 ` Dmitry Torokhov
2010-01-13 9:46 ` Hennerich, Michael
[not found] ` <8A42379416420646B9BFAC9682273B6D0F0DF094-pcKY8lWzTjquVPpjEGsWsTcYPEmu4y7e@public.gmane.org>
2010-01-14 6:24 ` Dmitry Torokhov
2010-01-17 15:36 ` [PATCH v3] " Mike Frysinger
2010-01-18 6:35 ` Dmitry Torokhov
2010-01-18 6:48 ` [Uclinux-dist-devel] " Mike Frysinger
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=201001071116.19616.rgetz@blackfin.uclinux.org \
--to=rgetz@blackfin.uclinux.org \
--cc=Michael.Hennerich@analog.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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 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).