From: Sanath S <Sanath.S@amd.com>
To: <mario.limonciello@amd.com>, <andreas.noever@gmail.com>,
<michael.jamet@intel.com>, <mika.westerberg@linux.intel.com>,
<YehezkelShB@gmail.com>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Sanath S <Sanath.S@amd.com>
Subject: [Patch v3 0/4] Add support for downstream port reset(DPR)
Date: Sat, 6 Jan 2024 22:27:19 +0530 [thread overview]
Message-ID: <20240106165723.3377789-1-Sanath.S@amd.com> (raw)
Tunnels created by boot firmware results in incorrect PCI resource
allocation, which results in failure of extending daisy chain.
This series aims to resolve inconsistent tunnels or paths created
by boot firmware.
Before:
+-03.1-[04-62]----00.0-[05-07]--+-02.0-[06]----00.0
| \-04.0-[07]--
After:
+-03.1-[04-62]----00.0-[05-62]--+-02.0-[06]----00.0
| \-04.0-[07-62]--
This series also aligns with windows behaviour of performing a teardown
of tunnels and resetting the downstream ports using DPR during the init
sequence.
Changes since V3:
- Remove discover_tunnel() api before resetting DPR.
- Add lane and protocol adapters reset in tb_switch_reset()
- Addition of tb_lc_reset_port() for TBT1, TBT2 and TBT3 routers.
- Addition of tb_path_deactivate_hop() api to help suppport path
reset of given hop index.
- Addition on new patch to store and indicate host router reset
status of USB4 v2
Changes since V2:
- Perform DPR only for USB4 routers.
- Update kernel-doc and return value to -EOPNOTSUPP.
- Limit delay range to 10-15ms.
Sanath S (4):
thunderbolt: Introduce usb4_port_reset() and tb_lc_reset_port()
thunderbolt: Extend tb_switch_reset() to support lane and protocol
adapter reset
thunderbolt: Store host router reset status in nhi_probe()
thunderbolt: Teardown tunnels and reset downstream ports created by
boot firmware
drivers/thunderbolt/domain.c | 5 +--
drivers/thunderbolt/icm.c | 2 +-
drivers/thunderbolt/lc.c | 44 +++++++++++++++++++++++++
drivers/thunderbolt/nhi.c | 19 +++++++----
drivers/thunderbolt/path.c | 13 ++++++++
drivers/thunderbolt/switch.c | 61 +++++++++++++++++++++++++++++++++--
drivers/thunderbolt/tb.c | 29 +++++++++++++----
drivers/thunderbolt/tb.h | 7 ++--
drivers/thunderbolt/tb_regs.h | 4 +++
drivers/thunderbolt/usb4.c | 39 ++++++++++++++++++++++
10 files changed, 202 insertions(+), 21 deletions(-)
--
2.34.1
next reply other threads:[~2024-01-06 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 16:57 Sanath S [this message]
2024-01-06 16:57 ` [Patch v3 1/4] thunderbolt: Introduce usb4_port_reset() and tb_lc_reset_port() Sanath S
2024-01-06 16:57 ` [Patch v3 2/4] thunderbolt: Extend tb_switch_reset() to support lane and protocol adapter reset Sanath S
2024-01-06 16:57 ` [Patch v3 3/4] thunderbolt: Store host router reset status in nhi_probe() Sanath S
2024-01-06 16:57 ` [Patch v3 4/4] thunderbolt: Teardown tunnels and reset downstream ports created by boot firmware Sanath S
2024-01-10 14:31 ` [Patch v3 0/4] Add support for downstream port reset(DPR) Mika Westerberg
2024-01-10 15:29 ` Sanath S
2024-01-22 11:27 ` Mika Westerberg
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=20240106165723.3377789-1-Sanath.S@amd.com \
--to=sanath.s@amd.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.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
all inboxes | Powered by JetHome®