From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Johan Jonker <jbx6244@gmail.com>,
heiko@sntech.de, zhangqing@rock-chips.com
Cc: robh+dt@kernel.org, krzk+dt@kernel.org, mturquette@baylibre.com,
sboyd@kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/3] arm64: dts: rockchip: fix compatible string rk3328 cru node
Date: Tue, 29 Mar 2022 19:23:05 +0200 [thread overview]
Message-ID: <09fa521e-dcf9-b744-da30-86542fd8855e@linaro.org> (raw)
In-Reply-To: <20220329163016.27458-2-jbx6244@gmail.com>
On 29/03/2022 18:30, Johan Jonker wrote:
> The rockchip,rk3328-cru.txt file was converted to YAML.
> A DT test of the rk3328 cru node gives notifications regarding
> the compatible string. Bring it in line with the binding by
> removing some unused fall back strings.
Are you sure these are unused? rockchip,cru maybe, but what about DTS
used out of tree? It's useful to mention that the compatible is not
documented (so if there are any out of tree users, it's their fault).
Removal of syscon is different case - why do you think it is unused? Did
you check it? It's not a fallback compatible.
>
> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> ---
> arch/arm64/boot/dts/rockchip/rk3328.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> index b822533dc..73418fd2f 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> @@ -756,7 +756,7 @@
> };
>
> cru: clock-controller@ff440000 {
> - compatible = "rockchip,rk3328-cru", "rockchip,cru", "syscon";
> + compatible = "rockchip,rk3328-cru";
> reg = <0x0 0xff440000 0x0 0x1000>;
> rockchip,grf = <&grf>;
> #clock-cells = <1>;
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Johan Jonker <jbx6244@gmail.com>,
heiko@sntech.de, zhangqing@rock-chips.com
Cc: robh+dt@kernel.org, krzk+dt@kernel.org, mturquette@baylibre.com,
sboyd@kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/3] arm64: dts: rockchip: fix compatible string rk3328 cru node
Date: Tue, 29 Mar 2022 19:23:05 +0200 [thread overview]
Message-ID: <09fa521e-dcf9-b744-da30-86542fd8855e@linaro.org> (raw)
In-Reply-To: <20220329163016.27458-2-jbx6244@gmail.com>
On 29/03/2022 18:30, Johan Jonker wrote:
> The rockchip,rk3328-cru.txt file was converted to YAML.
> A DT test of the rk3328 cru node gives notifications regarding
> the compatible string. Bring it in line with the binding by
> removing some unused fall back strings.
Are you sure these are unused? rockchip,cru maybe, but what about DTS
used out of tree? It's useful to mention that the compatible is not
documented (so if there are any out of tree users, it's their fault).
Removal of syscon is different case - why do you think it is unused? Did
you check it? It's not a fallback compatible.
>
> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> ---
> arch/arm64/boot/dts/rockchip/rk3328.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> index b822533dc..73418fd2f 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> @@ -756,7 +756,7 @@
> };
>
> cru: clock-controller@ff440000 {
> - compatible = "rockchip,rk3328-cru", "rockchip,cru", "syscon";
> + compatible = "rockchip,rk3328-cru";
> reg = <0x0 0xff440000 0x0 0x1000>;
> rockchip,grf = <&grf>;
> #clock-cells = <1>;
Best regards,
Krzysztof
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Johan Jonker <jbx6244@gmail.com>,
heiko@sntech.de, zhangqing@rock-chips.com
Cc: robh+dt@kernel.org, krzk+dt@kernel.org, mturquette@baylibre.com,
sboyd@kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/3] arm64: dts: rockchip: fix compatible string rk3328 cru node
Date: Tue, 29 Mar 2022 19:23:05 +0200 [thread overview]
Message-ID: <09fa521e-dcf9-b744-da30-86542fd8855e@linaro.org> (raw)
In-Reply-To: <20220329163016.27458-2-jbx6244@gmail.com>
On 29/03/2022 18:30, Johan Jonker wrote:
> The rockchip,rk3328-cru.txt file was converted to YAML.
> A DT test of the rk3328 cru node gives notifications regarding
> the compatible string. Bring it in line with the binding by
> removing some unused fall back strings.
Are you sure these are unused? rockchip,cru maybe, but what about DTS
used out of tree? It's useful to mention that the compatible is not
documented (so if there are any out of tree users, it's their fault).
Removal of syscon is different case - why do you think it is unused? Did
you check it? It's not a fallback compatible.
>
> Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> ---
> arch/arm64/boot/dts/rockchip/rk3328.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> index b822533dc..73418fd2f 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> @@ -756,7 +756,7 @@
> };
>
> cru: clock-controller@ff440000 {
> - compatible = "rockchip,rk3328-cru", "rockchip,cru", "syscon";
> + compatible = "rockchip,rk3328-cru";
> reg = <0x0 0xff440000 0x0 0x1000>;
> rockchip,grf = <&grf>;
> #clock-cells = <1>;
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-29 17:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 16:30 [PATCH v1 1/3] dt-bindings: clock: convert rockchip,rk3328-cru.txt to YAML Johan Jonker
2022-03-29 16:30 ` [PATCH v1 1/3] dt-bindings: clock: convert rockchip, rk3328-cru.txt " Johan Jonker
2022-03-29 16:30 ` Johan Jonker
2022-03-29 16:30 ` [PATCH v1 2/3] arm64: dts: rockchip: fix compatible string rk3328 cru node Johan Jonker
2022-03-29 16:30 ` Johan Jonker
2022-03-29 16:30 ` Johan Jonker
2022-03-29 17:23 ` Krzysztof Kozlowski [this message]
2022-03-29 17:23 ` Krzysztof Kozlowski
2022-03-29 17:23 ` Krzysztof Kozlowski
2022-03-29 17:43 ` Johan Jonker
2022-03-29 17:43 ` Johan Jonker
2022-03-29 17:43 ` Johan Jonker
2022-03-29 16:30 ` [PATCH v1 3/3] arm64: rockchip: add clocks property to cru node rk3328 Johan Jonker
2022-03-29 16:30 ` Johan Jonker
2022-03-29 16:30 ` Johan Jonker
2022-03-29 17:20 ` [PATCH v1 1/3] dt-bindings: clock: convert rockchip, rk3328-cru.txt to YAML Krzysztof Kozlowski
2022-03-29 17:20 ` Krzysztof Kozlowski
2022-03-29 17:20 ` Krzysztof Kozlowski
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=09fa521e-dcf9-b744-da30-86542fd8855e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=krzk+dt@kernel.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+dt@kernel.org \
--cc=sboyd@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.