From: "Clément Léger" <clement.leger@bootlin.com>
To: Rob Herring <robh+dt@kernel.org>, Frank Rowand <frowand.list@gmail.com>
Cc: "Clément Léger" <clement.leger@bootlin.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Lizhi Hou" <lizhi.hou@xilinx.com>,
"Allan Nielsen" <allan.nielsen@microchip.com>,
"Horatiu Vultur" <horatiu.vultur@microchip.com>,
"Steen Hegelund" <steen.hegelund@microchip.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: [PATCH v1 0/2] of: populate of_root node if not set
Date: Thu, 23 Jun 2022 12:50:42 +0200 [thread overview]
Message-ID: <20220623105044.152832-1-clement.leger@bootlin.com> (raw)
In order to apply overlays or create new nodes under the root node, the
kernel expects of_root to be set. On some system were a device-tree us
not provided by firmware (x86 for instance) if CONFIG_OF is enabled,
then we will end up with a null of_root. This series add support to
create this root node using a builtin dtb and remove the manual
creation of the root node done in unittests.c.
Clément Léger (2):
of: base: populate of_root node if not set
of: unittest: remove check for of_root
drivers/of/Makefile | 2 +-
drivers/of/base.c | 18 ++++++++++++++++--
drivers/of/empty_root.dts | 6 ++++++
drivers/of/unittest.c | 10 ----------
4 files changed, 23 insertions(+), 13 deletions(-)
create mode 100644 drivers/of/empty_root.dts
--
2.36.1
next reply other threads:[~2022-06-23 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 10:50 Clément Léger [this message]
2022-06-23 10:50 ` [PATCH v1 1/2] of: base: populate of_root node if not set Clément Léger
2022-06-23 23:15 ` Frank Rowand
2022-06-24 1:01 ` Frank Rowand
2022-06-24 3:52 ` Frank Rowand
2022-06-24 12:04 ` Clément Léger
2022-06-23 10:50 ` [PATCH v1 2/2] of: unittest: remove check for of_root Clément Léger
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=20220623105044.152832-1-clement.leger@bootlin.com \
--to=clement.leger@bootlin.com \
--cc=allan.nielsen@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.hou@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=steen.hegelund@microchip.com \
--cc=thomas.petazzoni@bootlin.com \
/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).