From: Rob Herring <robh@kernel.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
linux-um@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, kunit-dev@googlegroups.com,
linux-kselftest@vger.kernel.org, devicetree@vger.kernel.org,
Frank Rowand <frowand.list@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v4 5/7] arm64: Unconditionally call unflatten_device_tree()
Date: Thu, 22 Feb 2024 17:03:17 -0700 [thread overview]
Message-ID: <20240223000317.GA3835346-robh@kernel.org> (raw)
In-Reply-To: <20240217010557.2381548-6-sboyd@kernel.org>
On Fri, Feb 16, 2024 at 05:05:54PM -0800, Stephen Boyd wrote:
> Call this function unconditionally so that we can populate an empty DTB
> on platforms that don't boot with a firmware provided or builtin DTB.
> When ACPI is in use, unflatten_device_tree() ignores the
> 'initial_boot_params' pointer so the live DT on those systems won't be
> whatever that's pointing to. Similarly, when kexec copies the DT data
> the previous kernel to the new one on ACPI systems,
> of_kexec_alloc_and_setup_fdt() will ignore the live DT (the empty root
> one) and copy the 'initial_boot_params' data.
>
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Frank Rowand <frowand.list@gmail.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: <linux-arm-kernel@lists.infradead.org>
> Signed-off-by: Stephen Boyd <sboyd@kernel.org>
> ---
> arch/arm64/kernel/setup.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
Catalin, Will, Can I get an ack on this so I can take the series via the
DT tree.
Rob
next prev parent reply other threads:[~2024-02-23 0:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 1:05 [PATCH v4 0/7] of: populate of_root node if bootloader doesn't Stephen Boyd
2024-02-17 1:05 ` [PATCH v4 1/7] of: Always unflatten in unflatten_and_copy_device_tree() Stephen Boyd
2024-02-17 1:05 ` [PATCH v4 2/7] of: Create of_root if no dtb provided by firmware Stephen Boyd
2024-02-17 1:05 ` [PATCH v4 3/7] um: Unconditionally call unflatten_device_tree() Stephen Boyd
2024-02-17 1:05 ` [PATCH v4 4/7] x86/of: Unconditionally call unflatten_and_copy_device_tree() Stephen Boyd
2024-02-17 1:05 ` [PATCH v4 5/7] arm64: Unconditionally call unflatten_device_tree() Stephen Boyd
2024-02-23 0:03 ` Rob Herring [this message]
2024-02-23 10:23 ` Will Deacon
2024-02-23 18:17 ` Rob Herring
2024-02-27 17:34 ` Mark Rutland
2024-02-28 16:26 ` Rob Herring
2024-03-07 15:09 ` Herve Codina
2024-02-27 17:22 ` Oreoluwa Babatunde
2024-02-17 1:05 ` [PATCH v4 6/7] of: unittest: treat missing of_root as error instead of fixing up Stephen Boyd
2024-02-17 1:05 ` [PATCH v4 7/7] of: Add KUnit test to confirm DTB is loaded Stephen Boyd
2024-03-08 19:57 ` [PATCH v4 0/7] of: populate of_root node if bootloader doesn't 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=20240223000317.GA3835346-robh@kernel.org \
--to=robh@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=patches@lists.linux.dev \
--cc=sboyd@kernel.org \
--cc=will@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).