linux-kernel - Re: [PATCH] arm64: dts: ti: k3-am62-main: Remove power-domains from crypto node

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]

Message-ID: <d030a431-933d-4f54-ba6a-f7bc5a12f843@ti.com>
Date:   Sat, 27 May 2023 12:01:28 +0530
From:   Vignesh Raghavendra <vigneshr@...com>
To:     Francesco Dolcini <francesco@...cini.it>,
        Nishanth Menon <nm@...com>, <kamlesh@...com>
CC:     <kristo@...nel.org>, <robh+dt@...nel.org>,
        <krzysztof.kozlowski+dt@...aro.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62-main: Remove power-domains from
 crypto node



On 25/05/23 8:14 pm, Francesco Dolcini wrote:
> On Mon, Apr 17, 2023 at 08:42:41AM -0500, Nishanth Menon wrote:
>> On 19:03-20230417, kamlesh@...com wrote:
>>> From: Kamlesh Gurudasani <kamlesh@...com>
>>>
>>> With latest firmware update, we can no longer control power of SA3UL from
>>> main domain.
>>
>> How is this backward compatible?
> 
> I just stumbled across this commit since I had an issue with crypto@...00000
> not being probed on Verdin AM62.
> 
> Not sure how this is supposed to work about backward/forward
> compatibility, however this is needed for having it working with the
> latest firmware.
> 

>From what I understand, newer firmware seems to hate SA3UL PD control
requests. But older firmwares just ignored the call as the SA3UL PD is
on by default. So as such, this DT patch alone wont break
forward/backward compatibility.

It looks like newer firmware is broken wrt older kernel which is
unfortunate.

Kamlesh: can you resubmit this patch with appropriate "Fixes" tag so
that it gets backported to stable kernels?

> And if there is a proper way that take care of this, it should be
> backported IMO.
> 
> Francesco
>