From: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
linux-usb@vger.kernel.org
Cc: pmalani@chromium.org, jthies@google.com,
Abhishek Pandit-Subedi <abhishekpandit@chromium.org>,
"Christian A. Ehrhardt" <lk@c--e.de>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Fabrice Gasnier <fabrice.gasnier@foss.st.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hans de Goede <hdegoede@redhat.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rajaram Regupathy <rajaram.regupathy@intel.com>,
Saranya Gopal <saranya.gopal@intel.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v5 0/3] usb: typec: ucsi: Adding support for UCSI 3.0
Date: Fri, 9 Feb 2024 14:37:29 -0800 [thread overview]
Message-ID: <20240209223824.622869-1-abhishekpandit@chromium.org> (raw)
Hi Heikki,
This series starts the work adding UCSI 3.0 support to the UCSI driver.
There's a couple of pieces to start here:
* Add version checks and limit read size on 1.2.
* Update Connector Status and Connector Capability structures.
* Expose Partner PD revision from Capability data.
These were tested against on a 6.6 kernel running a usermode PPM against
a Realtek Evaluation board.
One additional note: there are a lot more unaligned fields in UCSI now
and the struct definitions are getting a bit out of hand. We can discuss
alternate mechanisms for defining these structs in the patch that
changes these structures.
Thanks,
Abhishek
Changes in v5:
- Change min_t to clamp
Changes in v4:
- Added missing Tested-By tags from v1 and reviewed-by tags.
- Fix BCD translation of PD Major Rev
- Replace IS_MIN_VERSION macro and just compare version directly.
Changes in v3:
- Change include to asm/unaligned.h and reorder include.
Changes in v2:
- Changed log message to DEBUG
- Formatting changes and update macro to use brackets.
- Fix incorrect guard condition when checking connector capability.
Abhishek Pandit-Subedi (3):
usb: typec: ucsi: Limit read size on v1.2
usb: typec: ucsi: Update connector cap and status
usb: typec: ucsi: Get PD revision for partner
drivers/usb/typec/ucsi/ucsi.c | 49 +++++++++++++++++++++++--
drivers/usb/typec/ucsi/ucsi.h | 67 ++++++++++++++++++++++++++++++++---
2 files changed, 110 insertions(+), 6 deletions(-)
--
2.43.0.687.g38aa6559b0-goog
next reply other threads:[~2024-02-09 22:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 22:37 Abhishek Pandit-Subedi [this message]
2024-02-09 22:37 ` [PATCH v5 1/3] usb: typec: ucsi: Limit read size on v1.2 Abhishek Pandit-Subedi
2024-02-09 22:37 ` [PATCH v5 2/3] usb: typec: ucsi: Update connector cap and status Abhishek Pandit-Subedi
2024-02-09 22:37 ` [PATCH v5 3/3] usb: typec: ucsi: Get PD revision for partner Abhishek Pandit-Subedi
2024-02-16 13:44 ` Bagas Sanjaya
2024-02-15 21:40 ` [PATCH v5 0/3] usb: typec: ucsi: Adding support for UCSI 3.0 Abhishek Pandit-Subedi
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=20240209223824.622869-1-abhishekpandit@chromium.org \
--to=abhishekpandit@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=jthies@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lk@c--e.de \
--cc=neil.armstrong@linaro.org \
--cc=pmalani@chromium.org \
--cc=rajaram.regupathy@intel.com \
--cc=saranya.gopal@intel.com \
/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).