From: Chen Wang <unicorn_wang@outlook.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Chen Wang <unicornxw@gmail.com>,
aou@eecs.berkeley.edu, chao.wei@sophgo.com, conor@kernel.org,
krzysztof.kozlowski+dt@linaro.org, mturquette@baylibre.com,
palmer@dabbelt.com, paul.walmsley@sifive.com,
richardcochran@gmail.com, robh+dt@kernel.org, sboyd@kernel.org,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
haijiao.liu@sophgo.com, xiaoguang.xing@sophgo.com,
guoren@kernel.org, jszhang@kernel.org, inochiama@outlook.com,
samuel.holland@sifive.com
Subject: Re: [PATCH v2 3/4] clk: sophgo: Add SG2042 clock generator driver
Date: Mon, 27 Nov 2023 16:07:12 +0800 [thread overview]
Message-ID: <MA0P287MB03329CFBA3BB6A4E4F322F99FEBDA@MA0P287MB0332.INDP287.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <81d421c8-bfd6-42b5-9da1-f067792f8f48@linaro.org>
On 2023/11/27 15:12, Krzysztof Kozlowski wrote:
> On 27/11/2023 02:15, Chen Wang wrote:
>> From: Chen Wang <unicorn_wang@outlook.com>
>>
>> Add a driver for the SOPHGO SG2042 clock generator.
>>
>> Signed-off-by: Chen Wang <unicorn_wang@outlook.com>
> ...
>
>> +static void __init sg2042_clk_init(struct device_node *node)
>> +{
>> + struct sg2042_clk_data *clk_data = NULL;
>> + int i, ret = 0;
>> + int num_clks = 0;
>> +
>> + num_clks = ARRAY_SIZE(sg2042_pll_clks) +
>> + ARRAY_SIZE(sg2042_div_clks) +
>> + ARRAY_SIZE(sg2042_gate_clks) +
>> + ARRAY_SIZE(sg2042_mux_clks);
>> + if (num_clks == 0) {
>> + ret = -EINVAL;
>> + goto error_out;
>> + }
>> +
>> + ret = sg2042_clk_init_clk_data(node, num_clks, &clk_data);
>> + if (ret < 0)
>> + goto error_out;
>> +
>> + ret = sg2042_clk_register_plls(clk_data, sg2042_pll_clks,
>> + ARRAY_SIZE(sg2042_pll_clks));
>> + if (ret)
>> + goto cleanup;
>> +
>> + ret = sg2042_clk_register_divs(clk_data, sg2042_div_clks,
>> + ARRAY_SIZE(sg2042_div_clks));
>> + if (ret)
>> + goto cleanup;
>> +
>> + ret = sg2042_clk_register_gates(clk_data, sg2042_gate_clks,
>> + ARRAY_SIZE(sg2042_gate_clks));
>> + if (ret)
>> + goto cleanup;
>> +
>> + ret = sg2042_clk_register_muxs(clk_data, sg2042_mux_clks,
>> + ARRAY_SIZE(sg2042_mux_clks));
>> + if (ret)
>> + goto cleanup;
>> +
>> + for (i = 0; i < num_clks; i++)
>> + dbg_info("provider [%d]: %s\n", i, clk_hw_get_name(clk_data->onecell_data.hws[i]));
>> + ret = of_clk_add_hw_provider(node, of_clk_hw_onecell_get, &clk_data->onecell_data);
>> + if (ret)
>> + goto cleanup;
>> +
>> + return;
>> +
>> +cleanup:
>> + for (i = 0; i < num_clks; i++) {
>> + if (clk_data->onecell_data.hws[i] != NULL)
>> + clk_hw_unregister(clk_data->onecell_data.hws[i]);
>> + }
>> + kfree(clk_data);
>> +
>> +error_out:
>> + pr_err("%s failed error number %d\n", __func__, ret);
>> +}
>> +
>> +CLK_OF_DECLARE(sg2042_clk, "sophgo,sg2042-clkgen", sg2042_clk_init);
> No, this should be platform device. It's a child of another device, so
> you cannot use other way of init ordering.
hi, Krzysztof,
Thanks for your review.
I don't quite understand your opinion. Do you mean CLK_OF_DECLARE is
only used for platform device so it can not be use here? But I think
this driver is still for platform device though I move the clock
controller node as a child of the system contoller node. System
controller node is just a block of registers which are used to control
some other platform devices ,such as clock controller, reset controller
and pin controller for this SoC.
And I also see other similar code in kernel, for example:
drivers/clk/clk-k210.c.
And I'm confused by your input "so you cannot use other way of init
ordering." Do you mean "so you CAN use other way of init ordering"?
What's the other way of init ordering do you mean?
Thanks,
Chen
next prev parent reply other threads:[~2023-11-27 8:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 0:57 [PATCH v2 0/4] riscv: sophgo: add clock support for sg2042 Chen Wang
2023-11-27 0:58 ` [PATCH v2 1/4] dt-bindings: clock: sophgo: Add SG2042 bindings Chen Wang
2023-11-27 7:08 ` Krzysztof Kozlowski
2023-11-27 0:58 ` [PATCH v2 2/4] dt-bindings: soc: sophgo: Add Sophgo syscon module Chen Wang
2023-11-27 7:09 ` Krzysztof Kozlowski
2023-11-27 1:15 ` [PATCH v2 3/4] clk: sophgo: Add SG2042 clock generator driver Chen Wang
2023-11-27 7:12 ` Krzysztof Kozlowski
2023-11-27 8:07 ` Chen Wang [this message]
2023-11-27 9:16 ` Krzysztof Kozlowski
2023-11-30 6:37 ` Chen Wang
2023-11-30 8:01 ` Krzysztof Kozlowski
2023-11-30 11:42 ` Chen Wang
2023-11-30 8:12 ` Conor Dooley
2023-11-30 11:32 ` Chen Wang
2023-11-27 1:16 ` [PATCH v2 4/4] riscv: dts: add clock generator for Sophgo SG2042 SoC Chen Wang
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=MA0P287MB03329CFBA3BB6A4E4F322F99FEBDA@MA0P287MB0332.INDP287.PROD.OUTLOOK.COM \
--to=unicorn_wang@outlook.com \
--cc=aou@eecs.berkeley.edu \
--cc=chao.wei@sophgo.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=guoren@kernel.org \
--cc=haijiao.liu@sophgo.com \
--cc=inochiama@outlook.com \
--cc=jszhang@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=sboyd@kernel.org \
--cc=unicornxw@gmail.com \
--cc=xiaoguang.xing@sophgo.com \
/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
all inboxes | Powered by JetHome®