linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mike.looijmans@topic.nl (Mike Looijmans)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/5] ARM: zynq: dt: Convert to preprocessor includes
Date: Mon, 7 Apr 2014 14:17:24 +0200	[thread overview]
Message-ID: <53429754.8080105@topic.nl> (raw)
In-Reply-To: <53423E75.3020008@monstr.eu>

?On 04/07/2014 07:58 AM, Michal Simek wrote:
> Hi Soren,
>
> On 04/05/2014 01:14 AM, Soren Brinkmann wrote:
>> Convert all Zynq DT files to the dtc preprocessor include syntax.
>> This allows to include header files in the devicetrees like other
>> SoC-types already do.
>>
>> Inspired-by: Steffen Trumtrar <s.trumtrar@pengutronix.de>
>> (http://www.spinics.net/lists/arm-kernel/msg319832.html)
>>
>> Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com>
>
> These 4 patches needs more wider discussion if this is helpful or
> not. Currently I can't see any value in it because everything
> is just generated and fixed. I think I had the same discussion
> with Laurent some weeks ago regarding this.

I would be kinda neutral here. I'd consider it helpful, it improves 
readability (regardless of whether they are generated or hand crafted). That's 
convenient for things like interrupt sensitivity, I can't remember whether 4 
is level or edge type. On the other hand, the clock indices are just as much 
magic numbers as the memory addresses. If I suspect an error in that area, I'd 
start by lokking in /sys/kernel/debug/clk but wouldn't start in the DT.

> IRC the origin idea to use this was especially for people who
> writing these DTS by hand which is not our case - at least
> for majority of our customers.

I write them by hand. Is there any other way?

Mike.


Met vriendelijke groet / kind regards,

Mike Looijmans

TOPIC Embedded Systems
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: (+31) (0) 499 33 69 79
Telefax:  (+31) (0) 499 33 69 70
E-mail: mike.looijmans at topic.nl
Website: www.topic.nl

Please consider the environment before printing this e-mail

Visit us at the Hannover Messe 7 - 11 April 2014 - Hall 002/D10 (Dutch Pavillion)
http://www.hannovermesse.de/exhibitor/topic-embedded-products/V229623

  reply	other threads:[~2014-04-07 12:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 23:14 [PATCH v2 0/5] ARM: zynq: DT update Soren Brinkmann
2014-04-04 23:14 ` [PATCH v2 1/5] ARM: zynq: DT: Add 'clock-latency' property Soren Brinkmann
2014-04-07  5:46   ` Michal Simek
2014-04-11 19:41     ` Sören Brinkmann
2014-04-04 23:14 ` [PATCH v2 2/5] ARM: zynq: dt: Convert to preprocessor includes Soren Brinkmann
2014-04-07  5:58   ` Michal Simek
2014-04-07 12:17     ` Mike Looijmans [this message]
2014-04-07 12:24       ` Michal Simek
2014-04-07 17:10         ` Jason Gunthorpe
2014-04-07 18:02           ` Steffen Trumtrar
2014-04-08  7:03             ` Michal Simek
2014-04-08 17:27               ` Jason Gunthorpe
2014-04-10 10:44                 ` Michal Simek
2014-04-07 15:39       ` Sören Brinkmann
2014-04-04 23:14 ` [PATCH v2 3/5] ARM: zynq: dt: Use #defines for interrupt specifiers Soren Brinkmann
2014-04-04 23:14 ` [PATCH v2 4/5] dt-bindings: clock: Add Zynq-7000 header Soren Brinkmann
2014-04-04 23:14 ` [PATCH v2 5/5] ARM: zynq: dt: Use #defines for clock specifiers Soren Brinkmann

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=53429754.8080105@topic.nl \
    --to=mike.looijmans@topic.nl \
    --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).