All of lore.kernel.org
 help / color / mirror / Atom feed
From: scottwood@freescale.com (Scott Wood)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/3] ARM: use C pre-processor with dtc
Date: Tue, 25 Sep 2012 14:59:11 -0500	[thread overview]
Message-ID: <1348603151.5565.20@snotra> (raw)
In-Reply-To: <20120925195127.GA19350@sirena.org.uk> (from broonie@opensource.wolfsonmicro.com on Tue Sep 25 14:51:27 2012)

On 09/25/2012 02:51:27 PM, Mark Brown wrote:
> On Tue, Sep 25, 2012 at 02:35:46PM -0500, Scott Wood wrote:
> 
> > Do you have an example of where you'd actually benefit from this?
> > I'd think most things could either be done reasonably well with
> > what's built into DTC (see what we've done in
> > arch/powerpc/boot/dts/fsl), or would need math expression support in
> > DTC (or has that been added?).
> 
> The constant example is the magic numbers we need to embed into DTs  
> for
> things like interrupt modes, making them human readable would be a  
> real
> win.

Wasn't there a patch for named constant support in dtc a while back?
Hmm:  
https://lists.ozlabs.org/pipermail/devicetree-discuss/2012-January/011184.html

I'm not sure that going down the CPP path is better than the  
possibility of named constants having a different syntax from  
macros/functions.  It would be one thing if someone were actively  
working on the latter, but this paralysis seems to be a case of the  
perfect being the enemy of the good.

-Scott

WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Mark Brown
	<broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
Cc: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
	Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [RFC PATCH 0/3] ARM: use C pre-processor with dtc
Date: Tue, 25 Sep 2012 14:59:11 -0500	[thread overview]
Message-ID: <1348603151.5565.20@snotra> (raw)
In-Reply-To: <20120925195127.GA19350-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> (from broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org on Tue Sep 25 14:51:27 2012)

On 09/25/2012 02:51:27 PM, Mark Brown wrote:
> On Tue, Sep 25, 2012 at 02:35:46PM -0500, Scott Wood wrote:
> 
> > Do you have an example of where you'd actually benefit from this?
> > I'd think most things could either be done reasonably well with
> > what's built into DTC (see what we've done in
> > arch/powerpc/boot/dts/fsl), or would need math expression support in
> > DTC (or has that been added?).
> 
> The constant example is the magic numbers we need to embed into DTs  
> for
> things like interrupt modes, making them human readable would be a  
> real
> win.

Wasn't there a patch for named constant support in dtc a while back?
Hmm:  
https://lists.ozlabs.org/pipermail/devicetree-discuss/2012-January/011184.html

I'm not sure that going down the CPP path is better than the  
possibility of named constants having a different syntax from  
macros/functions.  It would be one thing if someone were actively  
working on the latter, but this paralysis seems to be a case of the  
perfect being the enemy of the good.

-Scott

  reply	other threads:[~2012-09-25 19:59 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25 19:06 [RFC PATCH 0/3] ARM: use C pre-processor with dtc Stephen Warren
2012-09-25 19:06 ` Stephen Warren
2012-09-25 19:06 ` [RFC PATCH 1/3] kbuild: introduce cmd_dtc_cpp Stephen Warren
2012-09-25 19:06   ` Stephen Warren
2012-09-27  5:44   ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-27  5:44     ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-27 15:39     ` Stephen Warren
2012-09-27 15:39       ` Stephen Warren
2012-09-27 17:40       ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-27 17:40         ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-25 19:06 ` [RFC PATCH 2/3] ARM: use cmd_dtc_cpp for compilation of *.dts-cpp to *.dtb Stephen Warren
2012-09-25 19:06   ` Stephen Warren
2012-09-27  5:47   ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-27  5:47     ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-27 15:40     ` Stephen Warren
2012-09-27 15:40       ` Stephen Warren
2012-09-25 19:06 ` [RFC PATCH 3/3] ARM: tegra: compile all DT files with cpp Stephen Warren
2012-09-25 19:06   ` Stephen Warren
2012-09-25 19:35 ` [RFC PATCH 0/3] ARM: use C pre-processor with dtc Scott Wood
2012-09-25 19:35   ` Scott Wood
2012-09-25 19:51   ` Mark Brown
2012-09-25 19:51     ` Mark Brown
2012-09-25 19:59     ` Scott Wood [this message]
2012-09-25 19:59       ` Scott Wood
2012-09-25 20:05       ` Stephen Warren
2012-09-25 20:05         ` Stephen Warren
2012-09-25 20:05       ` Mark Brown
2012-09-25 20:05         ` Mark Brown
2012-09-25 19:51   ` Stephen Warren
2012-09-25 19:51     ` Stephen Warren
2012-09-25 23:46     ` Tony Lindgren
2012-09-25 23:46       ` Tony Lindgren
2012-09-27  5:40 ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-27  5:40   ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-27 15:38   ` Stephen Warren
2012-09-27 15:38     ` Stephen Warren
2012-09-27 17:27     ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-27 17:27       ` Jean-Christophe PLAGNIOL-VILLARD

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=1348603151.5565.20@snotra \
    --to=scottwood@freescale.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 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.