From: "Pali Rohár" <pali@kernel.org>
To: Heiko Schocher <hs@denx.de>
Cc: u-boot@lists.denx.de
Subject: [PATCH u-boot 0/3] pci: Do not access Freescale PCI controllers BARs registers
Date: Thu, 20 Apr 2023 21:44:22 +0200 [thread overview]
Message-ID: <20230420194425.25224-1-pali@kernel.org> (raw)
Freescale PCI and PCIe controllers export in config space in BARs offset
for BDF address 00:00.0 internal controller registers, instead of BAR
registers. Avoid access to these registers to prevent overwriting them.
Fixes autoconfiguration of PCI and PCIe devices on Freescale PowerPC
platforms.
Pali Rohár (3):
pci: mpc85xx: Do not access PCI BARs registers of BDF address 00:00.0
pci: fsl: Do not access PCI BAR0 register of PCIe Root Port
pci: auto: Remove PCI_CLASS_PROCESSOR_POWERPC autoconfig case
drivers/pci/pci_auto.c | 4 ----
drivers/pci/pci_mpc85xx.c | 12 ++++++++++++
drivers/pci/pcie_fsl.c | 14 ++++++++++++++
3 files changed, 26 insertions(+), 4 deletions(-)
--
2.20.1
next reply other threads:[~2023-04-20 19:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 19:44 Pali Rohár [this message]
2023-04-20 19:44 ` [PATCH u-boot 1/3] pci: mpc85xx: Do not access PCI BARs registers of BDF address 00:00.0 Pali Rohár
2023-04-21 3:55 ` Heiko Schocher
2023-05-02 16:51 ` Tom Rini
2023-04-20 19:44 ` [PATCH u-boot 2/3] pci: fsl: Do not access PCI BAR0 register of PCIe Root Port Pali Rohár
2023-04-21 3:56 ` Heiko Schocher
2023-05-02 16:51 ` Tom Rini
2023-05-02 17:53 ` [PATCH v2 u-boot] " Pali Rohár
2023-05-04 15:52 ` Tom Rini
2023-04-20 19:44 ` [PATCH u-boot 3/3] pci: auto: Remove PCI_CLASS_PROCESSOR_POWERPC autoconfig case Pali Rohár
2023-04-21 3:56 ` Heiko Schocher
2023-05-02 16:51 ` Tom Rini
2023-04-21 3:54 ` [PATCH u-boot 0/3] pci: Do not access Freescale PCI controllers BARs registers Heiko Schocher
2023-04-29 11:06 ` Pali Rohár
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=20230420194425.25224-1-pali@kernel.org \
--to=pali@kernel.org \
--cc=hs@denx.de \
--cc=u-boot@lists.denx.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