From: Arnd Bergmann <arnd@arndb.de>
To: Song Xiaowei <songxiaowei@hisilicon.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>, Kishon <kishon@ti.com>,
Jingoo Han <jingoohan1@gmail.com>,
Tomasz Nowicki <tn@semihalf.com>,
Keith Busch <keith.busch@intel.com>,
niklas.cassel@axis.com, Duc Dang <dhdang@apm.com>,
liudongdong3@huawei.com, puck.chen@hisilicon.com,
Guodong Xu <guodong.xu@linaro.org>,
wangbinghui@hisilicon.com, suzhuangluan@hisilicon.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pci <linux-pci@vger.kernel.org>
Subject: Re: [Patch v3 2/3] PCI: dwc: kirin: add PCIe Driver for HiSilicon Kirin SoC
Date: Thu, 18 May 2017 10:41:54 +0200 [thread overview]
Message-ID: <CAK8P3a2cx9t92XKSDn8JCC4Lbq9QcaPt3swgj2mdMw3nXRZk4w@mail.gmail.com> (raw)
In-Reply-To: <20170518074535.20635-1-songxiaowei@hisilicon.com>
On Thu, May 18, 2017 at 9:45 AM, Song Xiaowei <songxiaowei@hisilicon.com> wrote:
> Hisilicon PCIe Driver shares the common functions fo PCIe dw-host
>
> The poweron functions is developed on hi3660 SoC, while Others Functions
> are common for Kirin series SoCs.
>
> Lowpower(L1ss and SR), hotplug and MSI feature are not supported
> currently.
>
> Cc: Guodong Xu <guodong.xu@linaro.org>
> Signed-off-by: Song Xiaowei <songxiaowei@hisilicon.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
prev parent reply other threads:[~2017-05-18 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 7:45 [Patch v3 2/3] PCI: dwc: kirin: add PCIe Driver for HiSilicon Kirin SoC Song Xiaowei
2017-05-18 7:45 ` [Patch v3 3/3] defconfig: PCI: Enable Kirin PCIe defconfig Song Xiaowei
2017-05-18 8:41 ` Arnd Bergmann [this message]
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=CAK8P3a2cx9t92XKSDn8JCC4Lbq9QcaPt3swgj2mdMw3nXRZk4w@mail.gmail.com \
--to=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=dhdang@apm.com \
--cc=guodong.xu@linaro.org \
--cc=jingoohan1@gmail.com \
--cc=keith.busch@intel.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liudongdong3@huawei.com \
--cc=niklas.cassel@axis.com \
--cc=puck.chen@hisilicon.com \
--cc=songxiaowei@hisilicon.com \
--cc=suzhuangluan@hisilicon.com \
--cc=tn@semihalf.com \
--cc=wangbinghui@hisilicon.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).