From: Alexandre Torgue <alexandre.torgue@st.com>
To: Benjamin Gaignard <benjamin.gaignard@linaro.org>,
<linux@armlinux.org.uk>, <mcoquelin.stm32@gmail.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: Re: [PATCH] ARM: mach-stm32: restore reboot capabilities
Date: Mon, 5 Mar 2018 09:41:28 +0100 [thread overview]
Message-ID: <e98c78a4-e5d3-1b90-7ca5-7ab191dc8b43@st.com> (raw)
In-Reply-To: <20180227143607.5583-1-benjamin.gaignard@st.com>
Hi Benjamin
On 02/27/2018 03:36 PM, Benjamin Gaignard wrote:
> To be able to reboot the platform we need to use armv7m_restart for STM32
> SoCs using ARMv7 cores.
>
> Fixes: e0644101bd2f ("ARM: mach-stm32: prepare stm32 family to welcome armv7 architecture)
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> ---
> NOTE: This patch should be applied only on
> git://git.kernel.org/pub/scm/linux/kernel/git/atorgue/stm32.git stm32-next
> until this patch: https://lkml.org/lkml/2018/2/26/386
> find it way to mainline KBuild will complain about it.
>
> arch/arm/mach-stm32/board-dt.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/arm/mach-stm32/board-dt.c b/arch/arm/mach-stm32/board-dt.c
> index 06911ad60cea..011d57b488c2 100644
> --- a/arch/arm/mach-stm32/board-dt.c
> +++ b/arch/arm/mach-stm32/board-dt.c
> @@ -7,6 +7,9 @@
>
> #include <linux/kernel.h>
> #include <asm/mach/arch.h>
> +#ifdef CONFIG_ARM_SINGLE_ARMV7M
> +#include <asm/v7m.h>
> +#endif
>
> static const char *const stm32_compat[] __initconst = {
> "st,stm32f429",
> @@ -20,4 +23,7 @@ static const char *const stm32_compat[] __initconst = {
>
> DT_MACHINE_START(STM32DT, "STM32 (Device Tree Support)")
> .dt_compat = stm32_compat,
> +#ifdef CONFIG_ARM_SINGLE_ARMV7M
> + .restart = armv7m_restart,
> +#endif
> MACHINE_END
Applied on stm32-next.
Thanks.
Alex
prev parent reply other threads:[~2018-03-05 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 14:36 Benjamin Gaignard
2018-03-05 8:41 ` 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=e98c78a4-e5d3-1b90-7ca5-7ab191dc8b43@st.com \
--to=alexandre.torgue@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=benjamin.gaignard@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.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
all inboxes | Powered by JetHome®