From: Marco Felsch <[email protected]>
To: Johannes Zink <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH master] ARM: i.MX7: enable caches when booted over USB
Date: Tue, 4 Oct 2022 09:54:14 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Hi,
On 22-09-30, Johannes Zink wrote:
> From: Ahmad Fatoum <[email protected]>
>
> BootROM on the i.MX7 doesn't set the SMP bit when booted
> over serial download. This leads to vastly worse performance
> when doing memory-heavy operations in a USB-booted system,
> as the caches are not utilized. Example running md5sum over
> a 25M image in ramfs:
>
> without patch: 10796ms
> with patch: 457ms
>
> This issue isn't unique to the i.MX7, but exists for the i.MX6UL as
> well, which also has the Cortex-A7 as CPU. Like with
> imx6ul_cpu_lowlevel_init(), adapt imx7_cpu_lowlevel_init() to avoid this
> slow down.
>
> Signed-off-by: Ahmad Fatoum <[email protected]>
> Signed-off-by: Johannes Zink <[email protected]>
> ---
> arch/arm/mach-imx/cpu_init.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-imx/cpu_init.c b/arch/arm/mach-imx/cpu_init.c
> index ea36215419..ede2076102 100644
> --- a/arch/arm/mach-imx/cpu_init.c
> +++ b/arch/arm/mach-imx/cpu_init.c
> @@ -49,7 +49,7 @@ void imx6ul_cpu_lowlevel_init(void)
>
> void imx7_cpu_lowlevel_init(void)
> {
> - arm_cpu_lowlevel_init();
> + cortex_a7_lowlevel_init();
Out of curiosity, arm_cpu_lowlevel_init() does a lot more than
cortex_a7_lowlevel_init() e.g. cache invalidation. Is it save to only
call cortex_a7_lowlevel_init() here?
Regards,
Marco
> imx_cpu_timer_init(IOMEM(MX7_SYSCNT_CTRL_BASE_ADDR));
> }
>
> --
> 2.30.2
>
>
>
next prev parent reply other threads:[~2022-10-04 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 13:37 Johannes Zink
2022-10-04 7:54 ` Marco Felsch [this message]
2022-10-10 6:32 ` Ahmad Fatoum
2022-10-10 5:52 ` Sascha Hauer
2022-10-10 6:35 ` Ahmad Fatoum
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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