All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	Alexandre Courbot <gnurou@gmail.com>,
	linux-tegra@vger.kernel.org, linux-pci@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: pci: tegra: Update for per-lane PHYs
Date: Mon, 18 Apr 2016 16:54:29 +0200	[thread overview]
Message-ID: <20160418145429.GD20508@ulmo.ba.sec> (raw)
In-Reply-To: <1460991105-22861-1-git-send-email-thierry.reding@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1771 bytes --]

On Mon, Apr 18, 2016 at 04:51:44PM +0200, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> The XUSB pad controller allows PCIe lanes to be controlled individually,
> providing fine-grained control over their power state. Previous attempts
> at describing the XUSB pad controller in DT had erroneously assumed that
> all PCIe lanes were driven by the same PHY, and hence the PCI host
> controller would reference only a single PHY.
> 
> Moving to a representation of per-lane PHYs requires that the operating
> system driver for the PCI host controller have access to the set of PHY
> devices that make up the connection of each root port in order to power
> up and down all of the lanes as necessary.
> 
> Acked-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> Changes in v5:
> - add per-SoC examples to clarify what properties are relevant on each
>   generation
> - clarify the rationale for moving the per-lane PHYs
> 
> Changes in v4:
> - add additional lanes subnode when dereferencing PHYs from the XUSB pad
>   controller to reflect changes in its binding
> 
>  .../bindings/pci/nvidia,tegra20-pcie.txt           | 224 ++++++++++++++++++++-
>  1 file changed, 219 insertions(+), 5 deletions(-)

Hi Bjorn,

I think I've requested this before, but in case I didn't: once you're
happy with these changes, I'd like to take them through the Tegra tree
to resolve the dependencies with the remainder of a series that involves
the pinctrl and PHY drivers as well as devicetree changes. In order to
do so I'm looking for an Acked-by.

Once applied I can provide a stable branch containing the dependencies
for you to pull into the PCI tree if necessary.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-04-18 14:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 14:51 [PATCH v5 1/2] dt-bindings: pci: tegra: Update for per-lane PHYs Thierry Reding
2016-04-18 14:51 ` [PATCH v5 2/2] PCI: tegra: Support " Thierry Reding
2016-04-18 14:51   ` Thierry Reding
2016-04-28 13:38   ` Thierry Reding
2016-04-28 13:38     ` Thierry Reding
2016-04-28 14:50   ` Bjorn Helgaas
2016-04-28 14:50     ` Bjorn Helgaas
2016-04-28 18:56     ` Bjorn Helgaas
2016-04-28 18:56       ` Bjorn Helgaas
2016-04-18 14:54 ` Thierry Reding [this message]
2016-04-18 16:50 ` [PATCH v5 1/2] dt-bindings: pci: tegra: Update for " Stephen Warren
2016-04-18 16:50   ` Stephen Warren

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=20160418145429.GD20508@ulmo.ba.sec \
    --to=thierry.reding@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gnurou@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@wwwdotorg.org \
    /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.