From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Alexandre Courbot <gnurou@gmail.com>,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: pci: tegra: Update for per-lane PHYs
Date: Thu, 17 Mar 2016 11:26:31 -0500 [thread overview]
Message-ID: <20160317162631.GA6858@rob-hp-laptop> (raw)
In-Reply-To: <1457452094-5409-1-git-send-email-thierry.reding@gmail.com>
On Tue, Mar 08, 2016 at 04:48:13PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Changes to the pad controller device tree binding have required that
> each lane be associated with a separate PHY. Update the PCI host bridge
> device tree binding to allow each root port to define the list of PHYs
> required to drive the lanes associated with it.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../devicetree/bindings/pci/nvidia,tegra20-pcie.txt | 18 +++++++++++++++++-
> 1 file changed, 17 insertions(+), 1 deletion(-)
Acked-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2016-03-17 16:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 15:48 [PATCH 1/2] dt-bindings: pci: tegra: Update for per-lane PHYs Thierry Reding
2016-03-08 15:48 ` [PATCH v3 2/2] PCI: tegra: Support " Thierry Reding
2016-03-11 23:54 ` Bjorn Helgaas
2016-03-16 17:01 ` Stephen Warren
2016-04-13 16:01 ` Thierry Reding
2016-04-13 17:01 ` Stephen Warren
2016-04-14 15:26 ` Thierry Reding
2016-04-05 17:07 ` Bjorn Helgaas
2016-03-16 16:51 ` [PATCH 1/2] dt-bindings: pci: tegra: Update for " Stephen Warren
2016-04-13 16:22 ` Thierry Reding
2016-04-13 17:04 ` Stephen Warren
2016-04-14 15:29 ` Thierry Reding
2016-04-18 14:48 ` Thierry Reding
2016-03-17 16:26 ` Rob Herring [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=20160317162631.GA6858@rob-hp-laptop \
--to=robh@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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