mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Renaud Barbier <Renaud.Barbier@ametek.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
	Barebox List <barebox@lists.infradead.org>
Cc: Lucas Stach <lst@pengutronix.de>
Subject: RE: PCIE on LS1021A
Date: Tue, 18 Nov 2025 17:42:20 +0000	[thread overview]
Message-ID: <BN8PR07MB69932217E808C9DB9435411FECD6A@BN8PR07MB6993.namprd07.prod.outlook.com> (raw)
In-Reply-To: <874d52d0-f476-53cf-1331-72f80bffacbd@pengutronix.de>

Hello Ahmad,
This has been a while that I asked you about a question on the PCIE for the LS1021A.
We are developing a new product with a NVME device using the LS1021A CPU and
I would like to add LPAE support to barebox so that PCI child devices can be probed.

I am trying to figure out how to assemble LPAE support based on the information you gave me below and what I see in U-boot.

A grep of LPAE in U-boot shows several files with specific code for LPAE:
arch/arm/cpu/armv7/start.S
arch/arm/lib/cache-cp15.c
arch/arm/cpu/armv7/ls102xa/cpu.c

I do  recognize similar pieces of code between barebox and U-boot
From the message below, I understand I would need to update map_io_sections to map the PCI address as in U-boot mmu_setup from the file arch/arm/cpu/armv7/ls102xa/cpu.c

Cheers,
Renaud



> -----Original Message-----
> From: Ahmad Fatoum <a.fatoum@pengutronix.de>
> Sent: 09 December 2022 19:18
> To: Renaud Barbier <Renaud.Barbier@ametek.com>; Barebox List
> <barebox@lists.infradead.org>
> Cc: Lucas Stach <lst@pengutronix.de>
> Subject: Re: PCIE on LS1021A
> 
> ***NOTICE*** This came from an external source. Use caution when
> replying, clicking links, or opening attachments.
> 
> On 09.12.22 19:37, Ahmad Fatoum wrote:
> >> From my debugging I can see that the Layerscape PCIE driver use VA
> >> address = PA address = 0x24000000
> >>
> >> So  Is the problem I am seeing an issue with mapping the correct physical
> address for a 32-bit processor?
> >>
> >> If yes, how can I map the 64-bit PA to a 32-bit VA?
> >
> > Normally, you would call map_io_sections as pci-tegra does, but in
> > your case this alone is insufficient as you will need to implement
> > ARM32 LPAE support first. Once that's in place, you can use
> > map_io_sections and map it to e.g. 0x24000000 as U-Boot does
> arch/arm/cpu/armv7/ls102xa/cpu.c mmu_setup().
> >
> > U-Boot LPAE support was added to support Rpi2, which starts in HYP
> > mode, but we had worked around that in barebox to not require LPAE.
> > For your case however, I don't believe there's a way around using LPAE
> page tables.
> >
> > Tangentially related: I don't know how the PCI controller maintains
> > cache coherency, but if it does write back through CPU caches, you may
> observe memory corruption.
> >
> > It may be the safest for you to disable cache snooping for PCIe until
> > that's resolved (We've this planned, but it will probably not happen this
> year.
> > If you're interested I can elaborate).
> 
> I should have shortened the context a bit. Posting again in case you missed
> it.
> 
> >
> > Cheers,
> > Ahmad
> >
> >
> >
> >>
> >> Cheers,
> >> Renaud
> >>
> >>
> >>
> >>
> >>
> >
> 
> --
> Pengutronix e.K.                           |                             |
> Steuerwalder Str. 21                       |
> https://urldefense.com/v3/__http://www.pengutronix.de/__;!!HKOSU0g!CfA
> u4L9MQvIuEvfQmVymcZYkrdbrn98J2QbYMFsHhqFrxp8fDzjT6-
> h9nSajsgYcNvsCjJVWd98oYvdyj7pvR-ZfDY0$   |
> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


      reply	other threads:[~2025-11-18 17:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 17:31 Renaud Barbier
2022-12-09 18:01 ` Renaud Barbier
2022-12-09 18:37 ` Ahmad Fatoum
2022-12-09 18:58   ` Renaud Barbier
2022-12-09 19:01     ` Ahmad Fatoum
2022-12-13  9:40       ` Renaud Barbier
2022-12-09 19:18   ` Ahmad Fatoum
2025-11-18 17:42     ` Renaud Barbier [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=BN8PR07MB69932217E808C9DB9435411FECD6A@BN8PR07MB6993.namprd07.prod.outlook.com \
    --to=renaud.barbier@ametek.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=lst@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