diff options
| author | Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> | 2026-09-08 09:54:06 +0200 |
|---|---|---|
| committer | Vinod Koul <vkoul@kernel.org> | 2026-09-15 11:55:54 +0530 |
| commit | a6b889f58add38f72fbaec36e5d7ba91535d964a (patch) | |
| tree | 1c7ffdadbaa30b0776522cf8b7fb6f3e52e3ce4b /tools/perf/scripts/python/stackcollapse.py | |
| parent | 477b110dd60233f0e791fda3680bb0d96a8c9eae (diff) | |
| download | linux-next-a6b889f58add38f72fbaec36e5d7ba91535d964a.tar.gz linux-next-a6b889f58add38f72fbaec36e5d7ba91535d964a.zip | |
phy: core: Define TBT phy_mode
There exist OS-accessible USB4 and Thunderbolt PHYs that need specific
configuration. Define a new phy_mode for them.
Currently, USB4 and TBT3 are defined as submodes, because they're quite
distinct, most visibly in the electrical/analog aspects (slightly
different frequencies, timings, etc.). This results in a need to make
the PHY aware of the actual mode needed (at least in the Qualcomm
implementation, but I believe that'll be a general need).
Newer versions of TBT are basically supersets of USB4 with higher
host-side requirements, so these are not defined. This can always be
changed as necessary.
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Link: https://patch.msgid.link/20260908-topic-usb4phy-v5-2-73aac69578ef@oss.qualcomm.com
Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
