From: Joe Perches <joe@perches.com>
To: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>,
bjorn.andersson@linaro.org, mturquette@baylibre.com,
sboyd@kernel.org
Cc: agross@kernel.org, marc.w.gonzalez@free.fr,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/3] clk: qcom: Allow constant ratio freq tables for rcg
Date: Mon, 04 Nov 2019 10:04:14 -0800 [thread overview]
Message-ID: <d3626d96b7fb9e0b1b25159a85d337f8882ceca1.camel@perches.com> (raw)
In-Reply-To: <20191031185715.15504-1-jeffrey.l.hugo@gmail.com>
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.
next prev parent reply other threads:[~2019-11-04 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 18:55 [PATCH v5 0/3] MSM8998 GPUCC Support Jeffrey Hugo
2019-10-31 18:57 ` [PATCH v5 1/3] clk: qcom: Allow constant ratio freq tables for rcg Jeffrey Hugo
2019-11-04 18:04 ` Joe Perches [this message]
2019-11-07 21:43 ` Stephen Boyd
2019-11-07 22:12 ` Jeffrey Hugo
2019-11-08 6:44 ` Stephen Boyd
2019-10-31 18:57 ` [PATCH v5 2/3] clk: qcom: Add MSM8998 GPU Clock Controller (GPUCC) driver Jeffrey Hugo
2019-11-07 21:44 ` Stephen Boyd
2019-10-31 18:58 ` [PATCH v5 3/3] arm64: dts: qcom: msm8998: Add gpucc node Jeffrey Hugo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d3626d96b7fb9e0b1b25159a85d337f8882ceca1.camel@perches.com \
--to=joe@perches.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=jeffrey.l.hugo@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.w.gonzalez@free.fr \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).