devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>
To: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
	Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Alexandre Courbot
	<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 3/6] arm64: tegra: Add Tegra210 support
Date: Fri, 22 May 2015 16:33:06 +0100	[thread overview]
Message-ID: <20150522153306.GA29424@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <20150522150514.GD19922-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>

On Fri, May 22, 2015 at 05:05:16PM +0200, Thierry Reding wrote:
> On Fri, May 22, 2015 at 02:38:00PM +0100, Catalin Marinas wrote:
> > So if you do it properly from the beginning with per-driver Kconfig
> > entry, I no longer see the point of an ARCH_TEGRA_*_SOC option. It may
> > be more convenient for people building end products but they should know
> > better what components are required, defconfig is rarely meant for them.
> 
> Your proposal also means that we'll have to go and add separate Kconfig
> entries for each SoC generation that a driver supports so that the SoC
> specific bits can be disabled.
> 
> So in order to get rid of one per-SoC Kconfig entry you'd prefer us to
> add per-SoC options per driver? Don't you think that's going to make
> things worse rather than improve them?
> 
> There are currently three drivers (off the top of my head) where we do
> this and each of them supports five existing generations plus the new
> Tegra210. So rather than having six symbols to select SoC generation
> support we'd be needing 18, and that's only counting existing drivers.

That's not what I meant. For example, you have a clk-tegra124.c file
built for two SoCs already and there may be more coming. Instead of
multiple obj-y of the same file, just add the entry below to
drivers/clk/tegra/Kconfig:

config CLK_TEGRA124
	bool "NVIDIA Tegra 124 clock"
	depends on ARCH_TEGRA_124_SOC || (ARM64 && ARCH_TEGRA)
	default y
	help
	  Used on Tegra 124, 132 etc.
	  ...

Note that I preserved the 124_SOC dependency for the 32-bit arm case.
But for arm64, just make it dependent on ARCH_TEGRA.

Once done, the Makefile only needs a single entry:

obj-$(CONFIG_TEGRA124) += clk-tegra124.o

-- 
Catalin

  parent reply	other threads:[~2015-05-22 15:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 14:57 [PATCH 1/6] arm64: tegra: Add Tegra132 support Thierry Reding
     [not found] ` <1431529065-20128-1-git-send-email-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-05-13 14:57   ` [PATCH 2/6] arm64: tegra: Add NVIDIA Tegra132 Norrin support Thierry Reding
2015-05-13 14:57   ` [PATCH 3/6] arm64: tegra: Add Tegra210 support Thierry Reding
     [not found]     ` <1431529065-20128-3-git-send-email-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-05-13 17:11       ` Catalin Marinas
     [not found]         ` <20150513171114.GA18655-M2fw3Uu6cmfZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2015-05-15 10:19           ` Thierry Reding
     [not found]             ` <20150515101913.GA20474-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>
2015-05-19 14:52               ` Catalin Marinas
     [not found]                 ` <20150519145211.GX21251-M2fw3Uu6cmfZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2015-05-19 15:17                   ` Thierry Reding
     [not found]                     ` <20150519151740.GA28161-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>
2015-05-22 13:38                       ` Catalin Marinas
     [not found]                         ` <20150522133800.GY29424-M2fw3Uu6cmfZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2015-05-22 15:05                           ` Thierry Reding
     [not found]                             ` <20150522150514.GD19922-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org>
2015-05-22 15:33                               ` Catalin Marinas [this message]
2015-05-22 15:37                           ` Stephen Warren
2015-05-13 14:57   ` [PATCH 4/6] arm64: tegra: Add NVIDIA P2530 compute module support Thierry Reding
2015-05-13 14:57   ` [PATCH 5/6] arm64: tegra: Add NVIDIA P2595 base board support Thierry Reding
2015-05-13 14:57   ` [PATCH 6/6] arm64: tegra: Add NVIDIA P2371 support 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=20150522153306.GA29424@e104818-lin.cambridge.arm.com \
    --to=catalin.marinas-5wv7dgnigg8@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
    --cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=will.deacon-5wv7dgnIgG8@public.gmane.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;
as well as URLs for NNTP newsgroup(s).