linux-kernel - Re: [PATCH] regulator: Support different config and dev of_nodes in regulator

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 6 Feb 2015 11:49:53 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Bjorn Andersson <bjorn.andersson@...ymobile.com>
Cc:	"Bird, Tim" <Tim.Bird@...ymobile.com>,
	"lgirdwood@...il.com" <lgirdwood@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] regulator: Support different config and dev of_nodes in
 regulator_register

On Thu, Feb 05, 2015 at 04:52:40PM -0800, Bjorn Andersson wrote:
> On Thu 05 Feb 16:32 PST 2015, Mark Brown wrote:
> > On Thu, Feb 05, 2015 at 02:08:54PM -0800, Bjorn Andersson wrote:

> > > However this only works for the non-supply regulator properties - and
> > > this is where Tim's patch is trying to sort out.

> > No, this works completely fine for supply properties - to repeat what I
> > said in reply to the original patch the supply is a supply to the chip
> > not to an individual IP on the chip.

> It does make some sense to consider the vbus-supply being connected to
> the block, rather than directly to the vbus-switch. So it would work for
> Tim's use case.

Like I say if we do that then we don't have consistency in how we map a
schematic into a DT binding - you have to dig into the binding of each
device and figure out if the supply is viewed as being for blocks or for
the chip as a whole and we've got the potential for problems in the
binding if we figure out that a supply is actually used by other blocks
later on and don't want to break existing DTs.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)