From: monstr@monstr.eu (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/5] ARM: zynq: dt: Convert to preprocessor includes
Date: Thu, 10 Apr 2014 12:44:20 +0200 [thread overview]
Message-ID: <53467604.1020400@monstr.eu> (raw)
In-Reply-To: <20140408172752.GC27776@obsidianresearch.com>
On 04/08/2014 07:27 PM, Jason Gunthorpe wrote:
> On Tue, Apr 08, 2014 at 09:03:27AM +0200, Michal Simek wrote:
>
>>> If in doubt follow common mainline practice. Although using includes
>>> for DT is not necessarily common practice, readability of DTs is
>>> really important IMHO.
>>
>> Let me give you one example. When you add xilinx intc controller
>> to zynq HW design which uses gic with headers you are using
>> then you will find out that sensitivity for both controllers
>> are just different.
>> This is just one case I am aware of. I expect there will be one more.
>
> I'm not sure I see the problem here, just because some bindings can't
> use the standard shared constants doesn't mean the GIC bindings and
> users should avoid them. The binding documentation is supposed to make
> it clear what is correct.
>
> It is just as easy to get confused with numbers, does 4 mean
> XILINX_INTC_IRQ_RISING or IRQ_TYPE_LEVEL_HIGH ?
That's why you have there biding documentation to exactly know what it is.
>> Using dtc preprocessor and macros improve DTS readability but at the same
>> time force other users to copy all necessary files from the kernel
>> to that projects which is just hassle.
>
> You can run the DTS through cpp before you export it out of the kernel
> environment, then you get a flat file with no includes.
What's the result?
1. DTSI and DTS together which completely break hierarchy
2. DTS without comments
It means, yes, you get a file when you go through cpp but different
then you have now.
> The shared kernel conventions are more important than constraints from
> outside projects.
zynq-7000.dtsi is fixed and you can't just change it based on your project.
For things which are in your board file like zynq-zc702 then you can use
whatever you like.
Maybe I just need some time to get used to it but currently...
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140410/36cce1d5/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Michal Simek <monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
To: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: Steffen Trumtrar
<s.trumtrar-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
Mike Looijmans <mike.looijmans-Oq418RWZeHk@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Russell King <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
Ian Campbell
<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
Michal Simek
<michal.simek-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Soren Brinkmann
<soren.brinkmann-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH v2 2/5] ARM: zynq: dt: Convert to preprocessor includes
Date: Thu, 10 Apr 2014 12:44:20 +0200 [thread overview]
Message-ID: <53467604.1020400@monstr.eu> (raw)
In-Reply-To: <20140408172752.GC27776-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]
On 04/08/2014 07:27 PM, Jason Gunthorpe wrote:
> On Tue, Apr 08, 2014 at 09:03:27AM +0200, Michal Simek wrote:
>
>>> If in doubt follow common mainline practice. Although using includes
>>> for DT is not necessarily common practice, readability of DTs is
>>> really important IMHO.
>>
>> Let me give you one example. When you add xilinx intc controller
>> to zynq HW design which uses gic with headers you are using
>> then you will find out that sensitivity for both controllers
>> are just different.
>> This is just one case I am aware of. I expect there will be one more.
>
> I'm not sure I see the problem here, just because some bindings can't
> use the standard shared constants doesn't mean the GIC bindings and
> users should avoid them. The binding documentation is supposed to make
> it clear what is correct.
>
> It is just as easy to get confused with numbers, does 4 mean
> XILINX_INTC_IRQ_RISING or IRQ_TYPE_LEVEL_HIGH ?
That's why you have there biding documentation to exactly know what it is.
>> Using dtc preprocessor and macros improve DTS readability but at the same
>> time force other users to copy all necessary files from the kernel
>> to that projects which is just hassle.
>
> You can run the DTS through cpp before you export it out of the kernel
> environment, then you get a flat file with no includes.
What's the result?
1. DTSI and DTS together which completely break hierarchy
2. DTS without comments
It means, yes, you get a file when you go through cpp but different
then you have now.
> The shared kernel conventions are more important than constraints from
> outside projects.
zynq-7000.dtsi is fixed and you can't just change it based on your project.
For things which are in your board file like zynq-zc702 then you can use
whatever you like.
Maybe I just need some time to get used to it but currently...
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Michal Simek <monstr@monstr.eu>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Steffen Trumtrar <s.trumtrar@pengutronix.de>,
Mike Looijmans <mike.looijmans@topic.nl>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Russell King <linux@arm.linux.org.uk>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Michal Simek <michal.simek@xilinx.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Kumar Gala <galak@codeaurora.org>,
Soren Brinkmann <soren.brinkmann@xilinx.com>
Subject: Re: [PATCH v2 2/5] ARM: zynq: dt: Convert to preprocessor includes
Date: Thu, 10 Apr 2014 12:44:20 +0200 [thread overview]
Message-ID: <53467604.1020400@monstr.eu> (raw)
In-Reply-To: <20140408172752.GC27776@obsidianresearch.com>
[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]
On 04/08/2014 07:27 PM, Jason Gunthorpe wrote:
> On Tue, Apr 08, 2014 at 09:03:27AM +0200, Michal Simek wrote:
>
>>> If in doubt follow common mainline practice. Although using includes
>>> for DT is not necessarily common practice, readability of DTs is
>>> really important IMHO.
>>
>> Let me give you one example. When you add xilinx intc controller
>> to zynq HW design which uses gic with headers you are using
>> then you will find out that sensitivity for both controllers
>> are just different.
>> This is just one case I am aware of. I expect there will be one more.
>
> I'm not sure I see the problem here, just because some bindings can't
> use the standard shared constants doesn't mean the GIC bindings and
> users should avoid them. The binding documentation is supposed to make
> it clear what is correct.
>
> It is just as easy to get confused with numbers, does 4 mean
> XILINX_INTC_IRQ_RISING or IRQ_TYPE_LEVEL_HIGH ?
That's why you have there biding documentation to exactly know what it is.
>> Using dtc preprocessor and macros improve DTS readability but at the same
>> time force other users to copy all necessary files from the kernel
>> to that projects which is just hassle.
>
> You can run the DTS through cpp before you export it out of the kernel
> environment, then you get a flat file with no includes.
What's the result?
1. DTSI and DTS together which completely break hierarchy
2. DTS without comments
It means, yes, you get a file when you go through cpp but different
then you have now.
> The shared kernel conventions are more important than constraints from
> outside projects.
zynq-7000.dtsi is fixed and you can't just change it based on your project.
For things which are in your board file like zynq-zc702 then you can use
whatever you like.
Maybe I just need some time to get used to it but currently...
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-04-10 10:44 UTC|newest]
Thread overview: 47+ 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 ` Soren Brinkmann
2014-04-04 23:14 ` Soren Brinkmann
2014-04-04 23:14 ` [PATCH v2 1/5] ARM: zynq: DT: Add 'clock-latency' property Soren Brinkmann
2014-04-04 23:14 ` Soren Brinkmann
2014-04-07 5:46 ` Michal Simek
2014-04-07 5:46 ` Michal Simek
2014-04-07 5:46 ` Michal Simek
2014-04-11 19:41 ` Sören Brinkmann
2014-04-11 19:41 ` Sören Brinkmann
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-04 23:14 ` Soren Brinkmann
2014-04-04 23:14 ` Soren Brinkmann
2014-04-07 5:58 ` Michal Simek
2014-04-07 5:58 ` Michal Simek
2014-04-07 5:58 ` Michal Simek
2014-04-07 12:17 ` Mike Looijmans
2014-04-07 12:17 ` Mike Looijmans
2014-04-07 12:17 ` Mike Looijmans
2014-04-07 12:24 ` Michal Simek
2014-04-07 12:24 ` Michal Simek
2014-04-07 12:24 ` Michal Simek
2014-04-07 17:10 ` Jason Gunthorpe
2014-04-07 17:10 ` Jason Gunthorpe
2014-04-07 17:10 ` Jason Gunthorpe
2014-04-07 18:02 ` Steffen Trumtrar
2014-04-07 18:02 ` Steffen Trumtrar
2014-04-07 18:02 ` Steffen Trumtrar
2014-04-08 7:03 ` Michal Simek
2014-04-08 7:03 ` Michal Simek
2014-04-08 7:03 ` Michal Simek
2014-04-08 17:27 ` Jason Gunthorpe
2014-04-08 17:27 ` Jason Gunthorpe
2014-04-08 17:27 ` Jason Gunthorpe
2014-04-10 10:44 ` Michal Simek [this message]
2014-04-10 10:44 ` Michal Simek
2014-04-10 10:44 ` Michal Simek
2014-04-07 15:39 ` Sören Brinkmann
2014-04-07 15:39 ` Sören Brinkmann
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 ` 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 ` Soren Brinkmann
2014-04-04 23:14 ` [PATCH v2 5/5] ARM: zynq: dt: Use #defines for clock specifiers Soren Brinkmann
2014-04-04 23:14 ` 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=53467604.1020400@monstr.eu \
--to=monstr@monstr.eu \
--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.