linux-kernel - Re: [PATCH] regulator: s5m8767: Disable OVCB in probe

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:	Thu, 14 Nov 2013 10:29:49 +0900
From:	Kyungmin Park <kmpark@...radead.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	Krzysztof Kozlowski <k.kozlowski@...sung.com>,
	Sangbeom Kim <sbkim73@...sung.com>,
	Liam Girdwood <lgirdwood@...il.com>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	Lee Jones <lee.jones@...aro.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: s5m8767: Disable OVCB in probe

On Wed, Nov 13, 2013 at 10:50 PM, Mark Brown <broonie@...nel.org> wrote:
> On Tue, Nov 12, 2013 at 02:41:55PM +0100, Krzysztof Kozlowski wrote:
>> According to SW Guide the Over-Voltage Clamp may malfunction at VBatt
>> 5.25V and 110'C temperature. This may result in overshooting or
>> undershooting LDO's voltage outputs.
>> Disable the Over-Voltage Clamp in probe by updating proper bit in all
>> LDO registers.
>
> Is there no way to detect these conditions at runtime?  The temperature
> condition in particular seems very high and hence relatively unlikely to
> hold most of the time, disabling the overvoltage protection all the time
> seems like an uncertain tradeoff.

It's hard to do at runtime. right it's rare case. but some condition
(as above) is meet, and no code as workaround. it's mal-function.
that's the guide to avoid this mal-functions.

Thank you,
Kyungmin Park
--
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/