linux-kernel - Re: [patch v1 1/1]regulator: fix for DA9055 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] [day] [month] [year] [list]

Date:	Fri, 28 Jun 2013 18:23:13 +0530
From:	Ankur Raina <Ankur.Raina@...tcummins.com>
To:	Mark Brown <broonie@...nel.org>
CC:	"lgirdwood@...il.com" <lgirdwood@...il.com>,
	"sameo@...ux.intel.com" <sameo@...ux.intel.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"david.chen@...semi.com" <david.chen@...semi.com>
Subject: Re: [patch v1 1/1]regulator: fix for DA9055 regulator

On Fri, 2013-06-28 at 10:33 +0100, Mark Brown wrote:
> On Fri, Jun 28, 2013 at 07:05:03AM +0000, Ankur Raina wrote:
> > This patch adds support for usage of GPIO's by multiple bucks and regulators
> > of DA9055 for enable-disable and voltage set selection.Without this patch regulator
> > control through GPIO would fail for more than one regulator/buck.
> 
> This needs a much better patch description.  What specifically is the
> bug that you are trying to fix here?
The DA9055 hardware supports regulator control through GPIO for all its regulators and bucks.
For this, the contolling GPIO should be set as GPI.The current driver requests gpio for every regulator
that is gpio controlled.This request fails in case of a regulator requesting a gpio, which is already
been assigned to other regulators. The corresponding register update for that regulator also fails.
This patch fixes the above issue.


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