linux-kernel - Re: [RFC PATCH 3/3] dt: Document: Add optional MAX77686 operating mode 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] [day] [month] [year] [list]

Date:	Wed, 12 Dec 2012 12:07:41 +0900
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Doug Anderson <dianders@...omium.org>
Cc:	Abhilash Kesavan <a.kesavan@...sung.com>, lrg@...com,
	linux-kernel@...r.kernel.org, olof@...om.net,
	grant.likely@...retlab.ca, thomas.abraham@...aro.org,
	kgene.kim@...sung.com, sameo@...ux.intel.com
Subject: Re: [RFC PATCH 3/3] dt: Document: Add optional MAX77686 operating
 mode bindings

On Mon, Dec 10, 2012 at 10:30:42AM -0800, Doug Anderson wrote:

> The max77686 appears to support NORMAL and IDLE mode for most LDOs, so
> the only reasonable values for these two would be 2 and 4.  It appears
> that it would also be nonsensical (impossible to map to a register
> value) to have REGULATOR_MODE_NORMAL for suspend and
> REGULATOR_MODE_IDLE for the normal running mode.

The concept of normal and idle modes is Linux-specific, it's not a
generic hardware property.  You'd want to have something like the
expected current drain, the regulator API does already have support for
mapping into an optimal mode already.
--
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/