From: Alexander Kurz <akurz@blala.de>
To: Lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>,
Griffin Kroah-Hartman <griffin@kroah.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
"Alexander Kurz" <akurz@blala.de>
Subject: [PATCH v3 0/2] modernize and fix mc13xxx-led driver
Date: Sun, 22 Nov 2026 17:06:13 +0000 [thread overview]
Message-ID: <20261122170615.31710-1-akurz@blala.de> (raw)
Main goal of this series is a fix enabling deferred probing of the
mc13xxx-led driver. The previous implementation has been dependent
on the MFD instance being present first and which has been changed
by commit 78efa53e715e ("leds: Init leds class earlier"), breaking
functionality. While working on it, replace the OF-specific API
with the newerunified device property API.
Signed-off-by: Alexander Kurz <akurz@blala.de>
---
Changes in v3:
- use dev_fwnode() to check parent availability, replacing dev_of_node().
(Sashiko)
- drop CONFIG_OF guard around mc13xxx_led_probe_dt() as all used. (Sashiko)
implementations should be safe for compilation with CONFIG_OF=n now.
- Link to v2: https://lore.kernel.org/all/20261122073235.26707-1-akurz@blala.de/
Changes in v2:
- removed unintended change of property "led-control" (Sashiko)
- Link to v1: https://lore.kernel.org/all/20261121074239.8745-1-akurz@blala.de/
Alexander Kurz (2):
leds: mc13783: Use unified device property API
leds: leds-mc13783: enable driver for deferred probe
drivers/leds/leds-mc13783.c | 37 +++++++++++++++----------------------
1 file changed, 15 insertions(+), 22 deletions(-)
--
2.39.5
next reply other threads:[~2026-11-22 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-22 17:06 Alexander Kurz [this message]
2026-11-22 17:06 ` [PATCH v3 1/2] leds: mc13783: Use unified device property API Alexander Kurz
2026-11-22 17:06 ` [PATCH v3 2/2] leds: leds-mc13783: enable driver for deferred probe Alexander Kurz
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=20261122170615.31710-1-akurz@blala.de \
--to=akurz@blala.de \
--cc=bhelgaas@google.com \
--cc=griffin@kroah.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
/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®