Devicetree
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: Jonas Rebmann <jre@pengutronix.de>
Cc: <devicetree@vger.kernel.org>, <conor+dt@kernel.org>,
	<robh@kernel.org>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	<sashiko-reviews@lists.linux.dev>
Subject: Re: [PATCH v2 1/2] dt-bindings: leds: Add default-intensity property
Date: Fri, 5 Jun 2026 11:29:31 +0100	[thread overview]
Message-ID: <20260605-factsheet-giving-69f8767bc5d7@wendy> (raw)
In-Reply-To: <3cbee0dc-87a9-4b87-9d22-b3e378fa57c3@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 2656 bytes --]

On Fri, Jun 05, 2026 at 10:45:12AM +0200, Jonas Rebmann wrote:
> Hello,
> 
> On 2026-06-05 09:38, sashiko-bot@kernel.org wrote:
> > > @@ -73,6 +73,17 @@ properties:
> > >         - keep
> > >       default: off
> > > +  default-intensity:
> > > +    description:
> > > +      The initial intensity of the LED color component. Used only during
> > > +      initialization. Defaults to 0. As the intensity of each sub-LED is

I'd drop sentence two here, it just duplicates sentence one.

> > > +      multiplied with the overall brightness, without this property on a
> > > +      sub-LED, the leds-pwm-multicolor-LED is effectively initialized at
> > > +      minimum brightness regardless of its linux,default-trigger and
> > > +      default-brightness properties.
> > 
> > [Severity: Low]
> > This isn't a bug, but the description for default-intensity explicitly
> > mentions the specific driver name leds-pwm-multicolor-LED.
> > 
> > Since common.yaml is intended to be a hardware-agnostic specification
> > for all LED bindings, could this wording be updated to refer generically
> > to the multicolor LED or simply the LED to avoid leaking an
> > implementation detail into the generic schema?
> 
> I'll be leaving this as-is until human feedback.
> 
> I think documenting the property in common.yaml is correct because the
> default-intensity itself is applicable to other multicolor-LED drivers,

I think this is fine.

> I just only implemented it for pwm-multicolor because that's what I use.
> But we could just as well move it to leds-pwm-multicolor.yaml for as
> long as that's the only driver supporting it.

But this is probably also fine and it can be moved if other users crop
up.

> I intentionally included the "pwm" in that sentence because the
> described issue that default-intensity is effectively required when
> using linux,default-trigger may be pwm-multicolor specific.

I don't think this is fine. However, it is almost certainly fine if you
just do s/the leds-pwm-multicolour-LED/it/ because you're no longer
tying the description to the name of one driver.

> 
> I would not like to omit the sentence either because this situation is
> the reason why one might actually need (not just want)
> default-intensity (for -pwm-).
> 
> Regards,
> Jonas
> 
> -- 
> Pengutronix e.K.                           | Jonas Rebmann               |
> Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-9    |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-06-05 10:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05  7:27 [PATCH v2 0/2] leds: pwm-multicolor: Fix default-trigger by allowing default-intensity Jonas Rebmann
2026-06-05  7:27 ` [PATCH v2 1/2] dt-bindings: leds: Add default-intensity property Jonas Rebmann
2026-06-05  7:38   ` sashiko-bot
2026-06-05  8:45     ` Jonas Rebmann
2026-06-05 10:29       ` Conor Dooley [this message]
2026-06-05 10:52         ` Conor Dooley
2026-06-05  7:27 ` [PATCH v2 2/2] leds: pwm-multicolor: Introduce " Jonas Rebmann
2026-06-17 14:47   ` (subset) " Lee Jones

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=20260605-factsheet-giving-69f8767bc5d7@wendy \
    --to=conor.dooley@microchip.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jre@pengutronix.de \
    --cc=kernel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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