From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pantelis Antoniou Subject: Re: [PATCH 1/2] fdt: Allow stacked overlays phandle references Date: Fri, 14 Jul 2017 10:21:01 +0300 Message-ID: <1500016861.19864.26.camel@hp800z> References: <1497451946-15443-1-git-send-email-pantelis.antoniou@konsulko.com> <1497451946-15443-2-git-send-email-pantelis.antoniou@konsulko.com> <20170703090648.GV13989@umbus.fritz.box> <5967CAA6.6010801@gmail.com> <5967D2F7.60303@gmail.com> <5967E8BC.4090307@gmail.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=konsulko.com; s=google; h=message-id:subject:from:to:cc:date:in-reply-to:references :mime-version:content-transfer-encoding; bh=v8BFaBugjznD9UGzdriOzPIso5ETM3kYL6xC1A3OiN8=; b=l21Tlyx9lGhn+YIswr7tDhG0avAG5xrnTA9dJiJuy03sForhr9KFSCDu6qqY2aGaqB 0jVkEvtWGm2NR7Kuyn2WtgmPi8RzYZtTzA0ZsiIVdXQVkjGY2X+6O3Hphcs+LlalEG1q dmEJjoNvhD0cyameVg1oe4zU425NHgy8umRkk= In-Reply-To: <5967E8BC.4090307-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Sender: devicetree-compiler-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Frank Rowand Cc: Phil Elwell , Nishanth Menon , Rob Herring , Devicetree Compiler , David Gibson , Tom Rini , devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Tero Kristo , Simon Glass Hi Frank, On Thu, 2017-07-13 at 14:40 -0700, Frank Rowand wrote: > On 07/13/17 14:22, Phil Elwell wrote: > > On 13/07/2017 21:07, Frank Rowand wrote: > >> On 07/13/17 12:38, Phil Elwell wrote: > >> [snip] > > hope an inability to solve the problem posed by this advanced usage won't > > prevent a solution to a simpler problem from being accepted. I have waited until people started commenting on this patchset before replying. I think we agree on a few things to keep the discussion moving forward. 1. Stacked overlays are useful and make overlays easier to use. 2. Changing the overlay symbols format now would be unwise. 3. A number of extensions have been put forward/requested. 3.1. There should be a method to place a symbol on a node that didn't have one originally (due to vendor supplying broken DTB or being generated by firmware at runtime). 3.2. Scoping symbol visibility in case of clashes. This can the ability to put multiple path references to a single label/symbol. i.e. foo = "/path/bar", "/path/bar/baz"; Resolving the ambiguity would require the caller to provide it's 'location' on the tree. I.e. a device under /path/bar/baz would resolve to the latter. It is a big change semantically. Do you have anything else? Regards -- Pantelis