From: Marek Vasut <marex@denx.de>
To: Adam Ford <aford173@gmail.com>
Cc: u-boot@lists.denx.de,
Ariel D'Alessandro <ariel.dalessandro@collabora.com>,
"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
"Ying-Chun Liu (PaulLiu)" <paul.liu@linaro.org>,
Andrejs Cainikovs <andrejs.cainikovs@toradex.com>,
Fabio Estevam <festevam@gmail.com>,
Manoj Sai <abbaraju.manojsai@amarulasolutions.com>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
Peng Fan <peng.fan@nxp.com>,
Ricardo Salveti <ricardo@foundries.io>,
Simon Glass <sjg@chromium.org>, Stefano Babic <sbabic@denx.de>,
Tim Harvey <tharvey@gateworks.com>, Ye Li <ye.li@nxp.com>
Subject: Re: [PATCH 10/10] arm: imx: imx8m: Add basic PSCI provider implementation
Date: Tue, 3 Jan 2023 00:58:09 +0100 [thread overview]
Message-ID: <d0bf490a-a489-e7d1-3ecf-5a8bd305776a@denx.de> (raw)
In-Reply-To: <CAHCN7x+Px1TqHUQX9H=WnKQfQQq65+9SPk30GV7jzQgMezkNiA@mail.gmail.com>
On 1/3/23 00:47, Adam Ford wrote:
> On Mon, Jan 2, 2023 at 5:41 PM Marek Vasut <marex@denx.de> wrote:
>>
>> On 1/2/23 17:44, Adam Ford wrote:
>>> On Wed, Dec 21, 2022 at 9:58 PM Marek Vasut <marex@denx.de> wrote:
>>>>
>>>> On 12/22/22 04:05, Adam Ford wrote:
>>>>> On Wed, Dec 21, 2022 at 6:47 PM Marek Vasut <marex@denx.de> wrote:
>>>>>>
>>>>>> Implement basic PSCI provider to let OS turn CPU cores off and on,
>>>>>> power off and restart the system and determine PSCI version. This
>>>>>> is sufficient to remove the need for the ATF BL31 blob altogether.
>>>>>>
>>>>>> To make use of this functionality, active the following Kconfig options:
>>>>>> # CONFIG_PSCI_RESET is not set
>>>>>> CONFIG_ARMV8_MULTIENTRY=y
>>>>>> CONFIG_ARMV8_SET_SMPEN=y
>>>>>> CONFIG_ARMV8_SPL_EXCEPTION_VECTORS=y
>>>>>> CONFIG_ARMV8_EA_EL3_FIRST=y
>>>>>> CONFIG_ARMV8_PSCI=y
>>>>>> CONFIG_ARMV8_PSCI_CPUS_PER_CLUSTER=4
>>>>>> CONFIG_ARMV8_SECURE_BASE=0x970000
>>>>>
>>>>> I am guessing 0x970000 was for the 8MP based on the previous location
>>>>> of ATF. Is that true? If that's the case, can I assume that this
>>>>> address would be 0x910000, 0x920000 and 0x960000 for the imx8mq,
>>>>> imx8mm and imx8mn respectively?
>>>>
>>>> It was for MX8MP, but you can pick whichever address you want, since it
>>>> is U-Boot that installs the SMC handlers, you are no longer forced to
>>>> somehow try and accommodate custom not well fitting load address picked
>>>> by some 3rd party binary blob.
>>>
>>> I patched U-Boot's master with this series and I tried it on
>>> imx8mn_beacon and imx8mm_beacon without success. I never even saw the
>>> SPL message. I tried to focus on the Nano since the boot ROM in that
>>> one is more similar to that of the 8mp, but the behaviour was similar
>>> to that of the Nano. Are there any dependencies or should I have used
>>> a specific starting branch?
>>
>> Nope . But if you don't even see output from SPL, that's where I would
>> start looking. Do you see output from SPL without this series ? Note
>> that bulk of this series content applies to U-Boot proper, not SPL so far.
>
> Without the patch series the generated flash.bin file booted both the
> Mini and the Nano just fine. I have a pending 8m plus that I can also
> try, since that is what you used. I just wanted to make sure I was
> starting from the right place before I went too far with it.
Try and drop
[PATCH 09/10] arm: imx: imx8m: Program CSU and TZASC if PSCI provider
does SPL start then ?
I plan to try this on Nano at some point this month too.
next prev parent reply other threads:[~2023-01-02 23:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 0:46 [PATCH 01/10] arm: psci: Add PSCI v1.1 macro Marek Vasut
2022-12-22 0:46 ` [PATCH 02/10] arm: psci: Fix RESET2 hook Marek Vasut
2023-01-31 16:52 ` sbabic
2022-12-22 0:46 ` [PATCH 03/10] arm: imx: Drop custom lowlevel_init Marek Vasut
2023-01-31 16:52 ` sbabic
2022-12-22 0:46 ` [PATCH 04/10] arm: dts: imx8m: Require ATF BL31 blob only if not PSCI provider Marek Vasut
2023-01-31 16:52 ` sbabic
2022-12-22 0:46 ` [PATCH 05/10] arm: imx: imx8m: Only use ROM pointers " Marek Vasut
2023-01-31 16:52 ` sbabic
2022-12-22 0:46 ` [PATCH 06/10] arm: imx: imx8m: Enable GICv3 support if " Marek Vasut
2023-01-31 16:52 ` sbabic
2022-12-22 0:46 ` [PATCH 07/10] arm: imx: imx8m: Map RAM as NS " Marek Vasut
2023-01-31 16:52 ` sbabic
2022-12-22 0:46 ` [PATCH 08/10] arm: imx: imx8m: Define trampoline location " Marek Vasut
2023-01-31 16:52 ` sbabic
2022-12-22 0:46 ` [PATCH 09/10] arm: imx: imx8m: Program CSU and TZASC " Marek Vasut
2023-01-31 16:53 ` sbabic
2022-12-22 0:46 ` [PATCH 10/10] arm: imx: imx8m: Add basic PSCI provider implementation Marek Vasut
2022-12-22 3:05 ` Adam Ford
2022-12-22 3:58 ` Marek Vasut
2023-01-02 16:44 ` Adam Ford
2023-01-02 23:41 ` Marek Vasut
2023-01-02 23:47 ` Adam Ford
2023-01-02 23:58 ` Marek Vasut [this message]
2023-01-03 1:05 ` Adam Ford
2023-01-03 9:38 ` Marek Vasut
2023-01-31 16:52 ` sbabic
2023-01-31 16:52 ` [PATCH 01/10] arm: psci: Add PSCI v1.1 macro sbabic
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=d0bf490a-a489-e7d1-3ecf-5a8bd305776a@denx.de \
--to=marex@denx.de \
--cc=abbaraju.manojsai@amarulasolutions.com \
--cc=aford173@gmail.com \
--cc=andrejs.cainikovs@toradex.com \
--cc=ariel.dalessandro@collabora.com \
--cc=festevam@gmail.com \
--cc=marcel.ziswiler@toradex.com \
--cc=michael@amarulasolutions.com \
--cc=paul.liu@linaro.org \
--cc=peng.fan@nxp.com \
--cc=ricardo@foundries.io \
--cc=sbabic@denx.de \
--cc=sjg@chromium.org \
--cc=tharvey@gateworks.com \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.com \
--cc=ye.li@nxp.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