linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: Conditionals in dtsi files
Date: Fri, 13 Nov 2015 11:15:00 +0000	[thread overview]
Message-ID: <20151113111459.GA22469@leverpostej> (raw)
In-Reply-To: <5151887.Q3EmlRO4WY@wuerfel>

On Fri, Nov 13, 2015 at 10:43:11AM +0100, Arnd Bergmann wrote:
> On Friday 13 November 2015 10:33:50 Mason wrote:
> > Hello,
> > 
> > I'm wondering how much C preprocessor syntax one can use in DT files.
> > 
> > Suppose I have 2 board DTS (both including common.dtsi)
> > 
> > board_A.dts (1-core), board_B.dts (2-core)
> > 
> > Can I have in common.dtsi something along these lines:
> > 
> > 	cpus {
> > 		enable-method = "foo,bar";
> > 		#address-cells = <1>;
> > 		#size-cells = <0>;
> > 
> > 		cpu0: cpu at 0 {
> > 			compatible = "arm,cortex-a9";
> > 			device_type = "cpu";
> > 			reg = <0>;
> > 		};
> > 
> > #if CORE_COUNT > 1
> > 		cpu1: cpu at 1 {
> > 			compatible = "arm,cortex-a9";
> > 			device_type = "cpu";
> > 			reg = <1>;
> > 		};
> > #endif
> > 	};
> > 
> > 
> > board_A.dts would have
> > #define CORE_COUNT 1
> > #include "common.dtsi"
> > 
> > board_B.dts would have
> > #define CORE_COUNT 2
> > #include "common.dtsi"
> 
> I would prefer not using any preprocessor statements other than
> #include in .dts files.

I very much agree with this.

We should only have (simple) macros for symbolic names, and #includes
required for those to work.

Thanks,
Mark.

      reply	other threads:[~2015-11-13 11:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13  9:33 Conditionals in dtsi files Mason
2015-11-13  9:43 ` Arnd Bergmann
2015-11-13 11:15   ` Mark Rutland [this message]

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=20151113111459.GA22469@leverpostej \
    --to=mark.rutland@arm.com \
    --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 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).