From: Manikanta Maddireddy <mmaddireddy@nvidia.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Jingoo Han <jingoohan1@gmail.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Krzysztof Wilczynski <kwilczynski@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Rob Herring <robh@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
Vidya Sagar <vidyas@nvidia.com>,
Niklas Cassel <cassel@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 2/3] PCI: tegra194: Avoid full Endpoint reinit on PERST#
Date: Mon, 19 Oct 2026 16:47:03 +0530 [thread overview]
Message-ID: <14da8b54-6e53-4466-83f2-e8a2cfa9e8a2@nvidia.com> (raw)
In-Reply-To: <6b4ffagwiepvhctdffzulxqvkie7rpk6eq47ssel4l6ilrkazr@j76sfnd3eush>
On 17/10/26 2:47 pm, Manivannan Sadhasivam wrote:
> On Wed, Sep 23, 2026 at 12:55:53PM +0530, Manikanta Maddireddy wrote:
>> Tegra194 and Tegra234 Endpoint mode receive PERST# as a fundamental
>> reset. Controller registers are lost across that reset, but DWC
>> Endpoint resources live for the controller lifetime.
>>
>
> What do you mean by 'DWC Endpoint resources are live for controller lifetime'?
> What resources you mean?
>
> - Mani
>
I mean the DWC software objects retained while the driver remains bound,
rather than hardware register contents. The existing initialization
already reuses several allocated objects; the unnecessary repeated
teardown/setup primarily concerns debugfs and eDMA where present. I’ll
name the resources explicitly and distinguish their lifetime from the
reset-lost register state.
- Manikanta
--
nvpublic
next prev parent reply other threads:[~2026-10-19 11:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 7:25 [PATCH 0/3] PCI: dwc: Avoid full EP cleanup " Manikanta Maddireddy
2026-09-23 7:25 ` [PATCH 1/3] PCI: dwc: Add Endpoint reinit helper Manikanta Maddireddy
2026-10-17 9:27 ` Manivannan Sadhasivam
2026-10-19 11:15 ` Manikanta Maddireddy
2026-09-23 7:25 ` [PATCH 2/3] PCI: tegra194: Avoid full Endpoint reinit on PERST# Manikanta Maddireddy
2026-10-17 9:17 ` Manivannan Sadhasivam
2026-10-19 11:17 ` Manikanta Maddireddy [this message]
2026-09-23 7:25 ` [PATCH 3/3] PCI: tegra194: Notify Endpoint functions on PERST# assert Manikanta Maddireddy
2026-10-17 9:22 ` Manivannan Sadhasivam
2026-10-19 11:19 ` Manikanta Maddireddy
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=14da8b54-6e53-4466-83f2-e8a2cfa9e8a2@nvidia.com \
--to=mmaddireddy@nvidia.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@kernel.org \
--cc=vidyas@nvidia.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®