[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a2c3eeec-b3ae-466e-b289-991b8658aaf1@oss.qualcomm.com>
Date: Mon, 6 Oct 2025 12:14:57 +0200
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Abhinaba Rakshit <abhinaba.rakshit@....qualcomm.com>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>,
Manivannan Sadhasivam <mani@...nel.org>,
"James E.J. Bottomley" <James.Bottomley@...senPartnership.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>
Cc: linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-scsi@...r.kernel.org
Subject: Re: [PATCH 1/2] soc: qcom: ice: enable ICE clock scaling API
On 10/1/25 1:38 PM, Abhinaba Rakshit wrote:
> Add ICE clock scaling API based on the parsed clk supported
> frequencies from dt entry.
>
> Signed-off-by: Abhinaba Rakshit <abhinaba.rakshit@....qualcomm.com>
> ---
[...]
> + prop = of_get_property(dev->of_node, "freq-table-hz", &len);
> + if (!prop || len < 2 * sizeof(uint32_t)) {
> + dev_err(dev, "Freq-hz property not found or invalid length\n");
> + } else {
> + engine->min_freq = be32_to_cpu(prop[0]);
> + engine->max_freq = be32_to_cpu(prop[1]);
> + }
As I suggested in <fca8355e-9b34-4df1-a7e6-459bdad8b1ff@....qualcomm.com>,
you should really use an OPP table if you want to do any sort of clock
scaling here.
There are then nice APIs associated with that construct that won't make
you pull your hair out..
Konrad
Powered by blists - more mailing lists