From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] arm: dts: am4372: let boards access all nodes through phandles
Date: Tue, 24 Jun 2014 20:40:16 -0500 [thread overview]
Message-ID: <20140625014016.GA21616@saruman.home> (raw)
In-Reply-To: <CAL_JsqJx_DJqxpEJebi0Etfv5g7=eYje_53vd_44GykreA-rkQ@mail.gmail.com>
Hi,
On Tue, Jun 24, 2014 at 04:11:48PM -0500, Rob Herring wrote:
> On Mon, Jun 23, 2014 at 1:20 PM, Felipe Balbi <balbi@ti.com> wrote:
> > by providing phandles to rtc, wdt, cpu and dispc nodes,
> > boards can access them to add board-specific data.
>
> Strictly speaking, you are adding labels, not phandles. You can do
heh, fair point. Easily editable when applying, though (?)
> phandles without using labels, but the syntax is not so obvious. I'd
> tell you what it is but offhand I don't remember. :)
something along the lines of using the full path ?
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140624/1ea17a10/attachment.sig>
next prev parent reply other threads:[~2014-06-25 1:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 18:20 [PATCH v3 0/2] arm: dts: add support for am437x sk Felipe Balbi
2014-06-23 18:20 ` [PATCH v3 1/2] arm: dts: am4372: let boards access all nodes through phandles Felipe Balbi
2014-06-24 18:39 ` Cooper Jr., Franklin
2014-06-24 20:51 ` Tom Rini
2014-06-24 21:11 ` Rob Herring
2014-06-25 1:40 ` Felipe Balbi [this message]
2014-06-25 11:14 ` Mark Rutland
2014-06-23 18:20 ` [PATCH v3 2/2] arm: dts: add support for AM437x StarterKit Felipe Balbi
2014-06-24 18:36 ` Cooper Jr., Franklin
2014-06-24 20:51 ` Tom Rini
2014-06-25 2:07 ` Darren Etheridge
2014-06-30 16:45 ` [PATCH v3 0/2] arm: dts: add support for am437x sk Felipe Balbi
2014-07-01 12:50 ` Tony Lindgren
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=20140625014016.GA21616@saruman.home \
--to=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).