Linux LED subsystem development
 help / color / mirror / Atom feed
From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "conor+dt@kernel.org" <conor+dt@kernel.org>,
	"afd@ti.com" <afd@ti.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: "robh@kernel.org" <robh@kernel.org>,
	"lee@kernel.org" <lee@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: leds: Convert LP8860 into YAML format
Date: Mon, 9 Dec 2024 15:25:06 +0000	[thread overview]
Message-ID: <4fe345a1fffbd75aab8473ad0dcb1f0dfb952bb2.camel@siemens.com> (raw)
In-Reply-To: <d1122a33-5735-4000-98b3-ae9b1ed73008@ti.com>

Hi Andrew!

On Mon, 2024-12-09 at 09:05 -0600, Andrew Davis wrote:
> > then some mapping between subnode and HW channel would be required.
> > We probably don't want to parse a node name in this case and carve out "-0"
> > part of it, in such case a well-defined property, such as "reg" would be
> > required.
> > 
> 
> We are not the only driver to do the "-#" method. Although yes just
> using reg is easier for the Linux driver.

After a quick grep over the bindings I'd say those led-X are using
"gpios" or "pwms" property to associate them with real HW and seems that
there is exactly one example of doing some implicit mapping: nxp,pca953x.yaml

It seems to me that using "reg" is much more widespread (if it's neither "gpios"
nor "pwms"). 

-- 
Alexander Sverdlin
Siemens AG
www.siemens.com

  reply	other threads:[~2024-12-09 15:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 20:31 [PATCH] dt-bindings: leds: Convert LP8860 into YAML format A. Sverdlin
2024-12-09 14:29 ` Andrew Davis
2024-12-09 14:35   ` Sverdlin, Alexander
2024-12-09 15:05     ` Andrew Davis
2024-12-09 15:25       ` Sverdlin, Alexander [this message]
2024-12-11 16:26   ` Rob Herring
2024-12-11 16:30     ` Rob Herring

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=4fe345a1fffbd75aab8473ad0dcb1f0dfb952bb2.camel@siemens.com \
    --to=alexander.sverdlin@siemens.com \
    --cc=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=robh@kernel.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