From: Stephen Boyd <sboyd@kernel.org>
To: Andy Gross <agross@kernel.org>,
Bartosz Dudziak <bartosz.dudziak@snejp.pl>,
Jeffrey Hugo <jhugo@codeaurora.org>, Luca Weiss <luca@z3ntu.xyz>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Taniya Das <tdas@codeaurora.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Cc: Bartosz Dudziak <bartosz.dudziak@snejp.pl>
Subject: Re: [PATCH v2 2/2] clk: qcom: Add MSM8226 Multimedia Clock Controller support
Date: Thu, 17 Feb 2022 15:22:53 -0800 [thread overview]
Message-ID: <20220217232254.DE517C340E8@smtp.kernel.org> (raw)
In-Reply-To: <20220207185411.19118-3-bartosz.dudziak@snejp.pl>
Quoting Bartosz Dudziak (2022-02-07 10:54:11)
> Modify the existing MSM8974 multimedia clock controller driver to
> support the MMCC found on MSM8226 based devices. This should allow most
> multimedia device drivers to probe and control their clocks.
>
> Signed-off-by: Bartosz Dudziak <bartosz.dudziak@snejp.pl>
> ---
> drivers/clk/qcom/mmcc-msm8974.c | 206 +++++++++++++++++++++++++++++++-
> 1 file changed, 201 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/clk/qcom/mmcc-msm8974.c b/drivers/clk/qcom/mmcc-msm8974.c
> index a1552b6771..f74662925a 100644
> --- a/drivers/clk/qcom/mmcc-msm8974.c
> +++ b/drivers/clk/qcom/mmcc-msm8974.c
> @@ -257,6 +257,18 @@ static struct clk_rcg2 mmss_ahb_clk_src = {
> },
> };
>
> +static struct freq_tbl ftbl_mmss_axi_clk_msm8226[] = {
const?
> + F(19200000, P_XO, 1, 0, 0),
> + F(37500000, P_GPLL0, 16, 0, 0),
> + F(50000000, P_GPLL0, 12, 0, 0),
> + F(75000000, P_GPLL0, 8, 0, 0),
> + F(100000000, P_GPLL0, 6, 0, 0),
> + F(150000000, P_GPLL0, 4, 0, 0),
> + F(200000000, P_MMPLL0, 4, 0, 0),
> + F(266666666, P_MMPLL0, 3, 0, 0),
> + { }
> +};
> +
> static struct freq_tbl ftbl_mmss_axi_clk[] = {
> F( 19200000, P_XO, 1, 0, 0),
> F( 37500000, P_GPLL0, 16, 0, 0),
> @@ -364,6 +376,23 @@ static struct clk_rcg2 csi3_clk_src = {
> },
> };
>
> +static struct freq_tbl ftbl_camss_vfe_vfe0_clk_msm8226[] = {
const?
> + F(37500000, P_GPLL0, 16, 0, 0),
> + F(50000000, P_GPLL0, 12, 0, 0),
> + F(60000000, P_GPLL0, 10, 0, 0),
> + F(80000000, P_GPLL0, 7.5, 0, 0),
> + F(100000000, P_GPLL0, 6, 0, 0),
> + F(109090000, P_GPLL0, 5.5, 0, 0),
> + F(133330000, P_GPLL0, 4.5, 0, 0),
> + F(150000000, P_GPLL0, 4, 0, 0),
> + F(200000000, P_GPLL0, 3, 0, 0),
> + F(228570000, P_MMPLL0, 3.5, 0, 0),
> + F(266670000, P_MMPLL0, 3, 0, 0),
> + F(320000000, P_MMPLL0, 2.5, 0, 0),
> + F(400000000, P_MMPLL0, 2, 0, 0),
> + { }
> +};
> +
> static struct freq_tbl ftbl_camss_vfe_vfe0_1_clk[] = {
> F(37500000, P_GPLL0, 16, 0, 0),
> F(50000000, P_GPLL0, 12, 0, 0),
> @@ -407,6 +436,18 @@ static struct clk_rcg2 vfe1_clk_src = {
> },
> };
>
> +static struct freq_tbl ftbl_mdss_mdp_clk_msm8226[] = {
const?
> + F(37500000, P_GPLL0, 16, 0, 0),
> + F(60000000, P_GPLL0, 10, 0, 0),
> + F(75000000, P_GPLL0, 8, 0, 0),
> + F(92310000, P_GPLL0, 6.5, 0, 0),
> + F(100000000, P_GPLL0, 6, 0, 0),
> + F(133330000, P_MMPLL0, 6, 0, 0),
> + F(177780000, P_MMPLL0, 4.5, 0, 0),
> + F(200000000, P_MMPLL0, 4, 0, 0),
> + { }
> +};
> +
> static struct freq_tbl ftbl_mdss_mdp_clk[] = {
> F(37500000, P_GPLL0, 16, 0, 0),
> F(60000000, P_GPLL0, 10, 0, 0),
> @@ -513,6 +554,14 @@ static struct clk_rcg2 pclk1_clk_src = {
> },
> };
>
> +static struct freq_tbl ftbl_venus0_vcodec0_clk_msm8226[] = {
const?
> + F(66700000, P_GPLL0, 9, 0, 0),
> + F(100000000, P_GPLL0, 6, 0, 0),
> + F(133330000, P_MMPLL0, 6, 0, 0),
> + F(160000000, P_MMPLL0, 5, 0, 0),
> + { }
> +};
> +
> static struct freq_tbl ftbl_venus0_vcodec0_clk[] = {
> F(50000000, P_GPLL0, 12, 0, 0),
> F(100000000, P_GPLL0, 6, 0, 0),
> @@ -593,6 +642,13 @@ static struct clk_rcg2 camss_gp1_clk_src = {
> },
> };
>
> +static struct freq_tbl ftbl_camss_mclk0_3_clk_msm8226[] = {
const?
> + F(19200000, P_XO, 1, 0, 0),
> + F(24000000, P_GPLL0, 5, 1, 5),
> + F(66670000, P_GPLL0, 9, 0, 0),
> + { }
> +};
> +
> static struct freq_tbl ftbl_camss_mclk0_3_clk[] = {
> F(4800000, P_XO, 4, 0, 0),
> F(6000000, P_GPLL0, 10, 1, 10),
> @@ -705,6 +761,15 @@ static struct clk_rcg2 csi2phytimer_clk_src = {
> },
> };
>
> +static struct freq_tbl ftbl_camss_vfe_cpp_clk_msm8226[] = {
const?
> + F(133330000, P_GPLL0, 4.5, 0, 0),
> + F(150000000, P_GPLL0, 4, 0, 0),
> + F(266670000, P_MMPLL0, 3, 0, 0),
> + F(320000000, P_MMPLL0, 2.5, 0, 0),
> + F(400000000, P_MMPLL0, 2, 0, 0),
> + { }
> +};
> +
prev parent reply other threads:[~2022-02-17 23:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 18:54 [PATCH v2 0/2] MSM8226 Multimedia Clock Controller Bartosz Dudziak
2022-02-07 18:54 ` [PATCH v2 1/2] dt-bindings: clock: Add support for the MSM8226 mmcc Bartosz Dudziak
2022-02-11 16:25 ` Rob Herring
2022-02-07 18:54 ` [PATCH v2 2/2] clk: qcom: Add MSM8226 Multimedia Clock Controller support Bartosz Dudziak
2022-02-17 23:22 ` Stephen Boyd [this message]
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=20220217232254.DE517C340E8@smtp.kernel.org \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=bartosz.dudziak@snejp.pl \
--cc=devicetree@vger.kernel.org \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=tdas@codeaurora.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).