From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Roan van Dijk <roan@protonic.nl>, <linux@armlinux.org.uk>
Cc: <mcoquelin.stm32@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-kernel@vger.kernel.org>, David Jander <david@protonic.nl>
Subject: Re: [PATCH] arm: mach-stm32: board-dt.c: Add support for STM32MP151
Date: Tue, 28 Mar 2023 16:43:23 +0200 [thread overview]
Message-ID: <e89aed99-12b6-d1ba-26a5-5e98c4cd6298@foss.st.com> (raw)
In-Reply-To: <20230328093311.1258948-1-roan@protonic.nl>
Hi
On 3/28/23 11:33, Roan van Dijk wrote:
> This patch adds initial support of STM32MP151 microprocessor (MPU)
> based on Arm Cortex-A7. New Cortex-A infrastructure (gic, timer,...)
> are selected if ARCH_MULTI_V7 is defined.
>
> Signed-off-by: David Jander <david@protonic.nl>
> Signed-off-by: Roan van Dijk <roan@protonic.nl>
>
> ---
> arch/arm/mach-stm32/board-dt.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/mach-stm32/board-dt.c b/arch/arm/mach-stm32/board-dt.c
> index 2ccaa11aaa56..5dcc4ddd1a56 100644
> --- a/arch/arm/mach-stm32/board-dt.c
> +++ b/arch/arm/mach-stm32/board-dt.c
> @@ -21,6 +21,7 @@ static const char *const stm32_compat[] __initconst = {
> "st,stm32mp131",
> "st,stm32mp133",
> "st,stm32mp135",
> + "st,stm32mp151",
> "st,stm32mp157",
> NULL
> };
Applied on stm32-next by changing the commit titile (ARM: stm32: ...).
You could send a patch in Documentation/arm/stm32 to highlights main
feature of this SoC or deltas with MP157.
Thanks.
Alex
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-03-28 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 9:33 [PATCH] arm: mach-stm32: board-dt.c: Add support for STM32MP151 Roan van Dijk
2023-03-28 14:43 ` Alexandre TORGUE [this message]
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=e89aed99-12b6-d1ba-26a5-5e98c4cd6298@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=david@protonic.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=roan@protonic.nl \
/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).