* [PATCH 0/4] Spilt PCIe node to comply with hardware design
@ 2020-04-17 9:35 chuanjia.liu
0 siblings, 0 replies; only message in thread
From: chuanjia.liu @ 2020-04-17 9:35 UTC (permalink / raw)
To: robh+dt, bhelgaas, matthias.bgg, lorenzo.pieralisi, amurray
Cc: linux-pci, linux-mediatek, devicetree, linux-kernel,
linux-arm-kernel, ryder.lee, chuanjia.liu, jianjun.wang,
srv_heupstream
There are two independent PCIe controllers in MT2712/MT7622 platform,
and each of them should contain an independent MSI domain.
In current architecture, MSI domain will be inherited from the root
bridge, and all of the devices will share the same MSI domain.
Hence that, the PCIe devices will not work properly if the irq number
which required is more than 32.
Split the PCIe node for MT2712/MT7622 platform to fix MSI issue and
comply with the hardware design.
chuanjia.liu (4):
dt-bindings: PCI: Mediatek: Update PCIe binding
PCI: mediatek: Use regmap to get shared pcie-cfg base
arm64: dts: mediatek: Split PCIe node for MT2712/MT7622
ARM: dts: mediatek: Update mt7629 PCIe node
.../bindings/pci/mediatek-pcie-cfg.yaml | 38 ++++++
.../devicetree/bindings/pci/mediatek-pcie.txt | 120 ++++++++++++------
arch/arm/boot/dts/mt7629-rfb.dts | 3 +-
arch/arm/boot/dts/mt7629.dtsi | 23 ++--
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 51 +++++---
.../dts/mediatek/mt7622-bananapi-bpi-r64.dts | 16 +--
arch/arm64/boot/dts/mediatek/mt7622-rfb1.dts | 6 +-
arch/arm64/boot/dts/mediatek/mt7622.dtsi | 68 ++++++----
drivers/pci/controller/pcie-mediatek.c | 25 +++-
9 files changed, 234 insertions(+), 116 deletions(-)
create mode 100644 Documentation/devicetree/bindings/pci/mediatek-pcie-cfg.yaml
--
2.18.0
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-04-17 9:39 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-17 9:35 [PATCH 0/4] Spilt PCIe node to comply with hardware design chuanjia.liu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).