linux-kernel - Re: [PATCH v2 1/2] power: supply: add input voltage limit property.

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]

Date:   Sat, 1 Dec 2018 16:09:34 +0100
From:   Pavel Machek <pavel@....cz>
To:     Enric Balletbo i Serra <enric.balletbo@...labora.com>
Cc:     linux-pm@...r.kernel.org, sre@...nel.org,
        Sameer Nanda <snanda@...omium.org>, gwendal@...omium.org,
        linux-kernel@...r.kernel.org, groeck@...omium.org,
        Adam.Thomson.Opensource@...semi.com, kernel@...labora.com,
        bleung@...omium.org, "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Len Brown <len.brown@...el.com>
Subject: Re: [PATCH v2 1/2] power: supply: add input voltage limit property.

Hi!

> >> We have a problem with USBPD chargers which under certain conditions
> >> can result in system overheating if the voltage provided by the USBPD
> >> port is too high. While the preferred means to control this would be
> >> through devicetree or ACPI settings, this is not always possible, and
> >> we need to have a means to set a voltage limit.
> >>
> >> This patch exposes a new property, similar to input current limit, to
> >> re-configure the maximum voltage from the external supply at runtime
> >> based on system-level knowledge or user input.
> > 
> > First, this should really be handled by dt / ACPI. If it is broken,
> > that's a hardware bug, and we can do DMI-based blacklists in kernel.
> > 
> 
> I think that handle this via dt / ACPI is not possible for our use case. It can
> be a hardware bug or a hardware/user constrain, let me try to explain better
> with an example.
> 
> On Pixel C's devices, userspace uses this to set a USB input limit of 5V when
> the screen is on for thermal reasons, but those go away when the screen is
> off/system is sleeping, so we allow 9V and 12V levels when sleeping.

So, on pixel C, what happens if userland ignores the constraint, keeps
display on and sets charger to 12V?

> > How are you supposed to fsck a system, for example?
> > 
> 
> hmm, I'm not sure I get the question, sorry, could you rephrase?

Ok, so I have just booted with init=/bin/bash, and would like to run
fsck.ext4 on my root filesystem.

> >> +What:		/sys/class/power_supply/<supply_name>/input_voltage_limit
> >> +Date:		Nov 2018
> >> +Contact:	linux-pm@...r.kernel.org
> >> +Description:
> >> +		Details the incoming VBUS voltage limit currently set in the
> >> +		supply. Normally this is configured based on the type of
> >> +		connection made.
> > 
> > "Details"?
> > 
> > Who can write to this value and when? What is the limit? If USB
> > charger is plugged in, should it show 5.0V (because that's nominal on
> > the USB) or 5.25V (because that is the real limit)?
> 
> The voltages here refer to the Typical or Nominal values defined by the USB
> specification for a Fixed power supply (or Fixed PDO). 5.0V, 5.25V, 4.75V,
> 5.5V... all of those are considered "5V" according to the USB specifications.
> 
> At the 5V level (defined in the USB PD specification as vSafe5V), a nominal
> power source is allowed to have a voltage between 4.75V and 5.50V (5V -5%/
> +10%). For simplicity, we refer to this range as 5V, the typical value.
> For all higher voltage levels other than vSafe5V, MIN voltage is PDO Voltage *
> 0.95, and MAX voltage is PDO Voltage * 1.05, where PDO Voltage is the Typical
> value (9V, 12V, 15V, 20V). [1]

> > Who can write to this and when. And what happens on write? What
> > happens if I write value that charger can't provide there?
> > 
> > Does it set the voltage power supply should produce? Or maximal it can
> > choose to produce?
> > 
> 
> This defines a maximal voltage. If you write a value it can't provide,
> it should go down to the next lowest level, and barring that, 5V is
> always allowed.
> 
> That makes me think that maybe I should also improve the implementation.
> 
> > This really needs better documentation.
> 
> Ack, I'll send a next version improving that.

Thanks.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)