From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
Renaud Barbier <renaud.barbier@ametek.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/1] Initial ARMv7-A LPAE support
Date: Mon, 23 Feb 2026 12:44:23 +0100 [thread overview]
Message-ID: <74d9ecd8-7c2d-4090-8ff0-7dd16d8b2be1@pengutronix.de> (raw)
In-Reply-To: <aZw8r4SBswMxocvb@pengutronix.de>
Hello Sascha,
On 2/23/26 12:40 PM, Sascha Hauer wrote:
> Hi Renaud,
>
> On Tue, Feb 03, 2026 at 02:19:44PM +0000, Renaud Barbier wrote:
>> The LPAE support allows to map physical address above the 32-bit space in
>> the ARMv7-A processor to a 32-bit virtual address.
>>
>> This patch set was tested on a LS1021A-IOT. Later, a patch to the PCIe
>> designware driver will be provided to prove the remapping of 40-bit PA to
>> 32-bit VA.
>>
>> This patch does not include an update of the mmuinfo command.
>>
>> Renaud Barbier (1):
>> arm: mmu: initial LPAE support
>>
>> arch/arm/Kconfig | 9 +
>> arch/arm/configs/layerscape_v7_defconfig | 1 +
>> arch/arm/cpu/Makefile | 4 +
>> arch/arm/cpu/mmu_lpae.c | 650 ++++++++++++++++++++
>> arch/arm/cpu/mmu_lpae.h | 101 +++
>
> The patch duplicates most of the existing MMU support. Can we do better?
I had asked for it in this form, so I can get a look at how much
duplication there is and how to go from there.
I haven't come around yet to review it though, but I will try to find
the time soon.
Cheers,
Ahmad
>
> Sascha
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2026-02-23 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 14:19 Renaud Barbier
2026-02-03 14:19 ` [PATCH 1/1] arm: mmu: initial " Renaud Barbier
2026-02-23 11:40 ` [PATCH 0/1] Initial ARMv7-A " Sascha Hauer
2026-02-23 11:44 ` Ahmad Fatoum [this message]
2026-02-23 11:52 ` Sascha Hauer
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=74d9ecd8-7c2d-4090-8ff0-7dd16d8b2be1@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=renaud.barbier@ametek.com \
--cc=s.hauer@pengutronix.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