From: "Robert P. J. Day" <rpjday-L09J2beyid0N/H6P543EQg@public.gmane.org>
To: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: is there any value in unreferenced <linux,phandle> assignments?
Date: Tue, 24 May 2016 06:49:40 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1605240643210.31752@localhost.localdomain> (raw)
apologies for what i'm sure is a trivial question, but is there any
point in a .dts file having "linux,phandle" assignments that are
unreferenced from anywhere in the final source file?
i ask only because i've been handed a .dts file that admittedly
works just fine, but it contains a number of lines of the form:
linux,phandle = <some-number>;
where none of those numeric phandles are referenced from anywhere else
in the source file (even after processing any .dtsi files).
one possibility is that those are leftovers before someone started
adding labels to nodes, and referring to them like that, but in my
case, the nodes defining those phandles don't even have labels, so
that seems fairly pointless.
is there any other explanation for them? thanks.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-05-24 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 10:49 Robert P. J. Day [this message]
[not found] ` <alpine.LFD.2.20.1605240643210.31752-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2016-05-24 10:57 ` is there any value in unreferenced <linux,phandle> assignments? Mark Rutland
2016-05-24 11:08 ` Robert P. J. Day
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=alpine.LFD.2.20.1605240643210.31752@localhost.localdomain \
--to=rpjday-l09j2beyid0n/h6p543eqg@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@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).