mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Renaud Barbier <Renaud.Barbier@ametek.com>
To: Barebox List <barebox@lists.infradead.org>
Subject: PCIE on LS1021A
Date: Fri, 9 Dec 2022 17:31:09 +0000	[thread overview]
Message-ID: <BL0PR07MB5665EA1D980C39F834845849EC1C9@BL0PR07MB5665.namprd07.prod.outlook.com> (raw)


Hello,
We have added support for the LS1021A in barebox (from v2022.03)
At present neither Linux and barebox are able to probe the PCIE device connected to PE1
The board has a switch fabric connected to PCE1.
Using U-boot we are able to see this device and the NXP bridge

Using barebox we see only the Bridge. Then, it fails on the first read to get the header type from the deivice on bus 1.

We know this driver works on the LS1046A as it can detects a PCI card on the LS1046A-RDB.
Both the LS1021A (32-bit cpu) and LS1046 (64-bit cpu) have their PCIE space to access the device conf, I/O and mem space in 64-bit address space

On the LS1046 I do see access at 0x40.xxxx.xxxx while on the LS1021A, it is only a 32-bit access using the lower 32-bit.

As an experiemnt in U-boot, I have disabled the PCI driver and configured the bridge to access the device.
To my surprise I could see the device not using the 40-bit address. So I am not sure it gets mapped (I send a question to NXP)

=> md 0x24000000
24000000: b86114e4 00100000 02000002 00000000  ..a.............


Doint the same operation on barebox, the data are only 
barebox:/ md 0x24000000
24000000: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx                ................
barebox:/ md 0x4024000000
4024000000: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx              ................
4024000010: xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx              ................

>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?

Cheers,
Renaud






             reply	other threads:[~2022-12-09 17:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 17:31 Renaud Barbier [this message]
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

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=BL0PR07MB5665EA1D980C39F834845849EC1C9@BL0PR07MB5665.namprd07.prod.outlook.com \
    --to=renaud.barbier@ametek.com \
    --cc=barebox@lists.infradead.org \
    /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