From: Bjorn Helgaas <bhelgaas@google.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Thierry Reding <treding@nvidia.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
linux-tegra@vger.kernel.org, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [RFC 0/5] PCI: tegra: Overhaul regulator usage
Date: Fri, 25 Apr 2014 10:57:48 -0600 [thread overview]
Message-ID: <20140425165748.GA32246@google.com> (raw)
In-Reply-To: <53444C4D.2080800@wwwdotorg.org>
On Tue, Apr 08, 2014 at 01:21:49PM -0600, Stephen Warren wrote:
> On 04/04/2014 08:49 AM, Thierry Reding wrote:
> > 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.
>
> I'd be happy to put this series into a branch in the Tegra tree, given
> suitable acks from Bjorn on the PCI changes.
For 3/5 ("PCI: tegra: Implement accurate power supply scheme"),
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
I do have the "PCI: tegra: Use new OF interrupt mapping when possible"
change from Lucas on my pci/host-tegra branch, but it shouldn't conflict
with this.
Bjorn
prev parent reply other threads:[~2014-04-25 16:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 14:49 [RFC 0/5] PCI: tegra: Overhaul regulator usage Thierry Reding
[not found] ` <1396622969-17837-1-git-send-email-treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-04-04 14:49 ` [RFC 1/5] " Thierry Reding
2014-04-08 19:15 ` Stephen Warren
[not found] ` <53444AE3.6030603-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-04-08 19:52 ` Thierry Reding
2014-04-04 14:49 ` [RFC 2/5] ARM: tegra: Add new PCIe regulator properties Thierry Reding
[not found] ` <1396622969-17837-3-git-send-email-treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-04-08 19:17 ` Stephen Warren
2014-04-08 19:54 ` Thierry Reding
2014-04-04 14:49 ` [RFC 4/5] PCI: tegra: Remove deprecated power supply properties Thierry Reding
2014-04-04 14:49 ` [RFC 5/5] ARM: tegra: Remove legacy PCIe " Thierry Reding
2014-04-08 19:21 ` [RFC 0/5] PCI: tegra: Overhaul regulator usage Stephen Warren
2014-04-25 16:57 ` Bjorn Helgaas [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=20140425165748.GA32246@google.com \
--to=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=treding@nvidia.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).