From: Jameson Thies <jthies@google.com>
To: ukaszb@chromium.org, tzungbi@kernel.org,
linux-usb@vger.kernel.org, chrome-platform@lists.linux.dev
Cc: bleung@chromium.org, heikki.krogerus@linux.intel.com,
gregkh@linuxfoundation.org, dmitry.baryshkov@linaro.org,
abhishekpandit@chromium.org, akuchynski@chromium.org,
Jameson Thies <jthies@google.com>
Subject: [PATCH v1 1/2] platform/chrome: add PD_EVENT_INIT bit definition
Date: Tue, 4 Feb 2025 02:45:58 +0000 [thread overview]
Message-ID: <20250204024600.4138776-2-jthies@google.com> (raw)
In-Reply-To: <20250204024600.4138776-1-jthies@google.com>
Update cros_ec_commands.h to include a definition for PD_EVENT_INIT.
On platforms supporting UCSI, this host event type is sent when the PPM
initializes.
Signed-off-by: Jameson Thies <jthies@google.com>
---
include/linux/platform_data/cros_ec_commands.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/platform_data/cros_ec_commands.h b/include/linux/platform_data/cros_ec_commands.h
index ecf290a0c98f..1f4e4f2b89bb 100644
--- a/include/linux/platform_data/cros_ec_commands.h
+++ b/include/linux/platform_data/cros_ec_commands.h
@@ -5046,6 +5046,7 @@ struct ec_response_pd_status {
#define PD_EVENT_DATA_SWAP BIT(3)
#define PD_EVENT_TYPEC BIT(4)
#define PD_EVENT_PPM BIT(5)
+#define PD_EVENT_INIT BIT(6)
struct ec_response_host_event_status {
uint32_t status; /* PD MCU host event status */
--
2.48.1.362.g079036d154-goog
next prev parent reply other threads:[~2025-02-04 2:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 2:45 [PATCH v1 0/2] usb: typec: ucsi: Recover from CrOS EC sysjump Jameson Thies
2025-02-04 2:45 ` Jameson Thies [this message]
2025-02-04 14:35 ` [PATCH v1 1/2] platform/chrome: add PD_EVENT_INIT bit definition Benson Leung
2025-02-04 15:01 ` Łukasz Bartosik
2025-02-05 4:27 ` Tzung-Bi Shih
2025-02-04 2:45 ` [PATCH v1 2/2] usb: typec: ucsi: resume work after EC init Jameson Thies
2025-02-04 14:34 ` Benson Leung
2025-02-04 15:12 ` Łukasz Bartosik
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=20250204024600.4138776-2-jthies@google.com \
--to=jthies@google.com \
--cc=abhishekpandit@chromium.org \
--cc=akuchynski@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=tzungbi@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