From: Thierry Reding <thierry.reding@kernel.org>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: [GIT PULL] PCI: tegra: Changes for v7.1-rc1
Date: Sun, 29 Mar 2026 17:50:39 +0200 [thread overview]
Message-ID: <20260329155040.1448158-1-thierry.reding@kernel.org> (raw)
From: Thierry Reding <thierry.reding@gmail.com>
Hi Lorenzo, Bjorn,
The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-7.1-pci
for you to fetch changes up to a0c0906bb09ee2f64690b3b8ffb458b4dbbcb26e:
PCI: tegra: Add Tegra264 support (2026-03-28 15:00:05 +0100)
This is v3 of the Tegra264 PCI patches that can be found here:
https://lore.kernel.org/linux-pci/20260326135855.2795149-1-thierry.reding@kernel.org/
This looks ready now, but if there's any more feedback, I will happily
respin these driver patches.
Note that the shortlog and the diffstat below include the dependencies
from the Tegra tree, and that subset will go in through the ARM SoC tree
as well. Effectively what's new in this pull request is just the two PCI
patches, the rest is only included here to resolve the build time
dependencies.
Thanks,
Thierry
----------------------------------------------------------------
PCI: tegra: Changes for v7.1-rc1
This set of patches uses standard wait times for PCIe link monitoring
and build on top of that to add Tegra264 support. It also includes all
the Tegra-specific build-dependencies.
----------------------------------------------------------------
Thierry Reding (8):
firmware: tegra: bpmp: Rename Tegra239 to Tegra238
soc/tegra: Update BPMP ABI header
firmware: tegra: bpmp: Add tegra_bpmp_get_with_id() function
dt-bindings: pci: Document the NVIDIA Tegra264 PCIe controller
Merge branch for-7.1/dt-bindings into for-7.1/pci
Merge branch for-7.1/firmware into for-7.1/pci
PCI: Use standard wait times for PCIe link monitoring
PCI: tegra: Add Tegra264 support
.../bindings/pci/nvidia,tegra264-pcie.yaml | 149 +
drivers/firmware/tegra/bpmp.c | 34 +
drivers/pci/controller/Kconfig | 10 +-
drivers/pci/controller/Makefile | 1 +
.../controller/cadence/pcie-cadence-host-common.c | 6 +-
.../pci/controller/cadence/pcie-cadence-lga-regs.h | 5 -
drivers/pci/controller/mobiveil/pcie-mobiveil.c | 4 +-
drivers/pci/controller/mobiveil/pcie-mobiveil.h | 5 -
drivers/pci/controller/pci-aardvark.c | 7 +-
drivers/pci/controller/pcie-tegra264.c | 522 +++
drivers/pci/controller/pcie-xilinx-nwl.c | 9 +-
drivers/pci/controller/plda/pcie-starfive.c | 9 +-
drivers/pci/pci.h | 2 +
include/soc/tegra/bpmp-abi.h | 4573 ++++++++++++++++----
include/soc/tegra/bpmp.h | 8 +
15 files changed, 4412 insertions(+), 932 deletions(-)
create mode 100644 Documentation/devicetree/bindings/pci/nvidia,tegra264-pcie.yaml
create mode 100644 drivers/pci/controller/pcie-tegra264.c
next reply other threads:[~2026-03-29 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 15:50 Thierry Reding [this message]
2026-04-02 11:56 ` [GIT PULL] PCI: tegra: Changes for v7.1-rc1 Thierry Reding
2026-04-02 16:59 ` Manivannan Sadhasivam
2026-04-07 8:28 ` Thierry Reding
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=20260329155040.1448158-1-thierry.reding@kernel.org \
--to=thierry.reding@kernel.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox