From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: frowand.list@gmail.com, Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/4] of: remove *phandle properties from expanded device tree
Date: Fri, 16 Jun 2017 10:06:30 +1000 [thread overview]
Message-ID: <1497571590.2897.88.camel@kernel.crashing.org> (raw)
In-Reply-To: <1497073632-22402-1-git-send-email-frowand.list@gmail.com>
On Fri, 2017-06-09 at 22:47 -0700, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@sony.com>
>
> Remove "phandle" and "linux,phandle" properties from the internal
> device tree. The phandle will still be in the struct device_node
> phandle field.
>
> This is to resolve the issue found by Stephen Boyd [1] when he changed
> the type of struct property.value from void * to const void *. As
> a result of the type change, the overlay code had compile errors
> where the resolver updates phandle values.
Piggy back on the powerpc breakage thread...
So various things in userspace will consume these. The main one is
kexec which needs them to rebuild a fdt. So if you're going to do that
you need to modify the sysfs code to expose a phandle attribute from
the device node ->phandle.
Cheers,
Ben.
next prev parent reply other threads:[~2017-06-16 0:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-10 5:47 [PATCH v5 0/4] of: remove *phandle properties from expanded device tree frowand.list
[not found] ` <1497073632-22402-1-git-send-email-frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-06-10 5:47 ` [PATCH v5 1/4] " frowand.list-Re5JQEeQqe8AvxtiuMwx3w
2017-06-15 6:53 ` Michael Ellerman
2017-06-10 5:47 ` [PATCH v5 2/4] of: make __of_attach_node() static frowand.list
2017-06-10 5:47 ` [PATCH v5 3/4] of: be consistent in form of file mode frowand.list
2017-06-10 5:47 ` [PATCH v5 4/4] of: detect invalid phandle in overlay frowand.list
2017-06-13 22:08 ` [PATCH v5 0/4] of: remove *phandle properties from expanded device tree Rob Herring
2017-06-16 0:06 ` Benjamin Herrenschmidt [this message]
[not found] ` <1497571590.2897.88.camel-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2017-06-16 1:31 ` Frank Rowand
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=1497571590.2897.88.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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).