From: Stephen Warren <swarren@wwwdotorg.org>
To: Thierry Reding <thierry.reding@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-tegra@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 0/5] PCI: tegra: Overhaul regulator usage
Date: Mon, 16 Jun 2014 12:30:27 -0600 [thread overview]
Message-ID: <539F37C3.7070600@wwwdotorg.org> (raw)
In-Reply-To: <1401288555-24197-1-git-send-email-thierry.reding@gmail.com>
On 05/28/2014 08:49 AM, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The current device tree binding for the regulator setup on Tegra PCIe is
> not accurate. While it does work for current use-cases, that's likely by
> accident rather than design. This series replaces the existing set of
> power-supply properties with a new set that accurately describes the
> inputs of the IP block (depending on SoC generation).
>
> As a heads-up, this breaks backwards compatibility with prior versions
> of the device tree bindings, but I don't see a reason why that should
> keep us from fixing this properly. Not many people are currently using
> these bindings and those who are are most likely tracking upstream
> development closely enough not to be impacted by this.
>
> I've aimed to keep the series bisectible, which has the downside of
> interleaving patches to unrelated trees (ARM and PCI). I'm hoping that
> perhaps we can find a way to merge this as a whole to keep it possible
> to bisect across the series. Although again, I guess it wouldn't be all
> that bad if that wasn't the case, given how little PCIe is actually
> being used.
>
> This second version of the series has Bjorn's Acked-by for patch 3 from
> the RFC. Stephen, it would be great if you can take this through the
> Tegra tree so that the bisectability can be preserved. I have a bunch of
> other smaller changes for the PCIe driver (mostly cleanups). I don't
> think any of them will conflict, but for extra safety Bjorn may want to
> pull this as a stable branch into his tree.
I've applied this series to Tegra's for-3.17/pcie-regulators branch.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Bjorn Helgaas <bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 0/5] PCI: tegra: Overhaul regulator usage
Date: Mon, 16 Jun 2014 12:30:27 -0600 [thread overview]
Message-ID: <539F37C3.7070600@wwwdotorg.org> (raw)
In-Reply-To: <1401288555-24197-1-git-send-email-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 05/28/2014 08:49 AM, Thierry Reding wrote:
> From: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> The current device tree binding for the regulator setup on Tegra PCIe is
> not accurate. While it does work for current use-cases, that's likely by
> accident rather than design. This series replaces the existing set of
> power-supply properties with a new set that accurately describes the
> inputs of the IP block (depending on SoC generation).
>
> As a heads-up, this breaks backwards compatibility with prior versions
> of the device tree bindings, but I don't see a reason why that should
> keep us from fixing this properly. Not many people are currently using
> these bindings and those who are are most likely tracking upstream
> development closely enough not to be impacted by this.
>
> I've aimed to keep the series bisectible, which has the downside of
> interleaving patches to unrelated trees (ARM and PCI). I'm hoping that
> perhaps we can find a way to merge this as a whole to keep it possible
> to bisect across the series. Although again, I guess it wouldn't be all
> that bad if that wasn't the case, given how little PCIe is actually
> being used.
>
> This second version of the series has Bjorn's Acked-by for patch 3 from
> the RFC. Stephen, it would be great if you can take this through the
> Tegra tree so that the bisectability can be preserved. I have a bunch of
> other smaller changes for the PCIe driver (mostly cleanups). I don't
> think any of them will conflict, but for extra safety Bjorn may want to
> pull this as a stable branch into his tree.
I've applied this series to Tegra's for-3.17/pcie-regulators branch.
next prev parent reply other threads:[~2014-06-16 18:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 14:49 [PATCH v2 0/5] PCI: tegra: Overhaul regulator usage Thierry Reding
2014-05-28 14:49 ` [PATCH v2 1/5] " Thierry Reding
2014-05-28 14:49 ` Thierry Reding
2014-05-29 17:48 ` Stephen Warren
2014-05-29 17:48 ` Stephen Warren
2014-05-28 14:49 ` [PATCH v2 2/5] ARM: tegra: Add new PCIe regulator properties Thierry Reding
2014-05-28 14:49 ` [PATCH v2 3/5] PCI: tegra: Implement accurate power supply scheme Thierry Reding
2014-05-28 14:49 ` [PATCH v2 4/5] PCI: tegra: Remove deprecated power supply properties Thierry Reding
2014-05-28 14:49 ` Thierry Reding
2014-05-28 14:49 ` [PATCH v2 5/5] ARM: tegra: Remove legacy PCIe " Thierry Reding
2014-06-16 18:30 ` Stephen Warren [this message]
2014-06-16 18:30 ` [PATCH v2 0/5] PCI: tegra: Overhaul regulator usage 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=539F37C3.7070600@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.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 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.