From: Thierry Reding <thierry.reding@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: Mikko Perttunen <mperttunen@nvidia.com>,
linux-tegra@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
"open list:COMMON CLK FRAMEWORK" <linux-clk@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2] firmware/tegra: add COMPILE_TEST
Date: Tue, 24 Mar 2026 12:33:37 +0100 [thread overview]
Message-ID: <acJ1humept5gbQlF@orome> (raw)
In-Reply-To: <CAKxU2N9E-9HLCJfGYD_r+qaW03fLz9NVW=RWuPvotCbSxv3ueA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2174 bytes --]
On Mon, Mar 23, 2026 at 11:42:18PM -0700, Rosen Penev wrote:
> On Mon, Mar 23, 2026 at 11:01 PM Mikko Perttunen <mperttunen@nvidia.com> wrote:
> >
> > On Tuesday, March 24, 2026 10:57 AM Rosen Penev wrote:
> > > For this driver specifically, there's no arch specific stuff needed.
> > >
> > > Build the tegra clk stuff as tegra_bpmp_init_clocks is defined there.
> > > CLK_TEGRA_BPMP also depends on TEGRA_BPMP.
> > >
> > > Signed-off-by: Rosen Penev <rosenp@gmail.com>
> > > ---
> > > v2: also build the tegra clk stuff.
> > > drivers/clk/Makefile | 2 +-
> > > drivers/firmware/tegra/Kconfig | 4 ++--
> > > 2 files changed, 3 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/drivers/clk/Makefile b/drivers/clk/Makefile
> > > index 760d9643705f..334d5c522394 100644
> > > --- a/drivers/clk/Makefile
> > > +++ b/drivers/clk/Makefile
> > > @@ -154,7 +154,7 @@ obj-$(CONFIG_ARCH_STM32) += stm32/
> > > obj-y += starfive/
> > > obj-$(CONFIG_ARCH_SUNXI) += sunxi/
> > > obj-y += sunxi-ng/
> > > -obj-$(CONFIG_ARCH_TEGRA) += tegra/
> > > +obj-y += tegra/
> >
> > clk/tegra/Makefile doesn't separately check for ARCH_TEGRA, so this will cause
> > much of it to get built on non-Tegra platforms as well.
> Sure. It builds fine.
I think the point that Mikko was trying to make is that with the current
setup you get the Tegra clock code built on all platforms, whether you
enable ARCH_TEGRA or not. Meaning you will get this included in your
kernel builds even on x86 or MIPS systems, or ARM systems that don't
enable any Tegra code.
If you really want to make this build with COMPILE_TEST, the right way
to do so is by adding a dedicated Kconfig symbol that uses something
like:
config CLK_TEGRA
...
depends ARCH_TEGRA || COMPILE_TEST
and then use that symbol instead of CONFIG_ARCH_TEGRA above:
obj-$(CONFIG_CLK_TEGRA) += tegra/
That way you ensure that it gets enabled for build testing or if Tegra
support is explicitly enabled.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-03-24 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 1:57 [PATCHv2] firmware/tegra: add COMPILE_TEST Rosen Penev
2026-03-24 6:01 ` Mikko Perttunen
2026-03-24 6:42 ` Rosen Penev
2026-03-24 11:33 ` Thierry Reding [this message]
2026-03-26 19:35 ` kernel test robot
2026-03-26 19:35 ` kernel test robot
2026-03-26 21:51 ` 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=acJ1humept5gbQlF@orome \
--to=thierry.reding@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=mturquette@baylibre.com \
--cc=rosenp@gmail.com \
--cc=sboyd@kernel.org \
--cc=thierry.reding@gmail.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