All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] arm64, thunder: Add Kconfig option for Cavium Thunder SoC Family
Date: Mon, 08 Sep 2014 14:29:10 +0200	[thread overview]
Message-ID: <8282633.qB60Cj5UPD@wuerfel> (raw)
In-Reply-To: <20140908110131.GX4703@rric.localhost>

On Monday 08 September 2014 13:01:31 Robert Richter wrote:
> This is well hidden on x86, but each vendor has a config option. For
> AMD systems we have had our own option to disable vendor specific
> code, see CPU_SUP_AMD for example. Disabling this will remove all AMD
> specific code in the kernel. Of course this is enabled per default.
> 
> With ARCH_THUNDER I intended to do the same (you could name this also
> SOC_SUP_CAVIUM or so but I kept the current naming scheme). In patch
> 4/4 I have added the option to defconfig. This enables this per
> default and nobody has to deal with any option manually, just running
> make defconfig is fine.
> 
> Also, at least to disable building the dtb file for foo, you will need
> ARCH_FOO too. How else would you deal with dtb files then?

The only alternative I see is to build them all.

> Having ARCH_FOO might not be necessary for drivers. One could enable
> drivers manually, but this option is still a good reference for the
> drivers needed by foo. At some point you will carry tons of enabled
> drivers in your defconfig and you don't know which platform actually
> is using it. For generic drivers this might be fine.  But in my point
> of few, each soc specific driver should have an soc specific option
> too. Then you easily can remove an soc from the defconfig.

Yes, that's what I had in my example.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Robert Richter <rric@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	Will Deacon <Will.Deacon@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Robert Richter <robert.richter@caviumnetworks.com>,
	Olof Johansson <olof@lixom.net>,
	Radha Mohan Chintakuntla <rchintakuntla@cavium.com>
Subject: Re: [PATCH v2 1/4] arm64, thunder: Add Kconfig option for Cavium Thunder SoC Family
Date: Mon, 08 Sep 2014 14:29:10 +0200	[thread overview]
Message-ID: <8282633.qB60Cj5UPD@wuerfel> (raw)
In-Reply-To: <20140908110131.GX4703@rric.localhost>

On Monday 08 September 2014 13:01:31 Robert Richter wrote:
> This is well hidden on x86, but each vendor has a config option. For
> AMD systems we have had our own option to disable vendor specific
> code, see CPU_SUP_AMD for example. Disabling this will remove all AMD
> specific code in the kernel. Of course this is enabled per default.
> 
> With ARCH_THUNDER I intended to do the same (you could name this also
> SOC_SUP_CAVIUM or so but I kept the current naming scheme). In patch
> 4/4 I have added the option to defconfig. This enables this per
> default and nobody has to deal with any option manually, just running
> make defconfig is fine.
> 
> Also, at least to disable building the dtb file for foo, you will need
> ARCH_FOO too. How else would you deal with dtb files then?

The only alternative I see is to build them all.

> Having ARCH_FOO might not be necessary for drivers. One could enable
> drivers manually, but this option is still a good reference for the
> drivers needed by foo. At some point you will carry tons of enabled
> drivers in your defconfig and you don't know which platform actually
> is using it. For generic drivers this might be fine.  But in my point
> of few, each soc specific driver should have an soc specific option
> too. Then you easily can remove an soc from the defconfig.

Yes, that's what I had in my example.

	Arnd

  reply	other threads:[~2014-09-08 12:29 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05  7:46 [PATCH v2 0/4] arm64, thunder: Enable Cavium Thunder SoC Family Robert Richter
2014-09-05  7:46 ` Robert Richter
2014-09-05  7:46 ` [PATCH v2 1/4] arm64, thunder: Add Kconfig option for " Robert Richter
2014-09-05  7:46   ` Robert Richter
2014-09-05  8:39   ` Will Deacon
2014-09-05  8:39     ` Will Deacon
2014-09-05  9:21     ` Robert Richter
2014-09-05  9:21       ` Robert Richter
2014-09-05  9:25       ` Will Deacon
2014-09-05  9:25         ` Will Deacon
2014-09-05  9:36         ` Mark Rutland
2014-09-05  9:36           ` Mark Rutland
2014-09-05 10:51           ` Robert Richter
2014-09-05 10:51             ` Robert Richter
2014-09-05  9:32   ` Russell King - ARM Linux
2014-09-05  9:32     ` Russell King - ARM Linux
2014-09-05 10:45     ` Robert Richter
2014-09-05 10:45       ` Robert Richter
2014-09-05 11:05       ` Russell King - ARM Linux
2014-09-05 11:05         ` Russell King - ARM Linux
2014-09-05 12:51         ` Mark Rutland
2014-09-05 12:51           ` Mark Rutland
2014-09-05 14:04           ` Arnd Bergmann
2014-09-05 14:04             ` Arnd Bergmann
2014-09-05 14:22             ` Mark Rutland
2014-09-05 14:22               ` Mark Rutland
2014-09-05 16:25               ` Arnd Bergmann
2014-09-05 16:25                 ` Arnd Bergmann
2014-09-08 11:01                 ` Robert Richter
2014-09-08 11:01                   ` Robert Richter
2014-09-08 12:29                   ` Arnd Bergmann [this message]
2014-09-08 12:29                     ` Arnd Bergmann
2014-09-08 18:25                   ` Rob Herring
2014-09-08 18:25                     ` Rob Herring
2014-09-05  7:46 ` [PATCH v2 2/4] arm64, thunder: Add initial dts for Cavium Thunder SoC Robert Richter
2014-09-05  7:46   ` Robert Richter
2014-09-05 11:21   ` Arnd Bergmann
2014-09-05 11:21     ` Arnd Bergmann
2014-09-05 11:21     ` Arnd Bergmann
2014-09-11 14:51     ` Robert Richter
2014-09-11 14:51       ` Robert Richter
2014-09-11 14:51       ` Robert Richter
2014-09-05  7:46 ` [PATCH v2 3/4] arm64, thunder: Document devicetree bindings " Robert Richter
2014-09-05  7:46   ` Robert Richter
2014-09-05  8:42   ` Will Deacon
2014-09-05  8:42     ` Will Deacon
2014-09-05  8:42     ` Will Deacon
2014-09-05  9:32     ` Robert Richter
2014-09-05  9:32       ` Robert Richter
2014-09-05  9:39       ` Mark Rutland
2014-09-05  9:39         ` Mark Rutland
2014-09-05  9:39         ` Mark Rutland
2014-09-08  7:54         ` Robert Richter
2014-09-08  7:54           ` Robert Richter
2014-09-08  7:54           ` Robert Richter
2014-09-05  7:46 ` [PATCH v2 4/4] arm64, defconfig: Enable Cavium Thunder SoC in defconfig Robert Richter
2014-09-05  7:46   ` Robert Richter
2014-09-05  8:42 ` [PATCH v2 0/4] arm64, thunder: Enable Cavium Thunder SoC Family Will Deacon
2014-09-05  8:42   ` Will Deacon

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=8282633.qB60Cj5UPD@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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 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.