From: Shawn Guo <shawn.guo@linaro.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Rob Herring <robh+dt@kernel.org>,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
project-aspen-dev@linaro.org,
Jianguo Sun <sunjianguo1@huawei.com>
Subject: Re: [PATCH] PCI: histb: add power control GPIO for PCIe slot
Date: Fri, 2 Mar 2018 20:36:18 +0800 [thread overview]
Message-ID: <20180302123616.GE28619@dragon> (raw)
In-Reply-To: <20180302120959.GA13205@e107981-ln.cambridge.arm.com>
Hi Lorenzo,
On Fri, Mar 02, 2018 at 12:10:00PM +0000, Lorenzo Pieralisi wrote:
> Hi Shawn,
>
> On Tue, Jan 23, 2018 at 09:04:37AM +0800, Shawn Guo wrote:
> > From: Jianguo Sun <sunjianguo1@huawei.com>
> >
> > Besides the GPIO for controlling reset, there is also possibly another
> > GPIO for turning on/off the power of PCIe slot. Let's add the support
> > for that with another optional device tree property 'power-gpios'.
> >
> > Signed-off-by: Jianguo Sun <sunjianguo1@huawei.com>
> > Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> > ---
> > .../bindings/pci/hisilicon-histb-pcie.txt | 1 +
> > drivers/pci/dwc/pcie-histb.c | 28 +++++++++++++++++++---
>
> Is there a dependency between this patch and this series:
>
> https://patchwork.ozlabs.org/project/linux-pci/list/?series=31410
>
> It does not look like, I'd apply the series but I wanted to ask
> first.
This is the v1 of the same series. Please ignore this one, and only
review the latest v3. Sorry for the confusion.
Shawn
prev parent reply other threads:[~2018-03-02 12:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 1:04 [PATCH] PCI: histb: add power control GPIO for PCIe slot Shawn Guo
2018-01-23 1:12 ` Fabio Estevam
2018-01-23 10:54 ` Shawn Guo
2018-01-23 9:39 ` [project-aspen-dev] " Daniel Thompson
2018-01-23 9:39 ` Daniel Thompson
2018-01-23 10:52 ` Shawn Guo
2018-01-23 10:52 ` Shawn Guo
2018-03-02 12:10 ` Lorenzo Pieralisi
2018-03-02 12:36 ` Shawn Guo [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=20180302123616.GE28619@dragon \
--to=shawn.guo@linaro.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=project-aspen-dev@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sunjianguo1@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.