From: sashiko-bot@kernel.org
To: "Junjie Cao" <junjie.cao@linux.dev>
Cc: dri-devel@lists.freedesktop.org, linux-leds@vger.kernel.org,
lee@kernel.org
Subject: Re: [PATCH 1/2] backlight: aw99706: Fix DT property names to match binding
Date: Wed, 01 Jul 2026 13:49:32 +0000 [thread overview]
Message-ID: <20260701134932.7D08A1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260701133918.33487-1-junjie.cao@linux.dev>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] The driver attempts to communicate with the chip via I2C before acquiring and enabling the hardware via its enable GPIO.
--
commit a2f8eb8bf399f54262cbf37acb4512885c65a3b6
Author: Junjie Cao <junjie.cao@linux.dev>
backlight: aw99706: Fix DT property names to match binding
The driver reads four tuning properties without the unit suffixes that
the binding mandates. As a result, device_property_read_u32() never finds
these properties in a binding-conformant device tree and silently falls back
to the compiled-in defaults. This patch fixes the property name strings in
aw99706_dt_props[] to match the binding.
> diff --git a/drivers/video/backlight/aw99706.c b/drivers/video/backlight/aw99706.c
> index 18299faf06ad4..e130f164303a2 100644
> --- a/drivers/video/backlight/aw99706.c
> +++ b/drivers/video/backlight/aw99706.c
> @@ -130,23 +130,23 @@ static const struct aw99706_dt_prop aw99706_dt_props[] = {
[ ... ]
This is a pre-existing issue, but I noticed something concerning in the
initialization sequence within aw99706_probe() in the same file:
drivers/video/backlight/aw99706.c:aw99706_probe() {
...
ret = aw99706_chip_id_read(aw);
if (ret != AW99706_ID)
return dev_err_probe(dev, -ENODEV,
"Unknown chip id 0x%02x\n", ret);
aw99706_dt_parse(aw, &props);
aw->hwen_gpio = devm_gpiod_get(aw->dev, "enable", GPIOD_OUT_LOW);
if (IS_ERR(aw->hwen_gpio))
return dev_err_probe(dev, PTR_ERR(aw->hwen_gpio),
"Failed to get enable gpio\n");
ret = aw99706_hw_init(aw);
...
}
[Severity: High]
Does this sequence result in unconditional probe failure on platforms where the
bootloader does not pre-enable the backlight hardware?
The driver attempts to communicate with the chip via I2C during
aw99706_chip_id_read() before the hardware enable GPIO is acquired and
asserted in aw99706_hw_init().
Because the hardware is likely powered down when aw99706_chip_id_read() is
called, it will not acknowledge the I2C transaction and will return an error.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260701133918.33487-1-junjie.cao@linux.dev?part=1
prev parent reply other threads:[~2026-07-01 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 13:39 [PATCH 1/2] backlight: aw99706: Fix DT property names to match binding Junjie Cao
2026-07-01 13:39 ` [PATCH 2/2] backlight: aw99706: Validate all DT property values consistently Junjie Cao
2026-07-01 13:52 ` sashiko-bot
2026-07-01 13:49 ` 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=20260701134932.7D08A1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=junjie.cao@linux.dev \
--cc=lee@kernel.org \
--cc=linux-leds@vger.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