linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David Rivshin (Allworx)" <drivshin.allworx@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
	Richard Purdie <rpurdie@rpsys.net>,
	Jacek Anaszewski <j.anaszewski@samsung.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Kumar Gala <galak@codeaurora.org>,
	Stefan Wahren <stefan.wahren@i2se.com>
Subject: Re: [PATCH RFC 2/3] DT: leds: Add binding for the ISSI IS31FL32xx family of LED drivers
Date: Wed, 24 Feb 2016 13:57:13 -0500	[thread overview]
Message-ID: <20160224135713.1eb1e234.drivshin.allworx@gmail.com> (raw)
In-Reply-To: <20160224011508.GA20343@rob-hp-laptop>

On Tue, 23 Feb 2016 19:15:08 -0600
Rob Herring <robh@kernel.org> wrote:

> On Tue, Feb 23, 2016 at 01:17:24PM -0500, David Rivshin (Allworx) wrote:
> > From: David Rivshin <drivshin@allworx.com>
> > 
> > This adds a binding description for the is31fl3236/35/18/16 I2C LED
> > drivers.
> > 
> > Signed-off-by: David Rivshin <drivshin@allworx.com>
> > ---
> >  .../devicetree/bindings/leds/leds-is31fl32xx.txt   | 51 ++++++++++++++++++++++
> >  1 file changed, 51 insertions(+)
> >  create mode 100644 Documentation/devicetree/bindings/leds/leds-is31fl32xx.txt  
> 
> Acked-by: Rob Herring <robh@kernel.org>

Thanks, Rob. I just want to double check whether you noticed some
binding-related questions I had in the coverletter [1]. In hindsight
I should probably have included them in the patch comments as well so 
they'd show up in patchwork. For convenience, I'll repeat them here:

I choose to have 'reg' be 1-based in order to follow the hardware 
documentation. It seems 0-based is the normal choice, although HW
docs also usually use the 0-based numbering. Perhaps being consistent 
with other bindings is more important than being consistent with the 
datasheet's numbering?

I used the 'reg' property for the LED channel, as it seemed ePAPR 
required that name. I also considered naming the property 'chan', 
and not pretending that it represented a bus address at all (and
then removing the @n from the subnode names). That would solve the
'reg' question above as a side-effect, but would be inconstant with
other LED bindings (tca6507, pca963x, tlc59108, etc).

Note that the recently-added (and only in for-next) SN3218 driver 
uses a 0-based 'reg' property, and the SN3218 has the same HW doc
numbering as the IS31FL32xx family (indeed the IS31FL3218 appears 
to be a rebranded SN3218). So perhaps that sets the precedent if 
there was not one before?

Any guidance you could offer would be appreciated (especially since
this is my first from-scratch binding, and I'd rather not form any
bad habits).

[1] http://www.spinics.net/lists/linux-leds/msg05564.html
    http://thread.gmane.org/gmane.linux.leds/4530

  reply	other threads:[~2016-02-24 18:57 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 18:17 [PATCH RFC 0/3] leds: Add driver for the ISSI IS31FL32xx family of LED drivers David Rivshin (Allworx)
2016-02-23 18:17 ` [PATCH RFC 1/3] DT: Add vendor prefix for Integrated Silicon Solutions Inc David Rivshin (Allworx)
2016-02-23 23:36   ` Rob Herring
2016-02-23 18:17 ` [PATCH RFC 2/3] DT: leds: Add binding for the ISSI IS31FL32xx family of LED drivers David Rivshin (Allworx)
2016-02-24  1:15   ` Rob Herring
2016-02-24 18:57     ` David Rivshin (Allworx) [this message]
2016-02-24 19:45       ` Rob Herring
2016-02-24 23:16         ` David Rivshin (Allworx)
2016-02-24 16:04   ` Jacek Anaszewski
2016-02-24 19:34     ` David Rivshin (Allworx)
2016-02-24 19:49       ` Rob Herring
2016-02-26  0:30         ` David Rivshin (Allworx)
2016-02-26  9:56           ` Jacek Anaszewski
2016-02-23 18:17 ` [PATCH RFC 3/3] leds: Add driver " David Rivshin (Allworx)
2016-02-23 18:45   ` Mark Rutland
2016-02-23 22:38     ` David Rivshin (Allworx)
2016-02-24 16:08       ` Jacek Anaszewski
2016-02-24 16:04   ` Jacek Anaszewski
2016-02-25  2:24     ` David Rivshin (Allworx)
2016-02-25 10:55       ` Jacek Anaszewski
2016-02-25 19:12         ` David Rivshin (Allworx)
2016-02-26  9:47           ` Jacek Anaszewski
2016-02-26 21:58             ` David Rivshin (Allworx)
2016-02-27 10:48               ` Stefan Wahren
2016-02-29 18:02                 ` David Rivshin (Allworx)
2016-02-29 19:40                   ` Stefan Wahren
2016-03-01  1:32                     ` David Rivshin (Allworx)
2016-02-29  9:47               ` Jacek Anaszewski
2016-02-29 18:26                 ` David Rivshin (Allworx)
2016-03-01  8:24                   ` Jacek Anaszewski
2016-03-01 18:45                     ` David Rivshin (Allworx)
2016-03-02  8:15                       ` Jacek Anaszewski

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=20160224135713.1eb1e234.drivshin.allworx@gmail.com \
    --to=drivshin.allworx@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=j.anaszewski@samsung.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh@kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=stefan.wahren@i2se.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).