[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d3626d96b7fb9e0b1b25159a85d337f8882ceca1.camel@perches.com>
Date: Mon, 04 Nov 2019 10:04:14 -0800
From: Joe Perches <joe@...ches.com>
To: Jeffrey Hugo <jeffrey.l.hugo@...il.com>,
bjorn.andersson@...aro.org, mturquette@...libre.com,
sboyd@...nel.org
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
Subject: Re: [PATCH v5 1/3] clk: qcom: Allow constant ratio freq tables for
rcg
On Thu, 2019-10-31 at 11:57 -0700, Jeffrey Hugo wrote:
> 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.
[]
> diff --git a/drivers/clk/qcom/common.c b/drivers/clk/qcom/common.c
[]
> @@ -29,6 +29,9 @@ struct freq_tbl *qcom_find_freq(const struct freq_tbl *f, unsigned long rate)
> if (!f)
> return NULL;
>
> + if(!f->freq)
> + return f;
> +
trivia:
Space after if before open parenthesis please.
Can you please make sure to style check your
code with checkpatch before submission?
Thanks.
Powered by blists - more mailing lists