From: Lee Jones <lee@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Tzung-Bi Shih <tzungbi@kernel.org>, Pavel Machek <pavel@ucw.cz>,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
Dustin Howett <dustin@howett.net>,
Mario Limonciello <mario.limonciello@amd.com>,
linux-leds@vger.kernel.org,
Rajas Paranjpe <paranjperajas@gmail.com>
Subject: Re: [PATCH v3 0/4] cros_kbd_led_backlight: allow binding through cros_ec mfd device
Date: Fri, 31 May 2024 16:53:56 +0100 [thread overview]
Message-ID: <20240531155356.GR1005600@google.com> (raw)
In-Reply-To: <0172f4a6-27da-43ca-8df3-93279d1ef903@t-8ch.de>
On Fri, 31 May 2024, Thomas Weißschuh wrote:
> On 2024-05-31 16:35:30+0000, Lee Jones wrote:
> > On Sun, 26 May 2024, Thomas Weißschuh wrote:
> >
> > > Extend the cros_ec MFD device to also load cros_kbd_led_backlight
> > > when the EC reports EC_FEATURE_PWM_KEYB.
> > > As the driver can now be probed multiple times, some preparation in the
> > > LED core is necessary to avoid name collisions.
> > >
> > > Patch 1 is a general cleanup for the LED core.
> > > Patch 2 modifies the LED core to skip the default collision handling.
> > > Patch 3 adds the new probing logic to cros_kbd_led_backlight.
> > > Patch 4 wires up the driver to the cros_ec mfd devices.
> > >
> > > The helper keyboard_led_is_mfd_device is a bit iffy.
> > > But using match data doesn't work.
> > >
> > > * driver_data from platform_device_id is overwritten by the mfd platform data
> > > * Setting the driver_data in drivers/mfd/cros_ec_dev.c would expose the
> > > internals of cros_kbd_led_backlight
> > >
> > > Tested on a Framework 13 AMD, Firmware 3.05, and a Jinlon Chromebook.
> > >
> > > To: Lee Jones <lee@kernel.org>
> > > To: Benson Leung <bleung@chromium.org>
> > > To: Guenter Roeck <groeck@chromium.org>
> > > To: Tzung-Bi Shih <tzungbi@kernel.org>
> > > To: Pavel Machek <pavel@ucw.cz>
> > > Cc: chrome-platform@lists.linux.dev
> > > Cc: linux-kernel@vger.kernel.org
> > > Cc: Dustin Howett <dustin@howett.net>
> > > Cc: Mario Limonciello <mario.limonciello@amd.com>
> > > Cc: linux-leds@vger.kernel.org
> > > Cc: Rajas Paranjpe <paranjperajas@gmail.com>
> > > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> > >
> > > Changes in v3:
> > > - Avoid probing multiple times (Confirmed by Rajas)
> > > - Add Kconfig dependency on MFD_CROS_EC_DEV
> > > - Link to v2: https://lore.kernel.org/r/20240511-cros_ec-kbd-led-framework-v2-0-b20c48109e46@weissschuh.net
> > >
> > > Changes in v2:
> > > - Fix build with CONFIG_MFD_CROS_EC_DEV=n (kernel test robot)
> > > - Split out mfd registration into own commit (Lee)
> > > - Simplify keyboard_led_is_mfd_device() with mfd_get_cell()
> > > - Link to v1: https://lore.kernel.org/r/20240505-cros_ec-kbd-led-framework-v1-1-bfcca69013d2@weissschuh.net
> > >
> > > ---
> > > Thomas Weißschuh (4):
> > > leds: class: warn about name collisions earlier
> > > leds: add flag to avoid automatic renaming of led devices
> > > platform/chrome: cros_kbd_led_backlight: allow binding through mfd device
> > > mfd: cros_ec: Register keyboard backlight subdevice
> > >
> > > drivers/leds/led-class.c | 9 +++---
> > > drivers/mfd/cros_ec_dev.c | 9 ++++++
> > > drivers/platform/chrome/Kconfig | 2 +-
> > > drivers/platform/chrome/cros_kbd_led_backlight.c | 40 ++++++++++++++++++++++--
> > > include/linux/leds.h | 1 +
> > > 5 files changed, 54 insertions(+), 7 deletions(-)
> >
> > Looks okay.
>
> Thanks.
>
> > Does the platform patch need to be applied with the others?
>
> Each patch depends on all its predecessors.
> (but I'm not sure I understood your question)
Does the Platform patch have 'build-time' deps on the others?
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-05-31 15:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-26 18:17 [PATCH v3 0/4] cros_kbd_led_backlight: allow binding through cros_ec mfd device Thomas Weißschuh
2024-05-26 18:17 ` [PATCH v3 1/4] leds: class: warn about name collisions earlier Thomas Weißschuh
2024-05-26 18:17 ` [PATCH v3 2/4] leds: add flag to avoid automatic renaming of led devices Thomas Weißschuh
2024-05-26 18:17 ` [PATCH v3 3/4] platform/chrome: cros_kbd_led_backlight: allow binding through mfd device Thomas Weißschuh
2024-05-28 5:37 ` Tzung-Bi Shih
2024-05-28 5:41 ` Thomas Weißschuh
2024-05-28 6:53 ` Tzung-Bi Shih
2024-06-03 1:57 ` Tzung-Bi Shih
2024-06-13 14:34 ` Lee Jones
2024-06-14 2:39 ` Tzung-Bi Shih
2024-05-26 18:17 ` [PATCH v3 4/4] mfd: cros_ec: Register keyboard backlight subdevice Thomas Weißschuh
2024-05-31 15:35 ` [PATCH v3 0/4] cros_kbd_led_backlight: allow binding through cros_ec mfd device Lee Jones
2024-05-31 15:49 ` Thomas Weißschuh
2024-05-31 15:53 ` Lee Jones [this message]
2024-05-31 15:59 ` Thomas Weißschuh
2024-06-03 1:54 ` Tzung-Bi Shih
2024-07-09 9:25 ` [GIT PULL] Immutable branch between MFD, LEDs and Platform due for the v6.11 merge window[GIT PULL] Immutable branch between MFD, LEDs and Platform due for the v6.11 merge window Lee Jones
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=20240531155356.GR1005600@google.com \
--to=lee@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dustin@howett.net \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=mario.limonciello@amd.com \
--cc=paranjperajas@gmail.com \
--cc=pavel@ucw.cz \
--cc=tzungbi@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;
as well as URLs for NNTP newsgroup(s).