phandle via absolute path?

phandle via absolute path?

[Florian Fainelli]

Hi,

I can't really see anything that would prevent me to have a phandle
property taking a full-path to a node, but this produces a syntax error.
Let's say we have this:

/dts-v1/;

/ {
	soc@0 {
		somenode@deafbeef {
		};

		someothernode@cafebabe {
			handle = <&/soc@0/somenode@deafbeef>;
		};
	};
};

Does this sound like something that should work?
-- 
Florian

Re: phandle via absolute path?

[David Gibson]

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

On Wed, Jun 15, 2016 at 10:19:43AM -0700, Florian Fainelli wrote:
> Hi,
> 
> I can't really see anything that would prevent me to have a phandle
> property taking a full-path to a node, but this produces a syntax error.
> Let's say we have this:
> 
> /dts-v1/;
> 
> / {
> 	soc@0 {
> 		somenode@deafbeef {
> 		};
> 
> 		someothernode@cafebabe {
> 			handle = <&/soc@0/somenode@deafbeef>;
> 		};
> 	};
> };
> 
> Does this sound like something that should work?

So you can't specify full paths quite like that because it would cause
an ambiguity in the grammar (I forget the details).  You can however
specify a phandle to a full path as:
	handle = <&{/soc@0/somenode@deafbeef}>;

-- 
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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]