From: Manikanta Maddireddy <mmaddireddy@nvidia.com>
To: <bhelgaas@google.com>, <lpieralisi@kernel.org>,
<kwilczynski@kernel.org>, <mani@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
<jingoohan1@gmail.com>, <vidyas@nvidia.com>, <cassel@kernel.org>,
<18255117159@163.com>
Cc: <linux-pci@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Manikanta Maddireddy" <mmaddireddy@nvidia.com>
Subject: [V5,0/9] Enhancements to pcie-tegra194 driver
Date: Sun, 8 Feb 2026 23:39:27 +0530 [thread overview]
Message-ID: <20260208180936.2026329-1-mmaddireddy@nvidia.com> (raw)
This series[1] was originally posted by Vidya Sagar, and I have rebased
it onto 6.19.0-rc6-next. I addressed review comments and split this into
two series, one for fixes and the other is for enhancements(current).
I verified these patches on Jetson AGX Orin(Tegra234 SoC).
Disabling L1SS capability based on support-clkreq device tree property
is moved to common DWC driver, so I reworked below patch to disable
just L1.2 capability on Tegra234 SoC.
- PCI: tegra194: Disable L1.2 capability of Tegra234 EP
I added below new patch to tune the ASPM parameters, commit message of the
patch has the details on the bug and fix.
- PCI: tegra194: Add ASPM L1 entrance latency config
I added more context in the commit message for below patch based on review
comment in V3.
- PCI: tegra194: Remove IRQF_ONESHOT flag during Endpoint interrupt registration
Rest of the patches are same as the original V3 series, just rebased them on
6.19.0-rc6-next.
Verification details.
- I verified both Root port and Endpoint mode controllers on Tegra234 SoC.
- Basic sanity Link up, configuration space access and BAR access are verified.
- I verified that ASPM L1.2 capability is disabled for Endpoint mode.
- I verified suspend to RAM tests with Endpoint mode.
[1] https://patchwork.kernel.org/project/linux-pci/patch/20221013183854.21087-1-vidyas@nvidia.com/
Manikanta Maddireddy (1):
PCI: tegra194: Add ASPM L1 entrance latency config
Vidya Sagar (8):
PCI: tegra194: Drive CLKREQ signal low explicitly
PCI: tegra194: Calibrate P2U for endpoint mode
PCI: tegra194: Remove IRQF_ONESHOT flag during Endpoint interrupt
registration
PCI: tegra194: Enable DMA interrupt
PCI: tegra194: Enable hardware hot reset mode in Endpoint
PCI: tegra194: Disable L1.2 capability of Tegra234 EP
dt-bindings: PCI: tegra194: Add monitor clock support
PCI: tegra194: Add core monitor clock support
.../bindings/pci/nvidia,tegra194-pcie-ep.yaml | 6 +-
.../bindings/pci/nvidia,tegra194-pcie.yaml | 6 +-
drivers/pci/controller/dwc/pcie-tegra194.c | 67 ++++++++++++++++++-
3 files changed, 76 insertions(+), 3 deletions(-)
--
2.34.1
next reply other threads:[~2026-02-08 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-08 18:09 Manikanta Maddireddy [this message]
2026-02-08 18:09 ` [V5,1/9] PCI: tegra194: Drive CLKREQ signal low explicitly Manikanta Maddireddy
2026-02-08 18:09 ` [V5,2/9] PCI: tegra194: Calibrate P2U for endpoint mode Manikanta Maddireddy
2026-02-08 18:09 ` [V5,3/9] PCI: tegra194: Remove IRQF_ONESHOT flag during Endpoint interrupt registration Manikanta Maddireddy
2026-02-08 18:09 ` [V5,4/9] PCI: tegra194: Enable DMA interrupt Manikanta Maddireddy
2026-02-08 18:09 ` [V5,5/9] PCI: tegra194: Enable hardware hot reset mode in Endpoint Manikanta Maddireddy
2026-02-08 18:09 ` [V5,6/9] PCI: tegra194: Disable L1.2 capability of Tegra234 EP Manikanta Maddireddy
2026-02-08 18:09 ` [V5,7/9] dt-bindings: PCI: tegra194: Add monitor clock support Manikanta Maddireddy
2026-02-08 18:09 ` [V5,8/9] PCI: tegra194: Add core " Manikanta Maddireddy
2026-02-08 18:09 ` [V5,9/9] PCI: tegra194: Add ASPM L1 entrance latency config 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=20260208180936.2026329-1-mmaddireddy@nvidia.com \
--to=mmaddireddy@nvidia.com \
--cc=18255117159@163.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jingoohan1@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--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@gmail.com \
--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®