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 v7.0
Date: Mon, 9 Feb 2026 03:23:04 +0000 [thread overview]
Message-ID: <aYlTGG_NABjz3a-K@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1808 bytes --]
Hi Linus,
Please pull chrome-platform updates for Linux v7.0.
Thanks,
Tzung-Bi
------
The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:
Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/chrome-platform-v7.0
for you to fetch changes up to 520e345dfdab89aed4a0ad98d5ec35086661a11a:
platform/chrome: lightbar: Use flexible array member (2026-02-04 04:38:13 +0000)
----------------------------------------------------------------
chrome-platform: Updates for v7.0
* New
(cros_ec_lightbar)
- Report the number of exposed LED segments via sysfs.
- Support large sequence of program to be transmitted.
* Fixes
- Don't touch fwnode_handle::dev which is a private field.
- Fix wrong assignment for response size in cros_ec_lightbar.
* Cleanups
- Use acpi_get_local_u64_address() helper.
----------------------------------------------------------------
Andy Shevchenko (2):
platform/chrome: cros_typec_switch: Don't touch struct fwnode_handle::dev
platform/chrome: cros_typec_switch: Use acpi_get_local_u64_address()
Gwendal Grignou (4):
platform/chrome: lightbar: Report number of segments
platform/chrome: lightbar: Add support for large sequence
platform/chrome: lightbar: Fix lightbar_program_ex alignment
platform/chrome: lightbar: Use flexible array member
Tzung-Bi Shih (1):
platform/chrome: cros_ec_lightbar: Fix response size initialization
drivers/platform/chrome/cros_ec_lightbar.c | 133 +++++++++++++++++++------
drivers/platform/chrome/cros_typec_switch.c | 19 +---
include/linux/platform_data/cros_ec_commands.h | 24 +++++
3 files changed, 134 insertions(+), 42 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2026-02-09 3:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 3:23 Tzung-Bi Shih [this message]
2026-02-11 20:28 ` [GIT PULL] chrome-platform updates for v7.0 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=aYlTGG_NABjz3a-K@google.com \
--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