mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: Barebox List <barebox@lists.infradead.org>
Subject: RK3568 some question
Date: Fri, 13 Oct 2023 11:12:49 +0300	[thread overview]
Message-ID: <CAP1tNvRpgjbBKxCV94cOHdvFtgwmRz0fRX3B2=-FjYXCY+Z_MA@mail.gmail.com> (raw)

Hello.

I'm trying to run PCI-e 2.0 on an RK3568 processor. The driver loads
OK and does not detect anyone on the bus except itself.
In the kernel, everything works as it should and connected devices are
visible on the bus (in my case, I use Intel AX200 and MediaTek MT7921e
Wi-Fi modules).
Enabling PCI debugging produces these messages:
pbar0 set bad mask
pbar1 set bad mask
Has anyone run PCI on this CPU?

I'm not too familiar with the PCI subsystem, but after briefly looking
at the code,
I saw in the setup_device() function the line:
pci_write_config_dword(dev, pci_base_address_0, 0xfffffffe);
On Linux and u-boot this value is ~0.
The question is, are we doing the right thing here?

And the question is not related to the PCI:
rk3568_lowlevel_init() does not call arm_cpu_lowlevel_init(). Is this OK?

Thanks!



             reply	other threads:[~2023-10-13  8:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13  8:12 Alexander Shiyan [this message]
2023-10-13 10:37 ` Sascha Hauer
2023-10-13 10:53 ` Lucas Stach

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='CAP1tNvRpgjbBKxCV94cOHdvFtgwmRz0fRX3B2=-FjYXCY+Z_MA@mail.gmail.com' \
    --to=eagle.alexander923@gmail.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