Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Paul Sajna" <sajattack@postmarketos.org>
Cc: conor+dt@kernel.org, linux-leds@vger.kernel.org, lee@kernel.org,
	robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 7/7] leds: aw2013: move reset from probe_dt to chip_init
Date: Tue, 06 Oct 2026 04:00:39 +0000	[thread overview]
Message-ID: <20261006040039.8AF421F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261005-aw2013-aw20xx-rename-v2-7-108ecbdf2775@postmarketos.org>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] leds: aw2013 hardware retains uncontrolled bootloader state
- [Low] leds: commit message capitalization violation
--

commit 62a3fe5d7c44e90d5a2b75159d01568ea923e7e2
Author: Paul Sajna <sajattack@postmarketos.org>

leds: aw2013: move reset from probe_dt to chip_init

This commit moves the chip reset logic from the Device Tree probing function
to the chip initialization routine. This is intended to simplify mutex
requirements during initialization.

> leds: aw2013: move reset from probe_dt to chip_init

[Severity: Low]
This isn't a bug, but does the commit message violate the subsystem's
capitalization guidelines?

The LED subsystem requires the description to be capitalized after the
subsystem prefix. Should "move" be capitalized to "Move" here?

> diff --git a/drivers/leds/leds-aw2013.c b/drivers/leds/leds-aw2013.c
> index 2a133657d9b64..7bc0415375c6f 100644
> --- a/drivers/leds/leds-aw2013.c
> +++ b/drivers/leds/leds-aw2013.c

[ ... ]

> @@ -369,8 +376,6 @@ static int aw20xx_probe_dt(struct aw20xx *chip)
>  	if (!count || count > AW20XX_MAX_LEDS)
>  		return -EINVAL;
>  
> -	regmap_write(chip->regmap, AW20XX_RSTR, AW20XX_RSTR_RESET);
> -
>  	for_each_available_child_of_node_scoped(np, child) {

[Severity: Medium]
Will removing this unconditional reset from aw20xx_probe_dt() allow the
hardware to retain uncontrolled bootloader state?

By moving the reset exclusively to aw20xx_chip_init(), the reset only occurs
when the kernel explicitly enables the LEDs. If the bootloader leaves the
LEDs enabled and the regulator is shared with another active device, the chip
won't be reset during probe and will remain powered.

Could this cause the LEDs to stay illuminated indefinitely without the
kernel's awareness until user space explicitly requests a state change?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261005-aw2013-aw20xx-rename-v2-0-108ecbdf2775@postmarketos.org?part=7

      reply	other threads:[~2026-10-06  4:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-06  3:46 [PATCH v2 0/7] leds: aw2013: Add AW2027 support Paul Sajna
2026-10-06  3:46 ` [PATCH v2 1/7] dt-bindings: leds: aw2013: Add awinic,aw2027 compatible Paul Sajna
2026-10-06  3:48   ` sashiko-bot
2026-10-07 10:30   ` Conor Dooley
2026-10-06  3:46 ` [PATCH v2 2/7] leds: aw2013: Rename internal APIs from aw2013 to aw20xx Paul Sajna
2026-10-06  3:56   ` sashiko-bot
2026-10-06 10:45   ` Griffin Kroah-Hartman
2026-10-06 18:54     ` Paul Sajna
2026-10-06  3:46 ` [PATCH v2 3/7] leds: aw2013: Add AW2027 support Paul Sajna
2026-10-06  3:56   ` sashiko-bot
2026-10-06  3:46 ` [PATCH v2 4/7] leds: aw2013: use dev_err_probe Paul Sajna
2026-10-06  3:57   ` sashiko-bot
2026-10-06 19:52   ` Griffin Kroah-Hartman
2026-10-07  7:36   ` Andreas Kemnade
2026-10-06  3:46 ` [PATCH v2 5/7] leds: aw2013: Move assignment of chip->num_leds Paul Sajna
2026-10-06  4:01   ` sashiko-bot
2026-10-06  3:46 ` [PATCH v2 6/7] leds: aw2013: Prevent writes to unpowered chip Paul Sajna
2026-10-06  3:59   ` sashiko-bot
2026-10-06  3:46 ` [PATCH v2 7/7] leds: aw2013: move reset from probe_dt to chip_init Paul Sajna
2026-10-06  4:00   ` sashiko-bot [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=20261006040039.8AF421F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sajattack@postmarketos.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