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

Message-ID: <5571A5E3.3070700@nvidia.com>
Date:	Fri, 5 Jun 2015 19:06:35 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	Mark Brown <broonie@...nel.org>
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 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).
>
Hi Mark,
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 have some more patches pending on MAX8973 for supporting MAX77621 
device and if this series is not fine, I like to go on next set of 
patches while we discussing this need.

Thanks,
Laxman

--
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/