linux-kernel - Re: [PATCH v1] clk: Add enable-state column to clk summary

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:   Fri, 13 Nov 2020 00:18:30 -0800
From:   Stephen Boyd <sboyd@...nel.org>
To:     Dmitry Osipenko <digetx@...il.com>,
        Michael Turquette <mturquette@...libre.com>
Cc:     linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] clk: Add enable-state column to clk summary

Quoting Dmitry Osipenko (2020-11-04 08:56:31)
> Add "enable state" column to the clk summary. It's handy to know actual
> hardware state of all clocks for debugging purposes. In conjunction with
> clk_ignore_unused, this tells us what unused clocks are left on after
> bootloader without disabling the clocks.

Should it be called "boot state" then? That idea sounds OK to me.

> It's also s useful debugging

Stray 's' here.

> information for cases where firmware touches clocks.

Care to explain more? Presumably you mean when firmware is modifying clk
state without notifying the kernel? In which case it should be called
"hardware enable" or something like that and be a "Y/N/?" value
depending on if the value can be read or not and if it is enabled or not?

> 
> Signed-off-by: Dmitry Osipenko <digetx@...il.com>