From: "Diederik de Haas" <diederik@cknow-tech.com>
To: "Elaine Zhang" <zhangqing@rock-chips.com>,
<mturquette@baylibre.com>, <sboyd@kernel.org>,
<sugar.zhang@rock-chips.com>, <heiko@sntech.de>,
<robh@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-clk@vger.kernel.org>, <linux-rockchip@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <huangtao@rock-chips.com>
Subject: Re: [PATCH v3 4/5] dt-bindings: clock: Add support for rockchip pvtpll
Date: Mon, 20 Oct 2025 11:38:02 +0200 [thread overview]
Message-ID: <DDN1RQB4LG0X.30F0A3IMJ4YI4@cknow-tech.com> (raw)
In-Reply-To: <20251020023724.2723372-5-zhangqing@rock-chips.com>
On Mon Oct 20, 2025 at 4:37 AM CEST, Elaine Zhang wrote:
> Add pvtpll documentation for rockchip.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> ---
> .../bindings/clock/rockchip,clk-pvtpll.yaml | 100 ++++++++++++++++++
> 1 file changed, 100 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/clock/rockchip,clk-pvtpll.yaml
>
> diff --git a/Documentation/devicetree/bindings/clock/rockchip,clk-pvtpll.yaml b/Documentation/devicetree/bindings/clock/rockchip,clk-pvtpll.yaml
> new file mode 100644
Should this file have the 'clk-' part in its name?
In a way this is different from the other DT binding files, but none of
the others have the 'clk-' part in their file name:
me@pc:~/linux/Documentation/devicetree/bindings/clock$ ls -lh rockchip,*
-rw-rw-r-- 1 me me 2,9K okt 20 11:32 rockchip,px30-cru.yaml
-rw-rw-r-- 1 me me 1,9K okt 20 11:32 rockchip,rk3036-cru.yaml
-rw-rw-r-- 1 me me 1,8K okt 20 11:32 rockchip,rk3128-cru.yaml
-rw-rw-r-- 1 me me 2,3K okt 20 11:32 rockchip,rk3188-cru.yaml
-rw-rw-r-- 1 me me 2,1K okt 20 11:32 rockchip,rk3228-cru.yaml
-rw-rw-r-- 1 me me 2,6K okt 20 11:32 rockchip,rk3288-cru.yaml
-rw-rw-r-- 1 me me 2,2K okt 20 11:32 rockchip,rk3308-cru.yaml
-rw-rw-r-- 1 me me 2,1K okt 20 11:32 rockchip,rk3328-cru.yaml
-rw-rw-r-- 1 me me 2,4K okt 20 11:32 rockchip,rk3368-cru.yaml
-rw-rw-r-- 1 me me 2,5K okt 20 11:32 rockchip,rk3399-cru.yaml
-rw-rw-r-- 1 me me 1,5K okt 20 11:32 rockchip,rk3528-cru.yaml
-rw-rw-r-- 1 me me 1,1K okt 20 11:32 rockchip,rk3562-cru.yaml
-rw-rw-r-- 1 me me 1,8K okt 20 11:32 rockchip,rk3568-cru.yaml
-rw-rw-r-- 1 me me 1,2K okt 20 11:32 rockchip,rk3576-cru.yaml
-rw-rw-r-- 1 me me 1,6K okt 20 11:32 rockchip,rk3588-cru.yaml
-rw-rw-r-- 1 me me 2,2K okt 20 11:32 rockchip,rv1108-cru.yaml
-rw-rw-r-- 1 me me 1,3K okt 20 11:32 rockchip,rv1126-cru.yaml
> index 000000000000..8be34bcde7b0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/clock/rockchip,clk-pvtpll.yaml
> @@ -0,0 +1,100 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/clock/rockchip,clk-pvtpll.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Rockchip Pvtpll
> +
> +maintainers:
> + - Elaine Zhang <zhangqing@rock-chips.com>
> + - Heiko Stuebner <heiko@sntech.de>
> +
> +properties:
> + compatible:
> + items:
> + - enum:
> + - rockchip,rv1103b-core-pvtpll
> + - rockchip,rv1103b-enc-pvtpll
> + - rockchip,rv1103b-isp-pvtpll
> + - rockchip,rv1103b-npu-pvtpll
> + - rockchip,rv1126b-core-pvtpll
> + - rockchip,rv1126b-isp-pvtpll
> + - rockchip,rv1126b-enc-pvtpll
> + - rockchip,rv1126b-aisp-pvtpll
> + - rockchip,rv1126b-npu-pvtpll
> + - rockchip,rk3506-core-pvtpll
> + - const: syscon
> +
> + reg:
> + maxItems: 1
> +
> + "#clock-cells":
> + const: 0
> +
> + clocks:
> + maxItems: 1
> +
> + clock-output-names:
> + maxItems: 1
> +
> + rockchip,cru:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description: |
> + Phandle to the main Clock and Reset Unit (CRU) controller.
> + Required for PVTPLLs that need to interact with the main CRU
> + for clock management operations.
> +
> +required:
> + - "#clock-cells"
> + - compatible
> + - reg
> + - clock-output-names
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + pvtpll_core: pvtpll-core@20480000 {
> + compatible = "rockchip,rv1126b-core-pvtpll", "syscon";
> + reg = <0x20480000 0x100>;
> + #clock-cells = <0>;
> + clock-output-names = "clk_core_pvtpll";
> + };
> +
> + - |
> + pvtpll_isp: pvtpll-isp@21c60000 {
> + compatible = "rockchip,rv1126b-isp-pvtpll", "syscon";
> + reg = <0x21c60000 0x100>;
> + rockchip,cru = <&cru>;
> + #clock-cells = <0>;
> + clock-output-names = "clk_isp_pvtpll";
> + };
> +
> + - |
> + pvtpll_enc: pvtpll-enc@21f00000 {
> + compatible = "rockchip,rv1126b-enc-pvtpll", "syscon";
> + reg = <0x21f00000 0x100>;
> + #clock-cells = <0>;
> + clock-output-names = "clk_vepu_pvtpll";
> + };
> +
> + - |
> + pvtpll_aisp: pvtpll-aisp@21fc0000 {
> + compatible = "rockchip,rv1126b-aisp-pvtpll", "syscon";
> + reg = <0x21fc0000 0x100>;
> + rockchip,cru = <&cru>;
> + #clock-cells = <0>;
> + clock-output-names = "clk_vcp_pvtpll";
> + };
> +
> + - |
> + pvtpll_npu: pvtpll-npu@22080000 {
> + compatible = "rockchip,rv1126b-npu-pvtpll", "syscon";
> + reg = <0x22080000 0x100>;
> + rockchip,cru = <&cru>;
> + #clock-cells = <0>;
> + clock-output-names = "clk_npu_pvtpll";
rockchip,cru line as the last line?
Cheers,
Diederik
> + };
> +
> +...
next prev parent reply other threads:[~2025-10-20 9:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 2:37 [PATCH v3 0/5] clk: rockchip: Add clock controller for the RV1126B Elaine Zhang
2025-10-20 2:37 ` [PATCH v3 1/5] clk: rockchip: Implement rockchip_clk_register_armclk_multi_pll() Elaine Zhang
2025-10-20 2:37 ` [PATCH v3 2/5] dt-bindings: clock, reset: Add support for rv1126b Elaine Zhang
2025-10-20 17:27 ` Conor Dooley
2025-10-20 2:37 ` [PATCH v3 3/5] clk: rockchip: Add clock controller for the RV1126B Elaine Zhang
2025-10-20 2:37 ` [PATCH v3 4/5] dt-bindings: clock: Add support for rockchip pvtpll Elaine Zhang
2025-10-20 9:38 ` Diederik de Haas [this message]
2025-10-20 17:25 ` Conor Dooley
2025-10-20 17:26 ` Conor Dooley
2025-10-20 2:37 ` [PATCH v3 5/5] clk: rockchip: add support for pvtpll clk Elaine Zhang
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=DDN1RQB4LG0X.30F0A3IMJ4YI4@cknow-tech.com \
--to=diederik@cknow-tech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=sugar.zhang@rock-chips.com \
--cc=zhangqing@rock-chips.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