From: Niklas Cassel <cassel@kernel.org>
To: Thierry Reding <treding@nvidia.com>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Vidya Sagar <vidyas@nvidia.com>,
lpieralisi@kernel.org, kw@linux.com, robh@kernel.org,
bhelgaas@google.com, quic_schintav@quicinc.com,
johan+linaro@kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, jonathanh@nvidia.com,
kthota@nvidia.com, mmaddireddy@nvidia.com, sagar.tv@gmail.com
Subject: Re: [PATCH V1] PCI: tegra194: Add support for PCIe RC & EP in Tegra234 Platforms
Date: Fri, 7 Feb 2025 11:41:28 +0100 [thread overview]
Message-ID: <Z6XjWJd9jm0HHNXW@ryzen> (raw)
In-Reply-To: <zaj4vcbduaoceaueqq5hvbw5rvoksk5oz6via3jhfp7lyzlxnh@2umxfxphupgd>
On Tue, Feb 04, 2025 at 06:19:51PM +0100, Thierry Reding wrote:
> On Mon, Feb 03, 2025 at 10:29:32PM +0530, Manivannan Sadhasivam wrote:
> > On Tue, Jan 28, 2025 at 01:04:32PM +0100, Niklas Cassel wrote:
> > > Hello Vidya,
> > >
> > > On Tue, Jan 28, 2025 at 10:12:44AM +0530, Vidya Sagar wrote:
> > > > Add PCIe RC & EP support for Tegra234 Platforms.
> > >
> > > The commit log does leave quite a few questions unanswered.
> > >
> > > Since you are just updating the Kconfig and nothing else:
> > > Does the DT binding already have support for the Tegra234 SoC?
> > > Does the driver already have support for the Tegra234 SoC?
> > >
> > > Looking at the DT binding and driver, the answer to both questions
> > > is yes. (This should have been in the commit message IMO.)
> > >
> > >
> > > But that leads me to the question, since there is support for Tegra234
> > > SoC in the driver, does this means that this fixes a regression, e.g.
> > > the Kconfig ARCH_TEGRA_234_SOC was added after the driver support in
> > > this driver was added. In this case, you should have a Fixes: tag that
> > > points to the commit that added ARCH_TEGRA_234_SOC.
> > >
> > > Or has the the driver support for Tegra234 been "dead-code" since it
> > > was originally added? (Because without this patch, no one can have
> > > tested it, at least not without COMPILE_TEST.)
> > > In this case, you should add:
> > > Fixes: a54e19073718 ("PCI: tegra194: Add Tegra234 PCIe support")
> > >
> >
> > TBH, I don't like muddling with Kconfig like this. Ideally, the driver should
> > just depend on ARCH_TEGRA || COMPILE_TEST and the driver should be selected by
> > the relevant defconfig.
>
> ARCH_TEGRA is a symbol that exists both on 32-bit and 64-bit ARM. This
> driver is completely useless on 32-bit ARM and only used on a very small
> subset of 64-bit ARM devices. It doesn't make sense to be able to enable
> this if you want to build a kernel for say Tegra210.
Well, if you look in drivers/pci/controller/dwc/Kconfig
there are quite a few drivers that does:
depends on ARM64 or ARM and then a ARCH_ something.
I don't see why you can't do
depends on (ARCH_TEGRA && ARM64) || COMPILE_TEST
Kind regards,
Niklas
next prev parent reply other threads:[~2025-02-07 10:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 4:42 [PATCH V1] PCI: tegra194: Add support for PCIe RC & EP in Tegra234 Platforms Vidya Sagar
2025-01-28 12:04 ` Niklas Cassel
2025-02-03 16:59 ` Manivannan Sadhasivam
2025-02-04 17:19 ` Thierry Reding
2025-02-07 10:41 ` Niklas Cassel [this message]
2025-02-10 17:49 ` Manivannan Sadhasivam
2025-02-04 17:12 ` Thierry Reding
2025-02-07 10:32 ` Niklas Cassel
[not found] ` <BN9PR12MB5323E59E530FA1F87DE3C7FCB8F22@BN9PR12MB5323.namprd12.prod.outlook.com>
2025-02-10 17:50 ` manivannan.sadhasivam
2025-02-10 17:56 ` Vidya Sagar
2025-04-10 19:45 ` [PATCH V2] PCI: dwc: tegra194: Broaden architecture dependency Vidya Sagar
2025-04-11 5:40 ` Niklas Cassel
2025-04-16 15:43 ` kernel test robot
2025-04-16 16:09 ` Niklas Cassel
2025-04-16 17:15 ` kernel test robot
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=Z6XjWJd9jm0HHNXW@ryzen \
--to=cassel@kernel.org \
--cc=bhelgaas@google.com \
--cc=johan+linaro@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kthota@nvidia.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mmaddireddy@nvidia.com \
--cc=quic_schintav@quicinc.com \
--cc=robh@kernel.org \
--cc=sagar.tv@gmail.com \
--cc=treding@nvidia.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