From: Adam Skladowski <a39.skl@gmail.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Bjorn Andersson <andersson@kernel.org>,
Andy Gross <agross@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
AngeloGioacchino Del Regno <kholk11@gmail.com>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/7] clk: qcom: hfpll: Add MSM8976 PLL data
Date: Tue, 25 Jul 2023 12:03:04 +0200 [thread overview]
Message-ID: <80ce1710-38e3-2c6e-73b9-6b18c38b3ff3@gmail.com> (raw)
In-Reply-To: <411da19f-10f3-6dc1-a708-cdf06be9c4d8@linaro.org>
On 25.07.2023 10:02, Konrad Dybcio wrote:
> On 23.07.2023 18:08, Adam Skladowski wrote:
>> Add PLL configuration for MSM8976 SoC, this SoC offers 3 HFPLL.
>> Small cluster offers two presets for 652-902Mhz range and 902Mhz-1.47Ghz.
>> For simplicity only add second range as smaller frequencies can be obtained
>> via apcs divider or safe parent this also saves us
>> a hassle of reconfiguring VCO bit and config_val.
>> A72 and CCI cluster only use single frequency range with their
>> outputs/post_dividers/vco_bits being static.
>>
>> Signed-off-by: Adam Skladowski <a39.skl@gmail.com>
>> ---
> [...]
>
>> +static const struct hfpll_data msm8976_a72 = {
>> + .mode_reg = 0x00,
>> + .l_reg = 0x04,
>> + .m_reg = 0x08,
>> + .n_reg = 0x0c,
>> + .user_reg = 0x10,
>> + .config_reg = 0x14,
>> + .config_val = 0x4e0405d,
>> + .status_reg = 0x1c,
>> + .lock_bit = 16,
>> +
>> + .l_val = 0x3e,
>> + .user_val = 0x100109,
>> + .min_rate = 940800000UL,
>> + .max_rate = 1843200000UL,
> 2016000000?
We are using msm kernel as base not SODP ports.
https://android.googlesource.com/kernel/msm/+/android-lego-6.0.1_r0.2/drivers/clk/qcom/clock-cpu-8976.c
https://android.googlesource.com/kernel/msm.git/+/android-msm-lego-3.10-marshmallow-dr/arch/arm/boot/dts/qcom/msm8976.dtsi#349
> [...]
>> static const struct of_device_id qcom_hfpll_match_table[] = {
>> { .compatible = "qcom,hfpll", &hdata },
>> + { .compatible = "qcom,msm8976-hfpll-a53", &msm8976_a53 },
>> + { .compatible = "qcom,msm8976-hfpll-a72", &msm8976_a72 },
>> + { .compatible = "qcom,msm8976-hfpll-cci", &msm8976_cci },
> .data = is missing
>
> Konrad
Seems like i took "inspiration" from also not great code, albeit it does work somehow when printing inside init, will fix in v3
Thanks Angelo/Konrad
next prev parent reply other threads:[~2023-07-25 10:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 16:08 [PATCH v2 0/7] MSM8976 PLL,RPMPD and DTS changes Adam Skladowski
2023-07-23 16:08 ` [PATCH v2 1/7] drivers: soc: qcom: rpmpd: Fix MSM8976 power domains setup Adam Skladowski
2023-07-24 20:36 ` Dmitry Baryshkov
2023-07-23 16:08 ` [PATCH v2 2/7] clk: qcom: clk-hfpll: Configure l_val in init when required Adam Skladowski
2023-07-24 14:08 ` Konrad Dybcio
2023-07-23 16:08 ` [PATCH v2 3/7] clk: qcom: hfpll: Allow matching pdata Adam Skladowski
2023-07-24 14:08 ` Konrad Dybcio
2023-07-23 16:08 ` [PATCH v2 4/7] dt-bindings: clock: qcom,hfpll: Document MSM8976 compatibles Adam Skladowski
2023-07-24 7:30 ` Krzysztof Kozlowski
2023-07-23 16:08 ` [PATCH v2 5/7] clk: qcom: hfpll: Add MSM8976 PLL data Adam Skladowski
2023-07-25 8:02 ` Konrad Dybcio
2023-07-25 10:03 ` Adam Skladowski [this message]
2023-07-23 16:08 ` [PATCH v2 6/7] arm64: dts: qcom: msm8976: Split lpass region Adam Skladowski
2023-07-25 8:44 ` Konrad Dybcio
2023-07-25 9:46 ` Adam Skladowski
2023-07-23 16:08 ` [PATCH v2 7/7] arm64: dts: qcom: msm8976: Fix smsm ipc bit shifts Adam Skladowski
2023-07-24 20:38 ` [PATCH v2 0/7] MSM8976 PLL,RPMPD and DTS changes Dmitry Baryshkov
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=80ce1710-38e3-2c6e-73b9-6b18c38b3ff3@gmail.com \
--to=a39.skl@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kholk11@gmail.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=mturquette@baylibre.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.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).