Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	mfd@lists.linux.dev, robh@kernel.org, conor+dt@kernel.org,
	lee@kernel.org
Subject: Re: [PATCH 2/9] backlight: qcom-wled: fix string detection brightness on WLED5
Date: Thu, 15 Oct 2026 09:17:13 +0000	[thread overview]
Message-ID: <sashiko-outbox-172555@kernel.org> (raw)
In-Reply-To: <20261015-sm8150-display-card-v1-2-5c14928cef29@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] qcom-wled: missing brightness sync toggle for WLED4
--

commit 80c30ca9ff45480f825b4f3ca26c694d9fa71acf
Author: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>

backlight: qcom-wled: fix string detection brightness on WLED5

This patch updates the auto string detection logic to properly latch new
brightness values for WLED5. It introduces a helper function to set the
brightness and apply the version-specific sync toggle.

> diff --git a/drivers/video/backlight/qcom-wled.c b/drivers/video/backlight/qcom-wled.c
> index f2e0430cccbca..6fbac6a4c29b8 100644
> --- a/drivers/video/backlight/qcom-wled.c
> +++ b/drivers/video/backlight/qcom-wled.c
> @@ -577,6 +577,17 @@ static irqreturn_t wled_short_irq_handler(int irq, void *_wled)
>  
>  #define AUTO_DETECT_BRIGHTNESS		200
>  
> +static int wled_auto_detect_set_brightness(struct wled *wled, u16 brightness)
> +{
> +	int rc;
> +
> +	rc = wled->wled_set_brightness(wled, brightness);
> +	if (rc < 0 || wled->version < 5)
> +		return rc;

[Severity: Medium]
Does this code introduce a regression for WLED4 devices by missing the
brightness sync toggle?

During WLED4 auto string detection, the code updates the brightness to a low
test value, but it appears to return without latching it. Looking at the
standard brightness update path in wled_update_status(), WLED4 hardware
requires a sync toggle to apply brightness changes:

drivers/video/backlight/qcom-wled.c:wled_update_status() {
	...
	if (wled->version < 5) {
		rc = wled->wled_sync_toggle(wled);
	...
}

Without syncing the auto-detect test brightness, WLED4 might run the
detection with stale, potentially high brightness. Could this trigger false
over-voltage (OVP) faults and incorrectly mark valid LED strings as
disconnected?

> +
> +	return wled5_mod_sync_toggle(wled);
> +}

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261015-sm8150-display-card-v1-0-5c14928cef29@oss.qualcomm.com?part=2

  parent reply	other threads:[~2026-10-15  9:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15  8:58 [PATCH 0/9] arm64: qcom: enable display card support on SM8150 HDK Dmitry Baryshkov
2026-10-15  8:58 ` [PATCH 1/9] backlight: qcom-wled: fix unbalanced OVP interrupt enable Dmitry Baryshkov
2026-10-15  9:11   ` Konrad Dybcio
2026-10-15  9:44     ` Dmitry Baryshkov
2026-10-15  9:22   ` sashiko-bot
2026-10-15  8:58 ` [PATCH 2/9] backlight: qcom-wled: fix string detection brightness on WLED5 Dmitry Baryshkov
2026-10-15  9:13   ` Konrad Dybcio
2026-10-15  9:17   ` sashiko-bot [this message]
2026-10-15  8:58 ` [PATCH 3/9] dt-bindings: regulator: add Qualcomm LCDB regulator Dmitry Baryshkov
2026-10-15  9:14   ` Konrad Dybcio
2026-10-15  8:58 ` [PATCH 4/9] dt-bindings: mfd: qcom,spmi-pmic: add LCDB Dmitry Baryshkov
2026-10-15  8:58 ` [PATCH 5/9] regulator: add Qualcomm LCDB driver Dmitry Baryshkov
2026-10-15  9:31   ` sashiko-bot
2026-10-15  8:58 ` [PATCH 6/9] arm64: dts: qcom: pm8150l: add LCDB regulators Dmitry Baryshkov
2026-10-15  9:39   ` sashiko-bot
2026-10-15  8:58 ` [PATCH 7/9] arm64: dts: qcom: sm8150: add MDSS reset Dmitry Baryshkov
2026-10-15  9:15   ` Konrad Dybcio
2026-10-15  8:58 ` [PATCH 8/9] arm64: dts: qcom: sm8150-hdk: fix FSA4480 address Dmitry Baryshkov
2026-10-15  9:10   ` Konrad Dybcio
2026-10-15  9:11     ` Konrad Dybcio
2026-10-15  8:58 ` [PATCH 9/9] arm64: dts: qcom: sm8150-hdk: add display card overlay Dmitry Baryshkov

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=sashiko-outbox-172555@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lee@kernel.org \
    --cc=mfd@lists.linux.dev \
    --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