From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Andrei Kuchynski <akuchynski@chromium.org>
Cc: "Benson Leung" <bleung@chromium.org>,
"Guenter Roeck" <groeck@chromium.org>,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
"Abhishek Pandit-Subedi" <abhishekpandit@chromium.org>,
"Jameson Thies" <jthies@google.com>,
"Łukasz Bartosik" <ukaszb@chromium.org>
Subject: Re: [PATCH 0/2] Add sysfs attributes to cros-ec-typec
Date: Wed, 5 Feb 2025 04:22:22 +0000 [thread overview]
Message-ID: <Z6LnfiPNQsh50OAv@google.com> (raw)
In-Reply-To: <20250203125947.2701106-1-akuchynski@chromium.org>
On Mon, Feb 03, 2025 at 12:59:45PM +0000, Andrei Kuchynski wrote:
> This patch series adds sysfs attributes to expose the state of EC.
> These attributes provide user-space applications with a read-only view of
> the EC state, eliminating the need for ioct calls and facilitating
> diagnostics.
>
> Tested on a ChromeOS Brya device with kernel 6.6. Verified that user-space
> applications can correctly read the new sysfs attributes.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
[1/2] platform/chrome: cros_ec_sysfs: Expose PD mux status
commit: e6a3215f78716d25ad60b002fd0585c04ffd5d01
[2/2] platform/chrome: cros_ec_sysfs: Expose AP_MODE_ENTRY feature state
commit: 435a3d78b87a93c52a4f84e36ba4a0857554c958
Thanks!
prev parent reply other threads:[~2025-02-05 4:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 12:59 [PATCH 0/2] Add sysfs attributes to cros-ec-typec Andrei Kuchynski
2025-02-03 12:59 ` [PATCH 1/2] platform/chrome: cros_ec_typec: Expose PD mux status via sysfs Andrei Kuchynski
2025-02-03 12:59 ` [PATCH 2/2] platform/chrome: cros_ec_typec: Expose AP_MODE_ENTRY feature state " Andrei Kuchynski
2025-02-05 4:22 ` Tzung-Bi Shih [this message]
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=Z6LnfiPNQsh50OAv@google.com \
--to=tzungbi@kernel.org \
--cc=abhishekpandit@chromium.org \
--cc=akuchynski@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=jthies@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ukaszb@chromium.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