From: Tzung-Bi Shih <tzungbi@kernel.org>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, lee@kernel.org
Cc: nfraprado@collabora.com, angelogioacchino.delregno@collabora.com,
matthias.bgg@gmail.com, linux@weissschuh.net,
devicetree@vger.kernel.org, chrome-platform@lists.linux.dev,
linux-mediatek@lists.infradead.org, bleung@chromium.org,
groeck@chromium.org, tzungbi@kernel.org
Subject: [PATCH 0/2] platform/chrome: Remove cros-kbd-led-backlight
Date: Fri, 6 Dec 2024 03:14:03 +0000 [thread overview]
Message-ID: <20241206031405.1711996-1-tzungbi@kernel.org> (raw)
After applying 4c03a44e2668 ("arm64: dts: mediatek: mt8195-cherry: Remove
keyboard-backlight node"), there are no users for using the OF match.
Instead, the device is added via drivers/mfd/cros_ec_dev.c by
970c3a6b7aa3 ("mfd: cros_ec: Register keyboard backlight subdevice").
The series removes the OF match and the DT bindings.
Tzung-Bi Shih (2):
platform/chrome: cros_kbd_led_backlight: Remove OF match
dt-bindings: cros-ec: Remove google,cros-kbd-led-backlight
.../chrome/google,cros-kbd-led-backlight.yaml | 36 -----------
.../bindings/mfd/google,cros-ec.yaml | 3 -
.../platform/chrome/cros_kbd_led_backlight.c | 62 ++++---------------
3 files changed, 11 insertions(+), 90 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/chrome/google,cros-kbd-led-backlight.yaml
--
2.47.0.338.g60cca15819-goog
next reply other threads:[~2024-12-06 3:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 3:14 Tzung-Bi Shih [this message]
2024-12-06 3:14 ` [PATCH 1/2] platform/chrome: cros_kbd_led_backlight: Remove OF match Tzung-Bi Shih
2024-12-06 3:14 ` [PATCH 2/2] dt-bindings: cros-ec: Remove google,cros-kbd-led-backlight Tzung-Bi Shih
2024-12-10 23:01 ` Rob Herring (Arm)
2024-12-11 11:11 ` Lee Jones
2024-12-13 1:49 ` [PATCH 0/2] platform/chrome: Remove cros-kbd-led-backlight Tzung-Bi Shih
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=20241206031405.1711996-1-tzungbi@kernel.org \
--to=tzungbi@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=groeck@chromium.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@weissschuh.net \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=robh@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).