From: <honghui.zhang@mediatek.com>
To: bhelgaas@google.com, robh+dt@kerenl.org, matthias.bgg@gmail.com,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
yingjoe.chen@mediatek.com, eddie.huang@mediatek.com,
ryder.lee@mediatek.com
Cc: honghui.zhang@mediatek.com, hongkun.cao@mediatek.com,
youlin.pei@mediatek.com, yong.wu@mediatek.com,
yt.shen@mediatek.com, sean.wang@mediatek.com,
xinping.qian@mediatek.com
Subject: [PATCH 0/5] PCI: MediaTek: Add support for new generation host controller
Date: Fri, 21 Jul 2017 10:32:42 +0800 [thread overview]
Message-ID: <cover.1500601172.git.honghui.zhang@mediatek.com> (raw)
From: Honghui Zhang <honghui.zhang@mediatek.com>
MediaTek's PCIe host controller has two generation HWs, the new
generation HW has two root ports, it shares most probing flow with the
legacy controller. But the read/write config space logical is different
from the lagacy controller.
This patchset abstract the common probing flow, and add support for the
new generation controller.
Ryder Lee (5):
PCI: mediatek: Add a structure to abstract the controller generations
PCI: mediatek: switch to use platform_get_resource_byname()
dt-bindings: PCI: rename and cleanup MediaTek binding text
PCI: mediatek: Add new generation controller support
dt-bindings: PCI: add support for new generation controller
...{mediatek,mt7623-pcie.txt => mediatek-pcie.txt} | 113 +++-
drivers/pci/host/Kconfig | 5 +-
drivers/pci/host/pcie-mediatek.c | 578 +++++++++++++++++++--
3 files changed, 629 insertions(+), 67 deletions(-)
rename Documentation/devicetree/bindings/pci/{mediatek,mt7623-pcie.txt => mediatek-pcie.txt} (59%)
--
2.6.4
next reply other threads:[~2017-07-21 2:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 2:32 honghui.zhang [this message]
2017-07-21 2:32 ` [PATCH 1/5] PCI: mediatek: Add a structure to abstract the controller generations honghui.zhang
2017-07-21 2:32 ` [PATCH 2/5] PCI: mediatek: switch to use platform_get_resource_byname() honghui.zhang
2017-07-21 2:32 ` [PATCH 3/5] dt-bindings: PCI: rename and cleanup MediaTek binding text honghui.zhang
2017-07-21 2:32 ` [PATCH 4/5] PCI: mediatek: Add new generation controller support honghui.zhang
[not found] ` <416c6158ac6dbb5ef3f55d0a0fe5ba015aee1cd5.1500601172.git.honghui.zhang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-07-23 2:33 ` kbuild test robot
2017-07-21 2:32 ` [PATCH 5/5] dt-bindings: PCI: add support for new generation controller honghui.zhang
[not found] ` <3b449a88bd2f57ee005674d0161192ee01167e5a.1500601172.git.honghui.zhang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-07-24 20:26 ` Rob Herring
2017-07-25 2:09 ` Honghui Zhang
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=cover.1500601172.git.honghui.zhang@mediatek.com \
--to=honghui.zhang@mediatek.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=eddie.huang@mediatek.com \
--cc=hongkun.cao@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=matthias.bgg@gmail.com \
--cc=robh+dt@kerenl.org \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=xinping.qian@mediatek.com \
--cc=yingjoe.chen@mediatek.com \
--cc=yong.wu@mediatek.com \
--cc=youlin.pei@mediatek.com \
--cc=yt.shen@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).