From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Daniel Drake <dsd@laptop.org>,
sameo@linux.intel.com, devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, dilinger@queued.net
Subject: Re: [PATCH 3/3] gpio-vx855: Add device tree binding
Date: Wed, 21 Sep 2011 17:37:39 +0100 [thread overview]
Message-ID: <20110921163738.GK4374@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110921162906.GY7781@ponder.secretlab.ca>
On Wed, Sep 21, 2011 at 10:29:06AM -0600, Grant Likely wrote:
> On Wed, Sep 21, 2011 at 01:50:52PM +0100, Mark Brown wrote:
> > Shouldn't we just have a property for the polarity?
> A flags cell in gpio specifiers (and irq specifiers for that matter) is
> well established practice.
Oh, well :( We need to establish what the general style is for stuff
like this, it feels like there's frequent conflict between existing
practice and what people want to do with new bindings (in addition to
the cases like the arrays where there's some issues in general).
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
dilinger-pFFUokh25LWsTnJN9+BGXg@public.gmane.org,
Daniel Drake <dsd-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org>,
sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org
Subject: Re: [PATCH 3/3] gpio-vx855: Add device tree binding
Date: Wed, 21 Sep 2011 17:37:39 +0100 [thread overview]
Message-ID: <20110921163738.GK4374@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110921162906.GY7781-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
On Wed, Sep 21, 2011 at 10:29:06AM -0600, Grant Likely wrote:
> On Wed, Sep 21, 2011 at 01:50:52PM +0100, Mark Brown wrote:
> > Shouldn't we just have a property for the polarity?
> A flags cell in gpio specifiers (and irq specifiers for that matter) is
> well established practice.
Oh, well :( We need to establish what the general style is for stuff
like this, it feels like there's frequent conflict between existing
practice and what people want to do with new bindings (in addition to
the cases like the arrays where there's some issues in general).
next prev parent reply other threads:[~2011-09-21 16:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 12:02 [PATCH 3/3] gpio-vx855: Add device tree binding Daniel Drake
2011-09-21 12:02 ` Daniel Drake
2011-09-21 12:50 ` Mark Brown
2011-09-21 12:50 ` Mark Brown
2011-09-21 13:04 ` Daniel Drake
2011-09-21 13:04 ` Daniel Drake
2011-09-21 16:29 ` Grant Likely
2011-09-21 16:29 ` Grant Likely
2011-09-21 16:37 ` Mark Brown [this message]
2011-09-21 16:37 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2011-09-21 12:02 Daniel Drake
2011-09-28 9:08 Daniel Drake
2011-09-28 9:08 ` Daniel Drake
2011-09-28 9:08 Daniel Drake
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=20110921163738.GK4374@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dilinger@queued.net \
--cc=dsd@laptop.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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 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.