From: Andrey Skvortsov <andrej.skvortzov@gmail.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Jagan Teki <jagan@amarulasolutions.com>,
Hans de Goede <hdegoede@redhat.com>,
u-boot@lists.denx.de, Samuel Holland <samuel@sholland.org>,
Jarrah Gosbell <kernel@undef.tools>
Subject: Re: [PATCH] sunxi: board: provide CPU idle states to loaded OS
Date: Tue, 5 Sep 2023 11:37:31 +0300 [thread overview]
Message-ID: <ZPboy228t8rVajL8@skv.local> (raw)
In-Reply-To: <20230905092712.6ba245bb@donnerap.manchester.arm.com>
Hi Andrey,
On 23-09-05 09:27, Andre Przywara wrote:
> On Mon, 4 Sep 2023 23:54:30 +0300
> Andrey Skvortsov <andrej.skvortzov@gmail.com> wrote:
>
> Hi Andrey,
>
> > When using SCPI as the PSCI backend, firmware can wake up the CPUs and
> > cluster from sleep, so CPU idle states are available for loaded OS to
> > use. TF-A modifies DTB to advertise available CPU idle states, when
> > SCPI is detected. This change copies nodes added by TF-A to any new
> > dtb that is used for loaded OS.
>
> Why do you need that, exactly? Why not just use $fdtcontroladdr for the
> kernel? We now keep the U-Boot copy of the .dts files in sync with the
> kernel. If you need to modify the DT in U-Boot, for instance by applying
> overlays, you can copy that DTB into a better suitable location first:
> => fdt move $fdtcontroladdr $fdt_addr_r
>
> In any case, there shall be only one DT, that one in the U-Boot image. Why
> do you need to load another one for the kernel?
extlinux is used by distributions (sometimes with device-specific changes especially
for platforms not fully supported by mainline yet), then U-Boot loads DT defined in
extlinux.conf file. u-boot scripts are not used in case of extlinux at all.
--
Best regards,
Andrey Skvortsov
next prev parent reply other threads:[~2023-09-05 8:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 20:54 [PATCH] sunxi: board: provide CPU idle states to loaded OS Andrey Skvortsov
2023-09-05 8:27 ` Andre Przywara
2023-09-05 8:37 ` Andrey Skvortsov [this message]
2023-09-06 0:12 ` Andre Przywara
2023-09-06 20:53 ` Andrey Skvortsov
2023-09-11 22:15 ` Andre Przywara
2023-09-14 20:22 ` Andrey Skvortsov
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=ZPboy228t8rVajL8@skv.local \
--to=andrej.skvortzov@gmail.com \
--cc=andre.przywara@arm.com \
--cc=hdegoede@redhat.com \
--cc=jagan@amarulasolutions.com \
--cc=kernel@undef.tools \
--cc=samuel@sholland.org \
--cc=u-boot@lists.denx.de \
/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