From: Utkarsh Patel <utkarsh.h.patel@intel.com>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Cc: heikki.krogerus@linux.intel.com, pmalani@chromium.org,
chrome-platform@lists.linux.dev,
andriy.shevchenko@linux.intel.com, bleung@chromium.org,
Utkarsh Patel <utkarsh.h.patel@intel.com>
Subject: [PATCH v4 0/5] Displayport Alternate Mode 2.1 Support
Date: Tue, 19 Sep 2023 19:32:38 -0700 [thread overview]
Message-ID: <20230920023243.2494410-1-utkarsh.h.patel@intel.com> (raw)
This series enabels cable identification flow required for Displayport
Alternate Mode 2.1 support.
Please add this series to usb-next.
Changes in v4:
- Added [PATCH 3/5] back in this series with Reviewed-by tag from Heikki.
Changes in v3:
- Removed [PATCH 3/5] usb: pd: Add helper macro to get Type C cable speed
instead added the helper function in [PATCH 3/4].
- In [PATCH 3/4] Removed use of variable cable_speed.
Changes in v2:
- Added two new patches [PATCH 2/5] and [PATCH 3/5] in to this series.
- Removed [PATCH 2/4] platform/chrome: cros_ec: Add Displayport
Alternatemode 2.1 feature flag
- In [PATCH 4/5] Removed feature flag and separate function for DP2.1.
- In [PATCH 4/5] used cable vdos instead of host commands to get cable
details.
Utkarsh Patel (5):
usb: typec: Add Displayport Alternate Mode 2.1 Support
usb: typec: Add Active or Passive cable defination to cable discover
mode VDO
usb: pd: Add helper macro to get Type C cable speed
platform/chrome: cros_ec_typec: Add Displayport Alternatemode 2.1
Support
usb: typec: intel_pmc_mux: Configure Displayport Alternate mode 2.1
drivers/platform/chrome/cros_ec_typec.c | 28 ++++++++++++++++++++++++
drivers/usb/typec/altmodes/displayport.c | 5 ++++-
drivers/usb/typec/mux/intel_pmc_mux.c | 24 ++++++++++++++++++++
drivers/usb/typec/ucsi/displayport.c | 2 +-
drivers/usb/typec/ucsi/ucsi_ccg.c | 4 ++--
include/linux/usb/pd_vdo.h | 1 +
include/linux/usb/typec_dp.h | 28 ++++++++++++++++++++----
include/linux/usb/typec_tbt.h | 1 +
8 files changed, 85 insertions(+), 8 deletions(-)
--
2.25.1
next reply other threads:[~2023-09-20 2:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 2:32 Utkarsh Patel [this message]
2023-09-20 2:32 ` [PATCH v4 1/5] usb: typec: Add Displayport Alternate Mode 2.1 Support Utkarsh Patel
2023-09-20 2:32 ` [PATCH v4 2/5] usb: typec: Add Active or Passive cable defination to cable discover mode VDO Utkarsh Patel
2023-09-20 2:32 ` [PATCH v4 3/5] usb: pd: Add helper macro to get Type C cable speed Utkarsh Patel
2023-09-20 2:32 ` [PATCH v4 4/5] platform/chrome: cros_ec_typec: Add Displayport Alternatemode 2.1 Support Utkarsh Patel
2023-09-20 14:42 ` Andy Shevchenko
2023-09-25 15:54 ` Patel, Utkarsh H
2023-09-25 19:27 ` Andy Shevchenko
2023-09-28 1:31 ` Patel, Utkarsh H
2023-09-20 2:32 ` [PATCH v4 5/5] usb: typec: intel_pmc_mux: Configure Displayport Alternate mode 2.1 Utkarsh Patel
2023-09-20 9:10 ` Sergei Shtylyov
2023-09-26 2:00 ` Patel, Utkarsh H
2023-11-13 3:23 ` [PATCH v4 0/5] Displayport Alternate Mode 2.1 Support patchwork-bot+chrome-platform
2023-11-13 3:42 ` patchwork-bot+chrome-platform
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=20230920023243.2494410-1-utkarsh.h.patel@intel.com \
--to=utkarsh.h.patel@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmalani@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