From: Stephen Boyd <sboyd@kernel.org>
To: Huacai Chen <chenhuacai@kernel.org>,
Jianmin Lv <lvjianmin@loongson.cn>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>, WANG Xuerui <kernel@xen0n.name>,
Yang Li <yang.lee@linux.alibaba.com>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, liupeibao@loongson.cn,
loongarch@lists.linux.dev, wanghongliang@loongson.cn,
zhuyinbo <zhuyinbo@loongson.cn>
Subject: Re: [PATCH v10 2/4] clk: clk-loongson2: add clock controller driver support
Date: Wed, 22 Feb 2023 13:00:50 -0800 [thread overview]
Message-ID: <6c497d2d70d215a86be178fc08546f4d.sboyd@kernel.org> (raw)
In-Reply-To: <834da7dc-bb5d-3427-43e5-938e40a2d180@loongson.cn>
Quoting zhuyinbo (2023-02-21 21:10:14)
>
> >
> >>> yes, the use of dts doesn't require the use of CLK_OF_DECLARE and can
> >>> use platform_driver_register
> >>>
> >>> but my drvier not use platform_driver_register to register clk and use
> >>> CLK_OF_DECLARE to match of_clk_init.
> >> of_clk_init() is there to register clks that are needed for early init,
> >> i.e. the clockevent/clocksource or the root interrupt controller
> >> (irqchip). Otherwise, it isn't necessary to register clks via
> >> of_clk_init().
> > okay, I got it.
>
> and, the time driver get clock by CCF that ask loongson2 clock driver
> use CLK_OF_DECLARE
>
> to match of_clk_init. because the timer_probe is very early and the
> timer driver was use TIMER_OF_DECLARE
>
> to match time_probe.
>
If you have a time driver that gets clks, register those early with
CLK_OF_DECLARE_DRIVER() and then have a platform driver for the rest of
the clk tree that registers clks later.
next prev parent reply other threads:[~2023-02-22 21:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 3:41 [PATCH v10 1/4] dt-bindings: clock: add loongson-2 clock include file Yinbo Zhu
2022-11-29 3:41 ` [PATCH v10 2/4] clk: clk-loongson2: add clock controller driver support Yinbo Zhu
2022-11-30 3:32 ` XiaochuanMao
[not found] ` <dfc61f0b-0051-4146-f534-6436e3076b65@loongson.cn>
2022-11-30 10:16 ` Yinbo Zhu
2022-11-30 13:14 ` XiaochuanMao
2022-11-30 22:49 ` Yinbo Zhu
2022-12-07 2:15 ` Yinbo Zhu
2023-02-01 4:37 ` zhuyinbo
2023-02-10 23:42 ` Stephen Boyd
2023-02-15 7:35 ` zhuyinbo
2023-02-17 22:15 ` Stephen Boyd
2023-02-20 5:44 ` zhuyinbo
2023-02-21 23:07 ` Stephen Boyd
2023-02-22 2:02 ` zhuyinbo
2023-02-22 5:10 ` zhuyinbo
2023-02-22 21:00 ` Stephen Boyd [this message]
2023-02-23 2:16 ` zhuyinbo
2023-02-24 19:10 ` Stephen Boyd
2023-02-27 1:54 ` zhuyinbo
2022-11-29 3:41 ` [PATCH v10 3/4] LoongArch: time: add of_clk_init in time_init Yinbo Zhu
2023-02-10 23:33 ` Stephen Boyd
2022-11-29 3:41 ` [PATCH v10 4/4] dt-bindings: clock: add loongson-2 clock Yinbo Zhu
2023-02-10 23:43 ` Stephen Boyd
2023-02-10 23:42 ` [PATCH v10 1/4] dt-bindings: clock: add loongson-2 clock include file Stephen Boyd
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=6c497d2d70d215a86be178fc08546f4d.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liupeibao@loongson.cn \
--cc=loongarch@lists.linux.dev \
--cc=lvjianmin@loongson.cn \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=wanghongliang@loongson.cn \
--cc=yang.lee@linux.alibaba.com \
--cc=zhuyinbo@loongson.cn \
/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