[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191107214352.8A82E2166E@mail.kernel.org>
Date: Thu, 07 Nov 2019 13:43:51 -0800
From: Stephen Boyd <sboyd@...nel.org>
To: Jeffrey Hugo <jeffrey.l.hugo@...il.com>,
bjorn.andersson@...aro.org, mturquette@...libre.com
Cc: agross@...nel.org, marc.w.gonzalez@...e.fr,
linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org,
Jeffrey Hugo <jeffrey.l.hugo@...il.com>
Subject: Re: [PATCH v5 1/3] clk: qcom: Allow constant ratio freq tables for rcg
Quoting Jeffrey Hugo (2019-10-31 11:57:15)
> Some RCGs (the gfx_3d_src_clk in msm8998 for example) are basically just
> some constant ratio from the input across the entire frequency range. It
> would be great if we could specify the frequency table as a single entry
> constant ratio instead of a long list, ie:
>
> { .src = P_GPUPLL0_OUT_EVEN, .pre_div = 3 },
> { }
>
> So, lets support that.
>
> We need to fix a corner case in qcom_find_freq() where if the freq table
> is non-null, but has no frequencies, we end up returning an "entry" before
> the table array, which is bad. Then, we need ignore the freq from the
> table, and instead base everything on the requested freq.
>
> Suggested-by: Stephen Boyd <sboyd@...nel.org>
> Signed-off-by: Jeffrey Hugo <jeffrey.l.hugo@...il.com>
> ---
Applied to clk-next and fixed the space thing. I guess ceil/floor
rounding isn't a problem?
Powered by blists - more mailing lists