From: Jianjun Wang <jianjun.wang@mediatek.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Rob Herring <robh+dt@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Ryder Lee <ryder.lee@mediatek.com>
Cc: youlin.pei@mediatek.com, devicetree@vger.kernel.org,
qizhong.cheng@mediatek.com, chuanjia.liu@mediatek.com,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Jianjun Wang <jianjun.wang@mediatek.com>,
sin_jieyang@mediatek.com, Sj Huang <sj.huang@mediatek.com>,
linux-mediatek@lists.infradead.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
davem@davemloft.net, linux-arm-kernel@lists.infradead.org
Subject: [v3,0/3] PCI: mediatek: Add new generation controller support
Date: Sun, 27 Sep 2020 15:45:52 +0800 [thread overview]
Message-ID: <20200927074555.4155-1-jianjun.wang@mediatek.com> (raw)
These series patches add pcie-mediatek-gen3.c and dt-bindings file to
support new generation PCIe controller.
Changes in v3:
1. Remove standard property in binding document
2. Return error number when get_optional* API throws an error
3. Use the bulk clk APIs
Changes in v2:
1. Fix the typo of dt-bindings patch
2. Remove the unnecessary properties in binding document
3. dispos the irq mappings of msi top domain when irq teardown
Jianjun Wang (3):
dt-bindings: PCI: mediatek: Add YAML schema
PCI: mediatek: Add new generation controller support
MAINTAINERS: update entry for MediaTek PCIe controller
.../bindings/pci/mediatek-pcie-gen3.yaml | 126 ++
MAINTAINERS | 1 +
drivers/pci/controller/Kconfig | 14 +
drivers/pci/controller/Makefile | 1 +
drivers/pci/controller/pcie-mediatek-gen3.c | 1024 +++++++++++++++++
5 files changed, 1166 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pci/mediatek-pcie-gen3.yaml
create mode 100644 drivers/pci/controller/pcie-mediatek-gen3.c
--
2.25.1
_______________________________________________
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-09-27 7:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 7:45 Jianjun Wang [this message]
2020-09-27 7:45 ` [v3,1/3] dt-bindings: PCI: mediatek: Add YAML schema Jianjun Wang
2020-09-28 8:16 ` Philipp Zabel
2020-09-28 17:29 ` Rob Herring
2020-09-27 7:45 ` [v3,2/3] PCI: mediatek: Add new generation controller support Jianjun Wang
2020-09-28 8:32 ` Philipp Zabel
2020-11-03 5:44 ` Jianjun Wang
2020-09-27 7:45 ` [v3,3/3] MAINTAINERS: update entry for MediaTek PCIe controller Jianjun Wang
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=20200927074555.4155-1-jianjun.wang@mediatek.com \
--to=jianjun.wang@mediatek.com \
--cc=bhelgaas@google.com \
--cc=chuanjia.liu@mediatek.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--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=matthias.bgg@gmail.com \
--cc=mchehab+huawei@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=qizhong.cheng@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=sin_jieyang@mediatek.com \
--cc=sj.huang@mediatek.com \
--cc=youlin.pei@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).