From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Mark Brown
<broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
Cc: Laxman Dewangan
<ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org"
<olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
"linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org"
<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Liam Girdwood <lrg-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH] ARM: dt: tegra: harmony: add regulators
Date: Mon, 20 Aug 2012 12:08:45 -0600 [thread overview]
Message-ID: <50327D2D.6000509@wwwdotorg.org> (raw)
In-Reply-To: <20120820175410.GI26991-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
On 08/20/2012 11:54 AM, Mark Brown wrote:
> On Mon, Aug 20, 2012 at 11:49:11AM -0600, Stephen Warren wrote:
>
>> The problem there is that will prevent any regulators from being
>> registered at all, until the patch is merged with the regulator
>> tree. That will also prevent PCIe working on Harmony. Those both
>> work right now, so that's a bisection breakage.
>
>> I suppose the solution here is to merge the regulator tree into
>> the Tegra branch before the Harmony regulator patch. Mark, can we
>> do that?
>
> I've no idea what you're talking about here, sorry. What are
> "this" and "the patch"? Surely you can just add whatever DT
> changes you need to add without the thing that uses the bindings?
When booting Harmony using device tree, there's a special case that
registers all the regulators using the remnants of the Harmony board
file. Hence, regulators work right now even without the DT
instantiating them.
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.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
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 12:08:45 -0600 [thread overview]
Message-ID: <50327D2D.6000509@wwwdotorg.org> (raw)
In-Reply-To: <20120820175410.GI26991@opensource.wolfsonmicro.com>
On 08/20/2012 11:54 AM, Mark Brown wrote:
> On Mon, Aug 20, 2012 at 11:49:11AM -0600, Stephen Warren wrote:
>
>> The problem there is that will prevent any regulators from being
>> registered at all, until the patch is merged with the regulator
>> tree. That will also prevent PCIe working on Harmony. Those both
>> work right now, so that's a bisection breakage.
>
>> I suppose the solution here is to merge the regulator tree into
>> the Tegra branch before the Harmony regulator patch. Mark, can we
>> do that?
>
> I've no idea what you're talking about here, sorry. What are
> "this" and "the patch"? Surely you can just add whatever DT
> changes you need to add without the thing that uses the bindings?
When booting Harmony using device tree, there's a special case that
registers all the regulators using the remnants of the Harmony board
file. Hence, regulators work right now even without the DT
instantiating them.
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.
next prev parent reply other threads:[~2012-08-20 18:08 UTC|newest]
Thread overview: 22+ 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 6:59 ` Laxman Dewangan
[not found] ` <1345186799-18229-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-08-17 19:27 ` Stephen Warren
2012-08-17 19:27 ` Stephen Warren
[not found] ` <502E9B09.3080800-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-17 19:55 ` Stephen Warren
2012-08-17 19:55 ` Stephen Warren
[not found] ` <502EA1AC.4090205-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-20 17:22 ` Laxman Dewangan
2012-08-20 17:22 ` Laxman Dewangan
[not found] ` <50327242.80103-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-08-20 17:49 ` Stephen Warren
2012-08-20 17:49 ` Stephen Warren
[not found] ` <50327897.5030601-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-20 17:54 ` Mark Brown
2012-08-20 17:54 ` Mark Brown
[not found] ` <20120820175410.GI26991-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-08-20 18:08 ` Stephen Warren [this message]
2012-08-20 18:08 ` Stephen Warren
[not found] ` <50327D2D.6000509-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-20 18:14 ` Mark Brown
2012-08-20 18:14 ` Mark Brown
[not found] ` <20120820181432.GJ26991-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-08-20 18:37 ` Stephen Warren
2012-08-20 18:37 ` Stephen Warren
[not found] ` <503283F8.4070808-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-22 19:07 ` Mark Brown
2012-08-22 19:07 ` Mark Brown
[not found] ` <20120822190714.GF7995-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-08-24 18:53 ` Stephen Warren
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=50327D2D.6000509@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org \
--cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lrg-l0cyMroinI0@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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.