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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20150206005239.GD3218@sonymobile.com>
Date:	Thu, 5 Feb 2015 16:52:40 -0800
From:	Bjorn Andersson <bjorn.andersson@...ymobile.com>
To:	Mark Brown <broonie@...nel.org>
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 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.

Thanks for repeating yourself and sorry about that.

Regards,
Bjorn
--
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/