[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7f5e602c-a02c-2a4d-2b00-7cd934a8867e@somainline.org>
Date: Tue, 19 Jul 2022 12:01:53 +0200
From: Konrad Dybcio <konrad.dybcio@...ainline.org>
To: Stephen Boyd <sboyd@...nel.org>,
~postmarketos/upstreaming@...ts.sr.ht
Cc: martin.botka@...ainline.org,
angelogioacchino.delregno@...ainline.org,
marijn.suijten@...ainline.org, jamipkettunen@...ainline.org,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Michael Turquette <mturquette@...libre.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: clock: qcom: rpmcc: Add BIMC_FREQ_LOG
On 19.07.2022 09:13, Stephen Boyd wrote:
> Quoting Konrad Dybcio (2022-07-16 12:27:13)
>> Add the missing definition for the aforementioned clock.
>>
>
> What does the bimc freq log do?
It does not seem used by any driver downstream, not from a quick glance at
least. It is however exposed on the downstream kernel and here's what
debugfs has to say about it on mainline:
clk_accuracy:0
clk_duty_cycle:1/2
clk_enable_count:0
clk_max_rate:18446744073709551615
clk_min_rate:0
clk_notifier_count:0
clk_parent:xo_board
clk_phase:0
clk_prepare_count:0
clk_protect_count:0
clk_rate:1
Konrad
Powered by blists - more mailing lists