From: s.trumtrar@pengutronix.de (Steffen Trumtrar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/5] ARM: zynq: dt: Convert to preprocessor includes
Date: Mon, 7 Apr 2014 20:02:28 +0200 [thread overview]
Message-ID: <20140407180228.GN12170@pengutronix.de> (raw)
In-Reply-To: <20140407171012.GC9952@obsidianresearch.com>
Hi!
On Mon, Apr 07, 2014 at 11:10:12AM -0600, Jason Gunthorpe wrote:
> On Mon, Apr 07, 2014 at 02:24:07PM +0200, Michal Simek wrote:
>
> > Device-tree BSP and in 2014.01 there will be new BSP which just
> > generate them directly from the Vivado tools which just target your
> > reference design. You can connect your custom IP (or Xilinx or 3rd
> > party) directly to the GIC which using different IRQ sensitivity
> > with whatever register addresses and make no sense to write it by
> > hand.
>
> On our Zynq design here we ended up being unwilling to use platform
> generation from Vivado. Basically all our IP was custom, so there was
> no win at all to invoking the complexity of the automatic tools.
>
> Thus we write the DT by hand, and our DT is complex, integrating
> peripherals that span two FPGAs.
>
> I think the in-kernel DT should use the kernel conventions, which
> means using #include and the binding constants over magic values.
>
ACK.
If in doubt follow common mainline practice. Although using includes
for DT is not necessarily common practice, readability of DTs is
really important IMHO.
Regards,
Steffen
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2014-04-07 18:02 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
2014-04-07 12:24 ` Michal Simek
2014-04-07 17:10 ` Jason Gunthorpe
2014-04-07 18:02 ` Steffen Trumtrar [this message]
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=20140407180228.GN12170@pengutronix.de \
--to=s.trumtrar@pengutronix.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 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).