From: chuanjia.liu <Chuanjia.Liu@mediatek.com>
To: Rob Herring <robh+dt@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: devicetree@vger.kernel.org, Ryder Lee <ryder.lee@mediatek.com>,
chuanjia.liu@mediatek.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, jianjun.wang@mediatek.com,
linux-mediatek@lists.infradead.org, yong.wu@mediatek.com,
Bjorn Helgaas <bhelgaas@google.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/4] Split PCIe node to comply with hardware design
Date: Tue, 21 Jul 2020 15:49:11 +0800 [thread overview]
Message-ID: <20200721074915.14516-1-Chuanjia.Liu@mediatek.com> (raw)
There are two independent PCIe controllers in MT2712 and 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 and MT7622 platform to fix MSI
issue and comply with the hardware design.
change note:
v4:change commit message due to bayes statistical bogofilter
considers this series patch SPAM.
v3:rebase for 5.8-rc1. Only collect ack of Ryder, No code change.
v2:change the allocation of MT2712 PCIe MMIO space due to the
allocation size is not right in v1.
chuanjia.liu (4):
dt-bindings: pci: mediatek: Modified the Device tree bindings
PCI: mediatek: Use regmap to get shared pcie-cfg base
arm64: dts: mediatek: Split PCIe node for MT2712 and MT7622
ARM: dts: mediatek: Modified MT7629 PCIe node
.../bindings/pci/mediatek-pcie-cfg.yaml | 38 +++++
.../devicetree/bindings/pci/mediatek-pcie.txt | 144 +++++++++++-------
arch/arm/boot/dts/mt7629-rfb.dts | 3 +-
arch/arm/boot/dts/mt7629.dtsi | 23 +--
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 75 +++++----
.../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, 258 insertions(+), 140 deletions(-)
create mode 100644 .../bindings/pci/mediatek-pcie-cfg.yaml
--
2.18.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-07-21 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 7:49 chuanjia.liu [this message]
2020-07-21 7:49 ` [PATCH v4 1/4] dt-bindings: pci: mediatek: Modified the Device tree bindings chuanjia.liu
2020-07-21 7:49 ` [PATCH v4 2/4] PCI: mediatek: Use regmap to get shared pcie-cfg base chuanjia.liu
2020-07-21 7:49 ` [PATCH v4 3/4] arm64: dts: mediatek: Split PCIe node for MT2712 and MT7622 chuanjia.liu
2020-07-21 7:49 ` [PATCH v4 4/4] ARM: dts: mediatek: Modified MT7629 PCIe node chuanjia.liu
2020-08-03 7:46 ` [PATCH v4 0/4] Split PCIe node to comply with hardware design Chuanjia Liu
2020-09-08 6:13 ` Aw: " Frank Wunderlich
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=20200721074915.14516-1-Chuanjia.Liu@mediatek.com \
--to=chuanjia.liu@mediatek.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=jianjun.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=yong.wu@mediatek.com \
/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;
as well as URLs for NNTP newsgroup(s).