From: <Eugen.Hristev@microchip.com>
To: <clement.leger@bootlin.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCH] ARM: mach-at91: fix multiple cpu_reset definition when enabling SYSRESET
Date: Mon, 23 Aug 2021 07:42:58 +0000 [thread overview]
Message-ID: <bbb7bb9b-4b06-97d5-37fc-686135acd2ec@microchip.com> (raw)
In-Reply-To: <20210804145544.1105468-1-clement.leger@bootlin.com>
On 8/4/21 5:55 PM, Clément Léger wrote:
> When SYSRESET is enabled, cpu_reset function is also defined in
> sysreset-uclass.c which lead to multiple definitions of this function
> since reset.c is build unconditionally. Add a check in Makefile to build
> this file only if SYSRESET isn't enabled.
> SYSRESET can be enabled when building SYSRESET_PSCI for instance on this
> platform.
Hello Clement,
Does this mean that in fact, the cpu_reset function from the reset.c
file has to be implemented as a reset driver in the sysreset uclass ?
Eugen
>
> Signed-off-by: Clément Léger <clement.leger@bootlin.com>
> ---
> arch/arm/mach-at91/armv7/Makefile | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-at91/armv7/Makefile b/arch/arm/mach-at91/armv7/Makefile
> index f5b2665957..246050b67b 100644
> --- a/arch/arm/mach-at91/armv7/Makefile
> +++ b/arch/arm/mach-at91/armv7/Makefile
> @@ -11,7 +11,9 @@ obj-$(CONFIG_SAMA5D3) += sama5d3_devices.o clock.o
> obj-$(CONFIG_SAMA5D4) += sama5d4_devices.o clock.o
> obj-$(CONFIG_SAMA7G5) += sama7g5_devices.o
> obj-y += cpu.o
> -obj-y += reset.o
> +ifndef CONFIG_$(SPL_TPL_)SYSRESET
> +obj-y += reset.o
> +endif
> ifneq ($(CONFIG_ATMEL_PIT_TIMER),y)
> ifneq ($(CONFIG_MCHP_PIT64B_TIMER),y)
> # old non-DM timer driver
> --
> 2.32.0
>
next prev parent reply other threads:[~2021-08-23 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 14:55 [PATCH] ARM: mach-at91: fix multiple cpu_reset definition when enabling SYSRESET Clément Léger
2021-08-23 7:42 ` Eugen.Hristev [this message]
2021-08-24 9:37 ` Clément Léger
2021-08-24 9:51 ` Eugen.Hristev
2021-08-25 18:55 ` Clément Léger
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=bbb7bb9b-4b06-97d5-37fc-686135acd2ec@microchip.com \
--to=eugen.hristev@microchip.com \
--cc=clement.leger@bootlin.com \
--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