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  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:   Tue, 15 Dec 2020 10:21:16 +0100
From:   Krzysztof Kozlowski <>
To:     Guido Günther <>
Cc:     Rob Herring <>, Shawn Guo <>,
        Sascha Hauer <>,
        Pengutronix Kernel Team <>,
        Fabio Estevam <>,
        NXP Linux Team <>,
        Catalin Marinas <>,
        Will Deacon <>,
        Martin Kepplinger <>,
        Angus Ainslie <>,
        Bjorn Andersson <>,
        Li Yang <>,
        Geert Uytterhoeven <>,
        Vinod Koul <>,
        Anson Huang <>,
        Michael Walle <>,,,,
Subject: Re: [PATCH 3/4] arm64: dts: imx8mq-librem5-devkit: Mark more
 regulators as always-on

On Sun, Dec 13, 2020 at 06:17:13PM +0100, Guido Günther wrote:
> They power vital parts of the board and low power consumption is not
> really an issue here. It also brings things more in line with what
> Purism is using downstream.

I don't find it a proper explanation.  Not all regulators power vital
parts of board.  Having regulators always on makes people to skip adding
proper supplies thus not describing the HW properly.

Aligning with downstream without clear reason (just because) is also not
a good reason.

Please reduce the choice only to core regulators or describe it really
why they have to be always on.

Best regards,

Powered by blists - more mailing lists