linux-kernel - Re: [PATCH] ARM: dt: tegra: harmony: add regulators

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 20 Aug 2012 12:37:44 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	Laxman Dewangan <ldewangan@...dia.com>,
	Stephen Warren <swarren@...dia.com>,
	"olof@...om.net" <olof@...om.net>,
	"linux@....linux.org.uk" <linux@....linux.org.uk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	Liam Girdwood <lrg@...com>
Subject: Re: [PATCH] ARM: dt: tegra: harmony: add regulators

On 08/20/2012 12:14 PM, Mark Brown wrote:
> 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...

I think that'd end up causing some annoying conflicts with other
changes that also touch arch/arm/match-tegra/board-dt-tegra20.c.
Perhaps they're manageable; they probably aren't that bad, but it
seems better to avoid them.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/