On Fri, Nov 22, 2019 at 09:40:43PM +0100, mail@xxxxxxxxxxxxxxxxxxx wrote: > Hi, > > in the documentation on the /dts-v1/; identifier I did not find any > explicit reference whether this is meant only for .dts files or also > for to-be-included .dtsi files. From dtc's point of view, that's not really a meaningful question. As in C, dtc includes are a pure textual inclusion, most of dtc, including post of the parser isn't even aware of there being separate files involved. Originally, only a single /dts-v1/ per input was permitted, regardless of however many includes there are. Now - partly as a convenience for handling includes, multiple /dts-v1/ tags are allowed, but they all have to be before anything else, which means a dtsi which is expected to be included other than at the top of a .dts can't include the tags or it will trigger a parse error. > Is there a policy/rule/best-practice how the /dts-v1/ is to be used > when .dtsi files come into play? > > I'm asking because I care for a project where I'd like to propose a > policy for new device submissions, and, depending on your answer, > might also want to harmonize existing DTS(i) files regarding this > aspect. -- David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson
Attachment:
signature.asc
Description: PGP signature
