All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Patrick DELAUNAY <patrick.delaunay@foss.st.com>,
	"Alex G." <mr.nuke.me@gmail.com>,
	u-boot@lists.denx.de
Cc: patrice.chotard@foss.st.com,
	uboot-stm32@st-md-mailman.stormreply.com,
	etienne.carriere@linaro.org
Subject: Re: [PATCH 0/3] stm32mp: Attempt to resolve unintended breakage with v2021.10-rc2
Date: Fri, 8 Oct 2021 13:28:58 +0200	[thread overview]
Message-ID: <89864188-72a4-ecfc-5933-896a46f40b2a@denx.de> (raw)
In-Reply-To: <27a421f4-15f1-f164-a7d3-fe6091436478@foss.st.com>

On 10/8/21 11:18 AM, Patrick DELAUNAY wrote:
> Hi Alex,

Hi,

[...]

>> Without loss of generality, any CONFIG that conflates u-boot options 
>> with SPL options is likely to cause some changes down the line.
>>
> I have a issue today with the generic part of ARM support:
> 
> 1/ the PSCI is mandatory for Linux kernel

PSCI is mandatory only on ARMv8 , NOT on ARMv7.
And the "mandatory" part is forced onto everyone not by Linux kernel, 
but by the architecture specification.

[...]

  reply	other threads:[~2021-10-08 11:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 14:55 [PATCH 0/3] stm32mp: Attempt to resolve unintended breakage with v2021.10-rc2 Alexandru Gagniuc
2021-09-09 14:55 ` [PATCH 1/3] stm32mp: Rename FIP config to stm32mp15_tfaboot_fip_defconig Alexandru Gagniuc
2021-09-09 14:55 ` [PATCH 2/3] arm: Kconfig: Introduce a TFABOOT_FIP_CONTAINER option Alexandru Gagniuc
2021-09-09 14:55 ` [PATCH 3/3] stm32mp1: Replace STM32MP15x_STM32IMAGE with TFABOOT_FIP_CONTAINER Alexandru Gagniuc
2021-09-14 12:26 ` [PATCH 0/3] stm32mp: Attempt to resolve unintended breakage with v2021.10-rc2 Patrick DELAUNAY
2021-10-07 17:13   ` Alex G.
2021-10-08  9:18     ` Patrick DELAUNAY
2021-10-08 11:28       ` Marek Vasut [this message]
2021-10-08 13:20         ` Patrick DELAUNAY

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=89864188-72a4-ecfc-5933-896a46f40b2a@denx.de \
    --to=marex@denx.de \
    --cc=etienne.carriere@linaro.org \
    --cc=mr.nuke.me@gmail.com \
    --cc=patrice.chotard@foss.st.com \
    --cc=patrick.delaunay@foss.st.com \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-stm32@st-md-mailman.stormreply.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.