linux-kernel - RE: [PATCH 2/2] regulator: add documentation for ACT8945A's regulator DT bindings

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: <B256D81BAE5131468A838E5D7A243641D63F1B1E@penmbx01>
Date:	Mon, 18 Jan 2016 01:31:58 +0000
From:	"Yang, Wenyou" <Wenyou.Yang@...el.com>
To:	Mark Brown <broonie@...nel.org>
CC:	Liam Girdwood <lgirdwood@...il.com>,
	Rob Herring <robh+dt@...nel.org>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	"Ian Campbell" <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	"Ferre, Nicolas" <Nicolas.FERRE@...el.com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: RE: [PATCH 2/2] regulator: add documentation for ACT8945A's
 regulator DT bindings

Hi Mark,

> -----Original Message-----
> From: Mark Brown [mailto:broonie@...nel.org]
> Sent: 2016年1月16日 1:59
> To: Yang, Wenyou <Wenyou.Yang@...el.com>
> Cc: Liam Girdwood <lgirdwood@...il.com>; Rob Herring <robh+dt@...nel.org>;
> Pawel Moll <pawel.moll@....com>; Mark Rutland <mark.rutland@....com>; Ian
> Campbell <ijc+devicetree@...lion.org.uk>; Kumar Gala <galak@...eaurora.org>;
> Ferre, Nicolas <Nicolas.FERRE@...el.com>; linux-arm-
> kernel@...ts.infradead.org; linux-kernel@...r.kernel.org;
> devicetree@...r.kernel.org
> Subject: Re: [PATCH 2/2] regulator: add documentation for ACT8945A's regulator
> DT bindings
> 
> On Fri, Jan 08, 2016 at 10:08:58AM +0800, Wenyou Yang wrote:
> 
> > +Optional properties:
> > +- active-semi,vsel-high: Indicates if the VSEL pin is set to logic-high.
> > +  If this property is missing, assume the VSEL pin is set to logic-low.
> 
> Wouldn't such a pin normally be connected to a GPIO for runtime control
> - why is it expected to be tied statically all the time?

On the reference board, it is connected to the VSYS_5V statically.

Yes, it should be connected to a GPIO, it should be controllable at the necessary time.


Best Regards,
Wenyou Yang