linux-kernel - Re: [PATCH 1/2] regulator: core: add support to get VSEL register from hw driver

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] [day] [month] [year] [list]

Message-ID: <20150605165829.GY14071@sirena.org.uk>
Date:	Fri, 5 Jun 2015 17:58:29 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Laxman Dewangan <ldewangan@...dia.com>
Cc:	lgirdwood@...il.com, linux-kernel@...r.kernel.org,
	cfreeman@...dia.com, abrestic@...omium.org, afrid@...dia.com
Subject: Re: [PATCH 1/2] regulator: core: add support to get VSEL register
 from hw driver

On Fri, Jun 05, 2015 at 07:06:35PM +0530, Laxman Dewangan wrote:
> On Friday 29 May 2015 03:19 PM, Mark Brown wrote:
> >The problem will be there when external controller use the DVS pin for DVFS
> >and need two register address here. In this case, I think external
> >controller need to get information from different mechanism rather than via
> >regulator driver to avoid complication on regulator driver/framework.
> >Probably, it's definitely getting complicated (though in this case where
> >we only need one register we ought to be more able to manage it, not
> >that I have bright ideas right now).

> Are you accepting this patch? I am not much clear on the conclusion and
> hence my question is.

> Is anything pending  from me to provide any information?

I thought we agreed that this interface was a bad idea due to the need
to coordinate between the changes in register and the external device
using the value?

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