From: sashiko-bot@kernel.org
To: Clover <alex@ironrobin.net>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 2/3] platform: arm64: Add Lenovo ThinkPad X13s EC driver
Date: Fri, 25 Sep 2026 22:07:53 +0000 [thread overview]
Message-ID: <20260925220754.BF1A61F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260925215358.33417-3-alex@ironrobin.net>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] pm: system suspend aborted on non-critical backlight read failure
--
commit d53f4ca8cee991526718fae25d7c38b7a3993fc8
Author: Clover <alex@ironrobin.net>
platform: arm64: Add Lenovo ThinkPad X13s EC driver
Add a standalone driver for the Lenovo ThinkPad X13s embedded controller,
providing keyboard-backlight control and notifications of firmware-driven
brightness changes.
> diff --git a/drivers/platform/arm64/lenovo-thinkpad-x13s.c b/drivers/platform/arm64/lenovo-thinkpad-x13s.c
> new file mode 100644
> index 0000000000000..066f6e300d38f
> --- /dev/null
> +++ b/drivers/platform/arm64/lenovo-thinkpad-x13s.c
[ ... ]
> +static int x13s_suspend(struct device *dev)
> +{
> + struct x13s_ec *ec = dev_get_drvdata(dev);
> + int ret;
> +
> + /* Finish in-flight access while the GENI parent is still usable. */
> + mutex_lock(&ec->lock);
> + if (ec->suspended) {
> + ret = -EBUSY;
> + goto out;
> + }
> + /* Capture hardware state before firmware can reset the backlight. */
> + ret = x13s_brightness(ec);
> + if (ret < 0) {
> + dev_err(dev, "Failed to save backlight brightness: %d\n", ret);
> + goto out;
> + }
[Severity: High]
Could this abort the entire system suspend if the non-critical keyboard
backlight read fails? If x13s_brightness() fails due to a transient bus
error or returns a reserved state (-EINVAL), returning this error to the
PM core prevents the system from sleeping.
> + ec->saved_brightness = ret;
> +
> + /* DSDT: register 0x80 <- 0x55, then GPIO176 low. */
> + ret = x13s_write(ec, X13S_EC_REG_POWER_STATE, X13S_EC_POWER_STATE_ENTER);
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260925215358.33417-1-alex@ironrobin.net?part=2
next prev parent reply other threads:[~2026-09-25 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 21:54 [PATCH 0/3] Lenovo ThinkPad X13s embedded controller support Clover
2026-09-25 21:54 ` [PATCH 1/3] dt-bindings: embedded-controller: Add Lenovo ThinkPad X13s EC Clover
2026-09-25 21:54 ` [PATCH 2/3] platform: arm64: Add Lenovo ThinkPad X13s EC driver Clover
2026-09-25 22:07 ` sashiko-bot [this message]
2026-09-25 21:55 ` [PATCH 3/3] arm64: dts: qcom: sc8280xp-x13s: Add embedded controller Clover
2026-09-25 22:07 ` sashiko-bot
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=20260925220754.BF1A61F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alex@ironrobin.net \
--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.