linux-kernel - Re: [PATCH] clk: Add requested rate to clock summary output

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170412164856.GP7065@codeaurora.org>
Date:   Wed, 12 Apr 2017 09:48:56 -0700
From:   Stephen Boyd <sboyd@...eaurora.org>
To:     Peter De Schrijver <pdeschrijver@...dia.com>
Cc:     Michael Turquette <mturquette@...libre.com>,
        linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
        Alex Frid <afrid@...dia.com>
Subject: Re: [PATCH] clk: Add requested rate to clock summary output

On 03/22, Peter De Schrijver wrote:
> From: Alex Frid <afrid@...dia.com>
> 
> Added requested rate to clock summary output and to clock dump. This is
> useful for clock tree debugging. Also expand the clock name field in the
> clock tree debugfs output to provide room for deep multi-tier trees like
> on Tegra.
> 
> Signed-off-by: Alex Frid <afrid@...dia.com>
> Signed-off-by: Peter De Schrijver <pdeschrijver@...dia.com>

We should print out all the consumers (struct clks) and their
requested rates + prepare/enable counts instead. req_rate is sort
of an internal variable that records what the last aggregated
rate was. I'm not sure if we want to expose that to debugfs.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project