From: frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
To: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 0/4] of: remove *phandle properties from expanded device tree
Date: Fri, 14 Apr 2017 20:55:16 -0700 [thread overview]
Message-ID: <1492228520-12450-1-git-send-email-frowand.list@gmail.com> (raw)
From: Frank Rowand <frank.rowand-7U/KSKJipcs@public.gmane.org>
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.
[1] http://lkml.iu.edu/hypermail/linux/kernel/1702.1/04160.html
Patch 1 is the phandle related changes.
Patches 2 - 4 are minor fixups for issues that became visible
while implementing patch 1.
Frank Rowand (4):
of: remove *phandle properties from expanded device tree
of: make __of_attach_node() static
of: be consistent in form of file mode
of: detect invalid phandle in overlay
drivers/of/base.c | 53 +++++++++++++++++++++++++++++++++++++++++++++----
drivers/of/dynamic.c | 31 ++++++++++++++++-------------
drivers/of/fdt.c | 40 ++++++++++++++++++++++---------------
drivers/of/of_private.h | 1 -
drivers/of/overlay.c | 8 +++++---
drivers/of/resolver.c | 23 +--------------------
include/linux/of.h | 1 +
7 files changed, 97 insertions(+), 60 deletions(-)
--
Frank Rowand <frank.rowand-7U/KSKJipcs@public.gmane.org>
--
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:[~2017-04-15 3:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 3:55 frowand.list-Re5JQEeQqe8AvxtiuMwx3w [this message]
2017-04-15 3:55 ` [PATCH 2/4] of: make __of_attach_node() static frowand.list
2017-04-15 3:59 ` Frank Rowand
2017-04-15 3:55 ` [PATCH 3/4] of: be consistent in form of file mode frowand.list
2017-04-15 3:59 ` Frank Rowand
2017-04-15 3:55 ` [PATCH 4/4] of: detect invalid phandle in overlay frowand.list
2017-04-15 3:59 ` Frank Rowand
[not found] ` <1492228520-12450-1-git-send-email-frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-04-15 3:55 ` [PATCH 1/4] of: remove *phandle properties from expanded device tree frowand.list-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <1492228520-12450-2-git-send-email-frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-04-15 3:59 ` Frank Rowand
2017-04-15 3:58 ` [PATCH 0/4] " Frank Rowand
[not found] ` <58F19A75.80500-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-04-18 21:08 ` Frank Rowand
[not found] ` <58F6804A.3080206-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-04-19 13:38 ` Rob Herring
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=1492228520-12450-1-git-send-email-frowand.list@gmail.com \
--to=frowand.list-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@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).