From: Tzung-Bi Shih <tzungbi@kernel.org>
To: torvalds@linux-foundation.org
Cc: bleung@chromium.org, chrome-platform@lists.linux.dev,
tzungbi@kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] chrome-platform updates for v6.18
Date: Mon, 29 Sep 2025 09:08:16 +0800 [thread overview]
Message-ID: <aNncAJHyW430v7ny@tzungbi-laptop> (raw)
[-- Attachment #1: Type: text/plain, Size: 2646 bytes --]
Hi Linus,
Please pull chrome-platform updates for Linux v6.18.
Thanks,
Tzung-Bi
------
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/chrome-platform-v6.18
for you to fetch changes up to 48633acccf38d706d7b368400647bb9db9caf1ae:
Input: cros_ec_keyb - Defer probe until parent EC device is registered (2025-09-14 11:34:41 +0800)
----------------------------------------------------------------
chrome-platform: Updates for v6.18
* New
- Add a new API cros_ec_device_registered() for checking if the
cros_ec_deivce is ready.
* Improvements
- Use TRAILING_OVERLAP() to fix -Wflex-array-member-not-at-end
warning.
- Defer probe until parent EC device is ready in cros_ec_keyb.
* Cleanups
- Remove redundant and simplify code in cros_ec_chardev.
- Centralize cros_ec_device allocation and initialization to remove
duplicate code.
----------------------------------------------------------------
Gustavo A. R. Silva (1):
platform/chrome: cros_ec: Avoid -Wflex-array-member-not-at-end warning
Liao Yuanhong (1):
platform/chrome: wilco_ec: Remove redundant semicolons
Tzung-Bi Shih (7):
platform/chrome: cros_ec_chardev: Remove redundant struct field
platform/chrome: cros_ec_chardev: Decouple fops from struct cros_ec_dev
platform/chrome: Centralize cros_ec_device allocation
platform/chrome: Centralize common cros_ec_device initialization
platform/chrome: cros_ec: Separate initialization from cros_ec_register()
platform/chrome: cros_ec: Add a flag to track registration state
Input: cros_ec_keyb - Defer probe until parent EC device is registered
drivers/input/keyboard/cros_ec_keyb.c | 6 ++
drivers/platform/chrome/cros_ec.c | 90 ++++++++++++++++++----------
drivers/platform/chrome/cros_ec.h | 3 +
drivers/platform/chrome/cros_ec_chardev.c | 72 ++++++++++------------
drivers/platform/chrome/cros_ec_i2c.c | 9 +--
drivers/platform/chrome/cros_ec_ishtp.c | 6 +-
drivers/platform/chrome/cros_ec_lpc.c | 6 +-
drivers/platform/chrome/cros_ec_proto.c | 15 +++++
drivers/platform/chrome/cros_ec_rpmsg.c | 6 +-
drivers/platform/chrome/cros_ec_spi.c | 7 +--
drivers/platform/chrome/cros_ec_uart.c | 6 +-
drivers/platform/chrome/wilco_ec/telemetry.c | 2 +-
include/linux/platform_data/cros_ec_proto.h | 18 ++++--
13 files changed, 139 insertions(+), 107 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2025-09-29 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 1:08 Tzung-Bi Shih [this message]
2025-10-01 18:42 ` pr-tracker-bot
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=aNncAJHyW430v7ny@tzungbi-laptop \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®