From: Niklas Cassel <cassel@kernel.org>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: "Jon Hunter" <jonathanh@nvidia.com>,
"Francesco Lavra" <flavra@baylibre.com>,
thierry.reding@gmail.com,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Mayank Rana" <mayank.rana@oss.qualcomm.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Shradha Todi" <shradha.t@samsung.com>,
"Thippeswamy Havalige" <thippeswamy.havalige@amd.com>,
"Inochi Amaoto" <inochiama@gmail.com>,
"Vidya Sagar" <vidyas@nvidia.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] pci: controller: tegra194: remove dependency on Tegra194 SoC
Date: Mon, 5 Jan 2026 13:13:55 +0100 [thread overview]
Message-ID: <aVurA-MUECufgTw0@ryzen> (raw)
In-Reply-To: <q2iezy4uydlvwgo6m6yv2nlucafyvxgonm2o5q3g32p73vemwb@x33rmfffnwlu>
On Mon, Jan 05, 2026 at 05:38:34PM +0530, Manivannan Sadhasivam wrote:
> On Mon, Jan 05, 2026 at 11:56:37AM +0000, Jon Hunter wrote:
> >
> >
> > On 05/01/2026 09:09, Niklas Cassel wrote:
> > > On Mon, Jan 05, 2026 at 02:09:34PM +0530, Manivannan Sadhasivam wrote:
> > > > On Fri, Jan 02, 2026 at 10:58:15AM +0000, Jon Hunter wrote:
> > > > >
> > > > > On 23/12/2025 06:45, Manivannan Sadhasivam wrote:
> > > > > > On Wed, Nov 26, 2025 at 11:25:30AM +0100, Francesco Lavra wrote:
> > > > > >
> > > > > > + Tegra maintainers
> > > > > >
> > > > > > > This driver runs (for both host and endpoint operation) also on other Tegra
> > > > > > > SoCs (e.g. Tegra234).
> > > > > > > Replace the Kconfig dependency on ARCH_TEGRA_194_SOC with a more generic
> > > > > > > dependency on ARCH_TEGRA; in addition, amend the Kconfig help text to
> > > > > > > reflect the fact that this driver is no longer exclusive to Tegra194.
> > > > > > >
> > > > > >
> > > > > > I vaguely remember asking about this a while back during some other patch review
> > > > > > and I don't remember what we concluded.
> > > > > > > Thierry, Jon, thoughts?
> > > > >
> > > > > So ARCH_TEGRA means that this can be enabled for the legacy 32-bit Tegra
> > > > > devices as well as the current 64-bit Tegra devices (such as Tegra194).
> > > > > Given that this driver is only used for Tegra194 and Tegra234, it seems it
> > > > > would be better to only enable this for Tegra194 and Tegra234 instead of any
> > > > > Tegra.
> > > > >
> > > >
> > > > The dependency means, whenever someone tries to enable PCIE_TEGRA194_HOST,
> > > > ARCH_TEGRA should be enabled. So as long as someone not trying to enable
> > > > PCIE_TEGRA194_HOST for 32bit Tegra systems, ARCH_TEGRA should work fine and
> > > > PCIE_TEGRA194_HOST is not selected by arch/arm/configs/tegra_defconfig. So I
> > > > don't see any blocker with this patch. In fact, many other archs do the same.
> > > >
> > > > But I don't like extending the Kconfig with per SoC dependency as it won't
> > > > scale.
> > >
> > > We already have a patch from Vidya:
> > > [PATCH V4] PCI: dwc: tegra194: Broaden architecture dependency
> > > that was sent 2025-05-08
> > >
> > > Back then, the reason why it wasn't merged was because it required a
> > > similar change to the PHY driver to go in first:
> > > https://lore.kernel.org/linux-pci/174722268141.85510.14696275121588719556.b4-ty@kernel.org/
> > >
> > > The PHY driver change was merged in v6.16:
> > > 0c2228731974 ("phy: tegra: p2u: Broaden architecture dependency")
> > >
> > > So, I think we could just merge:
> > > https://lore.kernel.org/linux-pci/20250508051922.4134041-1-vidyas@nvidia.com/
> > >
> > > (Assuming it still applies.)
> >
> > Yes it does and applying Sagar's patch is fine with me. So it you want to
> > apply Sagar's patch please add my ...
> >
>
> Don't we need:
>
> depends on (ARCH_TEGRA && ARM64) || COMPILE_TEST
This is exactly what I originally suggested to Vidya:
https://lore.kernel.org/linux-pci/Z6XjWJd9jm0HHNXW@ryzen/
>
> in the above patch?
The above patch instead has:
depends on ARCH_TEGRA && (ARM64 || COMPILE_TEST)
I don't know why Vidya did not use my suggestion exactly, but I guess I
assumed that he had a reason not to use my suggestion exactly.
Kind regards,
Niklas
next prev parent reply other threads:[~2026-01-05 12:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 10:25 [PATCH] pci: controller: tegra194: remove dependency on Tegra194 SoC Francesco Lavra
2025-12-23 6:45 ` Manivannan Sadhasivam
2026-01-02 10:58 ` Jon Hunter
2026-01-05 8:39 ` Manivannan Sadhasivam
2026-01-05 9:09 ` Niklas Cassel
2026-01-05 11:56 ` Jon Hunter
2026-01-05 12:08 ` Manivannan Sadhasivam
2026-01-05 12:13 ` Niklas Cassel [this message]
2026-01-05 12:17 ` Manivannan Sadhasivam
2026-01-05 12:18 ` Jon Hunter
2026-01-05 12:21 ` Manivannan Sadhasivam
2026-01-05 12:23 ` Jon Hunter
2026-01-05 12:28 ` Manivannan Sadhasivam
2026-01-05 12:21 ` Niklas Cassel
2026-01-05 11:55 ` Jon Hunter
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=aVurA-MUECufgTw0@ryzen \
--to=cassel@kernel.org \
--cc=bhelgaas@google.com \
--cc=flavra@baylibre.com \
--cc=inochiama@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=mayank.rana@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=shradha.t@samsung.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=thippeswamy.havalige@amd.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 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.