devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: phandle via absolute path?
Date: Thu, 16 Jun 2016 11:01:53 +1000	[thread overview]
Message-ID: <20160616010153.GH28087@voom.fritz.box> (raw)
In-Reply-To: <57618E2F.8050900-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

[-- 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 --]

      parent reply	other threads:[~2016-06-16  1:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 17:19 phandle via absolute path? Florian Fainelli
     [not found] ` <57618E2F.8050900-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-06-16  1:01   ` David Gibson [this message]

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=20160616010153.GH28087@voom.fritz.box \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).