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: <53FE2F9E.80501@gmail.com>
Date:	Wed, 27 Aug 2014 21:21:02 +0200
From:	Tomasz Figa <tomasz.figa@...il.com>
To:	Mark Brown <broonie@...nel.org>
CC:	Javier Martinez Canillas <javier.martinez@...labora.co.uk>,
	Doug Anderson <dianders@...omium.org>,
	Olof Johansson <olof@...om.net>,
	Yuvaraj Kumar C D <yuvaraj.cd@...il.com>,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] regulator: max77802: set opmode to normal if off
 is read from hw

On 27.08.2014 21:15, Mark Brown wrote:
> On Wed, Aug 27, 2014 at 08:52:49PM +0200, Tomasz Figa wrote:
>> On 27.08.2014 20:47, Mark Brown wrote:
> 
>>> I'm not convinced that's worth it - chances are that if anything changed
>>> the mode it was a previously running Linux which will most likely be
>>> doing the same things when it starts running anyway.
> 
>> The previously running Linux would have changed the opmode accidentally,
>> due to hardware design of PMIC chip, which doesn't allow powering off a
>> regulator in other way than setting opmode to OFF.
> 
>> If you provide the "active" opmode to that Linux, after a warm reboot it
>> will be able to power on such regulator to correct opmode, without
>> defaulting it incorrectly to NORMAL.
> 
> This is in the scenario where the previously running Linux changed the
> mode to something other than normal and where the freshly booted Linux
> can't figure out how to do that when it needs to.  I'm not sure how
> plausible that scenario is, or that real systems would handle it
> robustly.
> 

I'm not sure I'm getting your point.

If the only thing Linux can do is read back the opmode from PMIC
registers, it doesn't explicitly set it to something other, but rather
reuses what was set by something before it (or, after this patch,
defaults to NORMAL if it's OFF), i.e. the low level firmware or Linux.

However the information about original setting is lost whenever Linux
turns the regulator off and performs a warm reboot, which I believe
would be a quite common scenario.

Best regards,
Tomasz
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ