All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: "Escala, Edelweise" <Edelweise.Escala@analog.com>
Cc: "sashiko-reviews@lists.linux.dev"
	<sashiko-reviews@lists.linux.dev>,
	"robh@kernel.org" <robh@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>
Subject: Re: [PATCH v8 2/2] leds: ltc3220: Add Support for LTC3220 18 channel LED Driver
Date: Wed, 20 May 2026 14:44:26 +0100	[thread overview]
Message-ID: <20260520134426.GB2767592@google.com> (raw)
In-Reply-To: <DS0PR03MB722893FF4942A436AAF69175ED012@DS0PR03MB7228.namprd03.prod.outlook.com>

On Wed, 20 May 2026, Escala, Edelweise wrote:

> 
> > -----Original Message-----
> > From: sashiko-bot@kernel.org <sashiko-bot@kernel.org>

Do I need to sign-up to receive these?

> > Sent: Tuesday, May 19, 2026 9:50 AM
> > To: Escala, Edelweise <Edelweise.Escala@analog.com>
> > Cc: robh@kernel.org; devicetree@vger.kernel.org; conor+dt@kernel.org

Working why only these email addresses were Cc:ed.

> > Subject: Re: [PATCH v8 2/2] leds: ltc3220: Add Support for LTC3220 18 channel
> > LED Driver
> > 
> > [External]
> > 
> > Thank you for your contribution! Sashiko AI review found 7 potential issue(s) to
> > consider:
> > - [High] The driver abuses the `brightness` attribute to multiplex hardware modes,
> > violating standard LED UAPI.
> > - [High] The `blink_mode` value is not shifted before being written via
> > `regmap_update_bits()`, causing blink timing to fail.
> > - [High] `ltc3220_blink_set()` fails to enable blink mode on the target LED's
> > control register.
> > - [High] `ltc3220_pattern_clear()` incorrectly halts the global gradation timer and
> > fails to reset the individual LED mode.
> > - [High] Duplicate `reg` values in the device tree cause double-registration and list
> > corruption.
> > - [High] Missing `select REGMAP_I2C` in Kconfig leads to silent build failures.
> > - [Medium] Missing `led_classdev_suspend()` and `led_classdev_resume()` calls
> > during power management.
> > --
> > 
> > commit 0ef3ccbe351040b28172d9e382676a039d0118d4
> > Author: Edelweise Escala <edelweise.escala@analog.com>



-- 
Lee Jones

      reply	other threads:[~2026-05-20 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19  1:14 [PATCH v8 0/2] Add Support for LTC3220 18 Channel LED Driver Edelweise Escala
2026-05-19  1:14 ` [PATCH v8 1/2] dt-bindings: leds: Add LTC3220 18 channel " Edelweise Escala
2026-05-19  1:23   ` sashiko-bot
2026-05-19 17:38     ` Conor Dooley
2026-05-20 12:05       ` Escala, Edelweise
2026-05-19  1:14 ` [PATCH v8 2/2] leds: ltc3220: Add Support for " Edelweise Escala
2026-05-19  1:50   ` sashiko-bot
2026-05-20 12:56     ` Escala, Edelweise
2026-05-20 13:44       ` Lee Jones [this message]

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=20260520134426.GB2767592@google.com \
    --to=lee@kernel.org \
    --cc=Edelweise.Escala@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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 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.