From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
Stephen Warren <swarren@nvidia.com>,
"olof@lixom.net" <olof@lixom.net>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ARM: dt: tegra: harmony: add regulators
Date: Mon, 20 Aug 2012 19:14:32 +0100 [thread overview]
Message-ID: <20120820181432.GJ26991@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50327D2D.6000509@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
On Mon, Aug 20, 2012 at 12:08:45PM -0600, Stephen Warren wrote:
> The patch in this thread adds all the required regulators to the DT
> file. However, it should also remove the special case so the
> regulators don't get registered twice, once from the board file and
> once from DT. However, doing that would prevent regulators getting
> registered at all, since v3.6-rc* don't have all the required
> (TPS6586x) regulator (driver) patches to get the regulators
> instantiated from DT. Everything will only work in linux-next or
> sometime during the 3.7 merge window. Hence, git bisect would be broken.
> One solution to this is to bring the regulator tree into the Tegra
> tree as a dependency, and then apply a patch which adds the regulators
> to DT, and removes the special case from the board file. I'm asking
> for your OK to do that.
Why not just pull the patch in via the regulator tree? The idea of
merging the entire regulator drivers branch into the Tegra tree doesn't
seem awesome...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-20 18:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 6:59 [PATCH] ARM: dt: tegra: harmony: add regulators Laxman Dewangan
2012-08-17 19:27 ` Stephen Warren
2012-08-17 19:55 ` Stephen Warren
2012-08-20 17:22 ` Laxman Dewangan
2012-08-20 17:49 ` Stephen Warren
2012-08-20 17:54 ` Mark Brown
2012-08-20 18:08 ` Stephen Warren
2012-08-20 18:14 ` Mark Brown [this message]
2012-08-20 18:37 ` Stephen Warren
2012-08-22 19:07 ` Mark Brown
2012-08-24 18:53 ` 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=20120820181432.GJ26991@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lrg@ti.com \
--cc=olof@lixom.net \
--cc=swarren@nvidia.com \
--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 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).