From: kevans-HZy0K5TPuP5AfugRpC6u6w@public.gmane.org
To: David Gibson
<david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>,
Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v3 0/2] overlays: auto allocate phandles for nodes in base fdt
Date: Wed, 3 Jan 2018 11:12:32 -0600 [thread overview]
Message-ID: <20180103171234.86105-1-kevans@FreeBSD.org> (raw)
Nodes in the base fdt that do not have phandles cannot currently be referenced
in overlays; we can target them for an overlay, but we cannot use them as a
reference in another property if needed. This is quite limiting for some
use-cases where you're needing cross-references that don't currently exist in
the base.
Kyle Evans (2):
fdt_overlay: Allocate phandles as needed for nodes referenced in base
fdt
fdt_overlay: Basic regression tests for automatically allocated
phandles
libfdt/fdt_overlay.c | 64 +++++++++++++++++-----
tests/overlay_base_manual_symbols_auto_phandle.dts | 24 ++++++++
tests/run_tests.sh | 6 ++
3 files changed, 81 insertions(+), 13 deletions(-)
create mode 100644 tests/overlay_base_manual_symbols_auto_phandle.dts
--
2.15.1
next reply other threads:[~2018-01-03 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 17:12 kevans-HZy0K5TPuP5AfugRpC6u6w [this message]
[not found] ` <20180103171234.86105-1-kevans-HZy0K5TPuP5AfugRpC6u6w@public.gmane.org>
2018-01-03 17:12 ` [PATCH v3 1/2] fdt_overlay: Allocate phandles as needed for nodes referenced in base fdt kevans-HZy0K5TPuP5AfugRpC6u6w
2018-01-03 17:12 ` [PATCH v3 2/2] fdt_overlay: Basic regression tests for automatically allocated phandles kevans-HZy0K5TPuP5AfugRpC6u6w
-- strict thread matches above, loose matches on Subject: below --
2018-01-03 17:25 [PATCH v3 0/2] overlays: auto allocate phandles for nodes in base fdt Kyle Evans
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=20180103171234.86105-1-kevans@FreeBSD.org \
--to=kevans-hzy0k5tpup5afugrpc6u6w@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jdl-CYoMK+44s/E@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).