From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "luca.ceresoli@bootlin.com" <luca.ceresoli@bootlin.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>
Subject: Re: [PATCH v4 6/8] backlight: led-backlight: add devlink to supplier LEDs
Date: Mon, 12 May 2025 12:13:54 +0000 [thread overview]
Message-ID: <b5d2b71ffc38eb1980ce72994a20e8f6ee7869bd.camel@siemens.com> (raw)
In-Reply-To: <fa87471d31a62017067d4c3ba559cf79d6c3afec.camel@siemens.com>
Hi Luca,
On Mon, 2025-05-12 at 13:39 +0200, Alexander Sverdlin wrote:
> > led-backlight is a consumer of one or multiple LED class devices, but no
> > devlink is created for such supplier-producer relationship. One consequence
> > is that removal ordered is not correctly enforced.
> >
> > Issues happen for example with the following sections in a device tree
> > overlay:
> >
> > // An LED driver chip
> > pca9632@62 {
> > compatible = "nxp,pca9632";
> > reg = <0x62>;
> >
> > // ...
> >
> > addon_led_pwm: led-pwm@3 {
> > reg = <3>;
> > label = "addon:led:pwm";
> > };
> > };
> >
> > backlight-addon {
> > compatible = "led-backlight";
> > leds = <&addon_led_pwm>;
> > brightness-levels = <255>;
> > default-brightness-level = <255>;
> > };
> >
> > On removal of the above overlay, the LED driver can be removed before the
> > backlight device, resulting in:
> >
> > Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010
> > ...
> > Call trace:
> > led_put+0xe0/0x140
> > devm_led_release+0x6c/0x98
> >
> > Fix by adding a devlink between the consuming led-backlight device and the
> > supplying LED device.
> >
> > Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
>
> I've tested the patch wit LP8864 LED as a provider for led_bl, removing the
> underlying I2C bus. The patch avoids the crash for me (by removing led_bl device as well),
> thanks for fixing it!
>
> Tested-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
Would it make sense to add
Fixes: ae232e45acf9 ("backlight: add led-backlight driver")
?
--
Alexander Sverdlin
Siemens AG
www.siemens.com
next prev parent reply other threads:[~2025-05-12 12:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 8:53 [PATCH v4 0/8] Add support for GE SUNH hot-pluggable connector Luca Ceresoli
2024-09-17 8:53 ` [PATCH v4 1/8] dt-bindings: connector: add GE SUNH hotplug addon connector Luca Ceresoli
2024-09-17 10:29 ` Rob Herring (Arm)
2024-09-17 14:54 ` Luca Ceresoli
2024-09-17 8:53 ` [PATCH v4 2/8] drm/bridge: allow bridges to be informed about added and removed bridges Luca Ceresoli
2024-09-17 8:53 ` [PATCH v4 3/8] drm/encoder: add drm_encoder_cleanup_from() Luca Ceresoli
2024-09-17 8:53 ` [PATCH v4 4/8] drm/bridge: hotplug-bridge: add driver to support hot-pluggable DSI bridges Luca Ceresoli
2024-09-24 15:42 ` Luca Ceresoli
2024-09-17 8:53 ` [PATCH v4 5/8] i2c: i2c-core-of: follow i2c-parent phandle to probe devices from added nodes Luca Ceresoli
2024-12-12 19:12 ` Sverdlin, Alexander
2024-12-13 11:28 ` Luca Ceresoli
2024-12-13 11:45 ` Sverdlin, Alexander
2024-09-17 8:53 ` [PATCH v4 6/8] backlight: led-backlight: add devlink to supplier LEDs Luca Ceresoli
2024-09-19 12:43 ` Daniel Thompson
2024-09-20 12:41 ` Luca Ceresoli
2025-05-19 15:16 ` Luca Ceresoli
2025-05-12 11:39 ` Sverdlin, Alexander
2025-05-12 12:13 ` Sverdlin, Alexander [this message]
2025-05-16 18:47 ` Luca Ceresoli
2024-09-17 8:53 ` [PATCH RFC v4 7/8] driver core: devlink: do not unblock consumers without any drivers found Luca Ceresoli
2024-09-17 8:53 ` [PATCH v4 8/8] misc: add ge-addon-connector driver Luca Ceresoli
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=b5d2b71ffc38eb1980ce72994a20e8f6ee7869bd.camel@siemens.com \
--to=alexander.sverdlin@siemens.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
/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
all inboxes | Powered by JetHome®