From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Basavaraj Natikar <bnatikar@amd.com>
Cc: Basavaraj Natikar <Basavaraj.Natikar@amd.com>,
andreas.noever@gmail.com, westeri@kernel.org,
YehezkelShB@gmail.com, linux-usb@vger.kernel.org,
Mario Limonciello <superm1@kernel.org>,
Sanath S <Sanath.S@amd.com>
Subject: Re: [PATCH v3] thunderbolt: Assert downstream port reset on shutdown
Date: Thu, 11 Jun 2026 06:47:47 +0200 [thread overview]
Message-ID: <20260611044747.GV2990@black.igk.intel.com> (raw)
In-Reply-To: <59484ded-53da-4004-9ae8-785d3b89ce85@amd.com>
Hi,
On Wed, Jun 10, 2026 at 10:19:29PM +0530, Basavaraj Natikar wrote:
> Sounds good, I'll go with that structure and name the driver hook
> nhi_pci_shutdown(). One note: I kept the flag rather than threading a
> 'reset' parameter down, because tb_stop() needs the stored
> nhi->host_reset for the unload case anyway (the host_reset module param
> is static in nhi.c and not visible in tb_stop()), and passing a parameter
> would also change tb_domain_remove() and the cm_ops->stop() signature
> shared with icm.c. So:
>
> - nhi_pci_shutdown (tb_nhi_ops handler) -> nhi_pci_release_irq()
> - nhi_pci_do_remove(pdev, reset): sets nhi->host_reset = true when
> 'reset', then does the usual removal
> - nhi_pci_remove() -> nhi_pci_do_remove(pdev, false)
> - nhi_pci_shutdown() -> nhi_pci_do_remove(pdev, true) (the ->shutdown hook)
> tb_stop() keeps checking nhi->host_reset.
>
> Please let me know if this looks fine and I'll send v4.
Looks okay to me.
prev parent reply other threads:[~2026-06-11 4:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 8:50 [PATCH v3] thunderbolt: Assert downstream port reset on shutdown Basavaraj Natikar
2026-06-10 10:57 ` Mika Westerberg
2026-06-10 11:32 ` Basavaraj Natikar
2026-06-10 11:58 ` Mika Westerberg
2026-06-10 13:32 ` Basavaraj Natikar
2026-06-10 14:23 ` Mika Westerberg
2026-06-10 16:49 ` Basavaraj Natikar
2026-06-11 4:47 ` Mika Westerberg [this message]
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=20260611044747.GV2990@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=Sanath.S@amd.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=bnatikar@amd.com \
--cc=linux-usb@vger.kernel.org \
--cc=superm1@kernel.org \
--cc=westeri@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.