From: Tzung-Bi Shih <tzungbi@kernel.org>
To: bleung@chromium.org, groeck@chromium.org,
linus.walleij@linaro.org, brgl@bgdev.pl,
hverkuil-cisco@xs4all.nl, mchehab@kernel.org, sre@kernel.org
Cc: tzungbi@kernel.org, chrome-platform@lists.linux.dev,
pmalani@chromium.org, linux-gpio@vger.kernel.org,
linux-media@vger.kernel.org, linux-pm@vger.kernel.org,
krzk@kernel.org
Subject: [PATCH v2 0/6] provide ID table for avoiding fallback match
Date: Mon, 1 Apr 2024 11:00:46 +0800 [thread overview]
Message-ID: <20240401030052.2887845-1-tzungbi@kernel.org> (raw)
Inspired by [1]. Turn all MODULE_ALIAS() in ChromeOS EC platform drivers into
proper platform_device_id table and MODULE_DEVICE_TABLE().
The series is basically looking for drivers from:
- `struct mfd_cell` in drivers/mfd/cros_ec_dev.c.
- grep -R MODULE_ALIAS drivers/platform/chrome/.
[1]: https://lore.kernel.org/chrome-platform/20240325-public-ucsi-h-v2-0-a6d716968bb1@chromium.org/T/#m2cc7d6f770cf0a48fb537bbaed655169c974f067
Changes from v1 (https://patchwork.kernel.org/project/chrome-platform/cover/20240329075630.2069474-1-tzungbi@kernel.org/):
- Split "platform/chrome: cros_kbd_led_backlight: provide ID table for avoiding
fallback match" into 2 commits.
- Remove patches that have been applied.
Tzung-Bi Shih (6):
media: platform: cros-ec: provide ID table for avoiding fallback match
gpio: cros-ec: provide ID table for avoiding fallback match
power: supply: cros_usbpd: provide ID table for avoiding fallback
match
power: supply: cros_pchg: provide ID table for avoiding fallback match
platform/chrome: cros_kbd_led_backlight: shrink the driver name
platform/chrome: cros_kbd_led_backlight: provide ID table for avoiding
fallback match
drivers/gpio/gpio-cros-ec.c | 8 ++++++++
drivers/media/cec/platform/cros-ec/cros-ec-cec.c | 9 ++++++++-
drivers/platform/chrome/cros_kbd_led_backlight.c | 11 +++++++++--
drivers/power/supply/cros_peripheral_charger.c | 11 +++++++++--
drivers/power/supply/cros_usbpd-charger.c | 11 +++++++++--
5 files changed, 43 insertions(+), 7 deletions(-)
--
2.44.0.478.gd926399ef9-goog
next reply other threads:[~2024-04-01 3:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 3:00 Tzung-Bi Shih [this message]
2024-04-01 3:00 ` [PATCH v2 1/6] media: platform: cros-ec: provide ID table for avoiding fallback match Tzung-Bi Shih
2024-04-08 7:36 ` Hans Verkuil
2024-04-01 3:00 ` [PATCH v2 2/6] gpio: " Tzung-Bi Shih
2024-04-02 8:58 ` Bartosz Golaszewski
2024-04-01 3:00 ` [PATCH v2 3/6] power: supply: cros_usbpd: " Tzung-Bi Shih
2024-04-01 3:00 ` [PATCH v2 4/6] power: supply: cros_pchg: " Tzung-Bi Shih
2024-04-01 3:00 ` [PATCH v2 5/6] platform/chrome: cros_kbd_led_backlight: shrink the driver name Tzung-Bi Shih
2024-04-01 10:02 ` Krzysztof Kozlowski
2024-04-01 10:19 ` Krzysztof Kozlowski
2024-04-01 10:42 ` Tzung-Bi Shih
2024-04-01 3:00 ` [PATCH v2 6/6] platform/chrome: cros_kbd_led_backlight: provide ID table for avoiding fallback match Tzung-Bi Shih
2024-04-01 10:03 ` Krzysztof Kozlowski
2024-04-01 9:45 ` (subset) [PATCH v2 0/6] " Sebastian Reichel
2024-05-27 2:55 ` patchwork-bot+chrome-platform
2024-05-27 3:07 ` patchwork-bot+chrome-platform
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=20240401030052.2887845-1-tzungbi@kernel.org \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=brgl@bgdev.pl \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=pmalani@chromium.org \
--cc=sre@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