From: Kathiravan T <quic_kathirav@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>, <agross@kernel.org>,
<andersson@kernel.org>, <mturquette@baylibre.com>,
<sboyd@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <jassisinghbrar@gmail.com>,
<linux-arm-msm@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/6] clk: qcom: apss-ipq-pll: refactor the driver to accommodate different PLL types
Date: Thu, 2 Feb 2023 21:52:48 +0530 [thread overview]
Message-ID: <22fbca02-2f1e-baac-b7c1-9fcba71565d2@quicinc.com> (raw)
In-Reply-To: <1948642d-dab9-4f20-9408-de7c952b9109@linaro.org>
On 2/2/2023 9:26 PM, Konrad Dybcio wrote:
>
> On 2.02.2023 16:37, Kathiravan T wrote:
>> On 2/2/2023 8:45 PM, Konrad Dybcio wrote:
>>> On 2.02.2023 15:52, Kathiravan T wrote:
>>>> APSS PLL found on the IPQ8074 and IPQ6018 are of type Huayra PLL. But,
>>>> IPQ5332 APSS PLL is of type Stromer Plus. To accommodate both these PLLs,
>>>> refactor the driver to take the clk_alpha_pll, alpha_pll_config via device
>>>> data.
>>>>
>>>> Signed-off-by: Kathiravan T <quic_kathirav@quicinc.com>
>>>> ---
>>>> drivers/clk/qcom/apss-ipq-pll.c | 55 +++++++++++++++++++++------------
>>>> 1 file changed, 36 insertions(+), 19 deletions(-)
>>>>
>>>> diff --git a/drivers/clk/qcom/apss-ipq-pll.c b/drivers/clk/qcom/apss-ipq-pll.c
>>>> index a5aea27eb867..6e815e8b7fe4 100644
>>>> --- a/drivers/clk/qcom/apss-ipq-pll.c
>>>> +++ b/drivers/clk/qcom/apss-ipq-pll.c
>>>> @@ -8,20 +8,22 @@
>>>> #include "clk-alpha-pll.h"
>>>> -static const u8 ipq_pll_offsets[] = {
>>>> - [PLL_OFF_L_VAL] = 0x08,
>>>> - [PLL_OFF_ALPHA_VAL] = 0x10,
>>>> - [PLL_OFF_USER_CTL] = 0x18,
>>>> - [PLL_OFF_CONFIG_CTL] = 0x20,
>>>> - [PLL_OFF_CONFIG_CTL_U] = 0x24,
>>>> - [PLL_OFF_STATUS] = 0x28,
>>>> - [PLL_OFF_TEST_CTL] = 0x30,
>>>> - [PLL_OFF_TEST_CTL_U] = 0x34,
>>>> +static const u8 ipq_pll_offsets[][PLL_OFF_MAX_REGS] = {
>>>> + [CLK_ALPHA_PLL_TYPE_HUAYRA] = {
>>> Is it really huayra? The definition in clk-alpha-pll.c is
>>> different..
>>
>> As per the HW document, yes it is Huayra. When you say "different", I understand these offsets are not matching with the one in clk-alpha-pll.c right? I checked with the sub system owner and they said it is expected since these PLLs are specific to each subsystem(A53 and GCC), so the offsets are different.
> Okay, that makes sense. Could you please leave a comment about this
> in the code?
Sure, will do it in V2.
> Konrad
>>
>> Thanks,
>>
>> Kathiravan T.
>>
>>
>>>
>>> Konrad
>>>> + [PLL_OFF_L_VAL] = 0x08,
>>>> + [PLL_OFF_ALPHA_VAL] = 0x10,
>>>> + [PLL_OFF_USER_CTL] = 0x18,
>>>> + [PLL_OFF_CONFIG_CTL] = 0x20,
>>>> + [PLL_OFF_CONFIG_CTL_U] = 0x24,
>>>> + [PLL_OFF_STATUS] = 0x28,
>>>> + [PLL_OFF_TEST_CTL] = 0x30,
>>>> + [PLL_OFF_TEST_CTL_U] = 0x34,
>>>> + },
>>>> };
>>>> -static struct clk_alpha_pll ipq_pll = {
>>>> +static struct clk_alpha_pll ipq_pll_huayra = {
>>>> .offset = 0x0,
>>>> - .regs = ipq_pll_offsets,
>>>> + .regs = ipq_pll_offsets[CLK_ALPHA_PLL_TYPE_HUAYRA],
>>>> .flags = SUPPORTS_DYNAMIC_UPDATE,
>>>> .clkr = {
>>>> .enable_reg = 0x0,
>>>> @@ -61,6 +63,21 @@ static const struct alpha_pll_config ipq8074_pll_config = {
>>>> .test_ctl_hi_val = 0x4000,
>>>> };
>>>> +struct apss_pll_data {
>>>> + struct clk_alpha_pll *pll;
>>>> + const struct alpha_pll_config *pll_config;
>>>> +};
>>>> +
>>>> +static struct apss_pll_data ipq8074_pll_data = {
>>>> + .pll = &ipq_pll_huayra,
>>>> + .pll_config = &ipq8074_pll_config,
>>>> +};
>>>> +
>>>> +static struct apss_pll_data ipq6018_pll_data = {
>>>> + .pll = &ipq_pll_huayra,
>>>> + .pll_config = &ipq6018_pll_config,
>>>> +};
>>>> +
>>>> static const struct regmap_config ipq_pll_regmap_config = {
>>>> .reg_bits = 32,
>>>> .reg_stride = 4,
>>>> @@ -71,7 +88,7 @@ static const struct regmap_config ipq_pll_regmap_config = {
>>>> static int apss_ipq_pll_probe(struct platform_device *pdev)
>>>> {
>>>> - const struct alpha_pll_config *ipq_pll_config;
>>>> + const struct apss_pll_data *data;
>>>> struct device *dev = &pdev->dev;
>>>> struct regmap *regmap;
>>>> void __iomem *base;
>>>> @@ -85,23 +102,23 @@ static int apss_ipq_pll_probe(struct platform_device *pdev)
>>>> if (IS_ERR(regmap))
>>>> return PTR_ERR(regmap);
>>>> - ipq_pll_config = of_device_get_match_data(&pdev->dev);
>>>> - if (!ipq_pll_config)
>>>> + data = of_device_get_match_data(&pdev->dev);
>>>> + if (!data)
>>>> return -ENODEV;
>>>> - clk_alpha_pll_configure(&ipq_pll, regmap, ipq_pll_config);
>>>> + clk_alpha_pll_configure(data->pll, regmap, data->pll_config);
>>>> - ret = devm_clk_register_regmap(dev, &ipq_pll.clkr);
>>>> + ret = devm_clk_register_regmap(dev, &data->pll->clkr);
>>>> if (ret)
>>>> return ret;
>>>> return devm_of_clk_add_hw_provider(dev, of_clk_hw_simple_get,
>>>> - &ipq_pll.clkr.hw);
>>>> + &data->pll->clkr.hw);
>>>> }
>>>> static const struct of_device_id apss_ipq_pll_match_table[] = {
>>>> - { .compatible = "qcom,ipq6018-a53pll", .data = &ipq6018_pll_config },
>>>> - { .compatible = "qcom,ipq8074-a53pll", .data = &ipq8074_pll_config },
>>>> + { .compatible = "qcom,ipq6018-a53pll", .data = &ipq6018_pll_data },
>>>> + { .compatible = "qcom,ipq8074-a53pll", .data = &ipq8074_pll_data },
>>>> { }
>>>> };
>>>> MODULE_DEVICE_TABLE(of, apss_ipq_pll_match_table);
next prev parent reply other threads:[~2023-02-02 16:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 14:52 [PATCH 0/6] Add APSS clock driver support for IPQ5332 Kathiravan T
2023-02-02 14:52 ` [PATCH 1/6] clk: qcom: apss-ipq-pll: refactor the driver to accommodate different PLL types Kathiravan T
2023-02-02 15:15 ` Konrad Dybcio
2023-02-02 15:37 ` Kathiravan T
2023-02-02 15:56 ` Konrad Dybcio
2023-02-02 16:22 ` Kathiravan T [this message]
2023-02-02 14:52 ` [PATCH 2/6] dt-bindings: clock: qcom,a53pll: add IPQ5332 compatible Kathiravan T
2023-02-02 15:28 ` Krzysztof Kozlowski
2023-02-02 14:52 ` [PATCH 3/6] clk: qcom: apss-ipq-pll: add support for IPQ5332 Kathiravan T
2023-02-02 15:18 ` Konrad Dybcio
2023-02-02 15:40 ` Kathiravan T
2023-02-02 14:52 ` [PATCH 4/6] dt-bindings: mailbox: qcom: add compatible for the IPQ5332 SoC Kathiravan T
2023-02-02 15:35 ` Krzysztof Kozlowski
2023-02-02 15:46 ` Kathiravan T
2023-02-02 20:00 ` Dmitry Baryshkov
2023-02-02 20:01 ` Dmitry Baryshkov
2023-02-06 9:12 ` Kathiravan T
2023-02-06 10:39 ` Krzysztof Kozlowski
2023-02-02 14:52 ` [PATCH 5/6] mailbox: qcom-apcs-ipc: add IPQ5332 APSS clock support Kathiravan T
2023-02-02 15:16 ` Konrad Dybcio
2023-02-02 15:30 ` Krzysztof Kozlowski
2023-02-02 15:56 ` Krzysztof Kozlowski
2023-02-02 18:42 ` Konrad Dybcio
2023-02-02 14:52 ` [PATCH 6/6] arm64: dts: qcom: ipq5332: enable the CPUFreq support Kathiravan T
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=22fbca02-2f1e-baac-b7c1-9fcba71565d2@quicinc.com \
--to=quic_kathirav@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@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=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--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).