linux-kernel - Re: [PATCH v3 1/2] regulator: dt-bindings: pca9450: add PMIC_RST

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: Fri, 10 May 2024 13:03:39 +0200
From: Fabio Aiuto <fabio.aiuto@...icam.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Mark Brown <broonie@...nel.org>, Liam Girdwood <lgirdwood@...il.com>,
	Rob Herring <robh@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	Matteo Lisi <matteo.lisi@...icam.com>,
	Mirko Ardinghi <mirko.ardinghi@...icam.com>
Subject: Re: [PATCH v3 1/2] regulator: dt-bindings: pca9450: add PMIC_RST_B
 warm reset property

Dear Krzysztof,

Il Thu, May 02, 2024 at 09:54:29AM +0200, Krzysztof Kozlowski ha scritto:
> On 15/04/2024 12:59, Fabio Aiuto wrote:
> > Dear Krzysztof,
> > 
> > Il Sat, Apr 13, 2024 at 11:40:18PM +0200, Krzysztof Kozlowski ha scritto:
> >> On 13/04/2024 19:10, Fabio Aiuto wrote:
> >>> Dear Krzysztof,
> >>>
> >>> Il Sat, Apr 13, 2024 at 12:58:35PM +0200, Krzysztof Kozlowski ha scritto:
> >>>> On 12/04/2024 09:21, Fabio Aiuto wrote:
> >>>>> Dear Krzysztof,
> >>>>>
> >>>>> Il Thu, Apr 11, 2024 at 09:52:12PM +0200, Krzysztof Kozlowski ha scritto:
> >>>>>> On 11/04/2024 18:58, Fabio Aiuto wrote:
> > <snip> 
> >> I don't understand what is the use case. You wrote runtime does not
> >> solve your use case. What is the use case?
> > 
> > We experimented problems on some boards with SD card, if a cold reset
> > is done when the card is powered back on it completely freezes, the way
> > devices behave when unpowered for such short intervals is design specific,
> > not an OS policy.
> > 
> 
> Then describe the actual hardware issue, not instruct OS how to behave.
> In the property name and description.

Unfortunately we don't know the details of the hardware issue at the moment.

kr,

fabio

> 
> Best regards,
> Krzysztof
>