linux-kernel - Re: [RFC PATCH 0/2] Propose critical clocks

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: <20221005230609.5BA04C433D6@smtp.kernel.org>
Date:   Wed, 05 Oct 2022 16:06:07 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     Marco Felsch <m.felsch@...gutronix.de>, abel.vesa@...aro.org,
        abelvesa@...nel.org, festevam@...il.com, kernel@...gutronix.de,
        krzysztof.kozlowski+dt@...aro.org, mturquette@...libre.com,
        robh+dt@...nel.org, s.hauer@...gutronix.de, shawnguo@...nel.org
Cc:     Peng Fan <peng.fan@....com>, linux-clk@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-imx@....com, Marek Vasut <marex@...x.de>
Subject: Re: [RFC PATCH 0/2] Propose critical clocks

Quoting Marco Felsch (2022-10-05 01:23:48)
> Hi Stephen, Michael,
> 
> I know it is a busy time right now, but maybe you have a few minutes for
> this RFC. I know it is incomplete, but the interessting part is there
> and it would fix a real issue we encountered on the imx8mm-evk's.
> 

There's another approach by Marek[1]. Can you work together on a
solution? I think we should step away from trying to make the critical
flag work during clk registration, and turn on the clk during provider
registration instead. That hopefully makes it simpler. We can keep the
clk flag of course, so that the clk can't be turned off, but otherwise
we shouldn't need to make registration path check for the property.

[1] https://lore.kernel.org/all/20220924174517.458657-1-marex@denx.de/