From: Krzysztof Kozlowski <krzk@kernel.org>
To: Gary Yang <gary.yang@cixtech.com>,
p.zabel@pengutronix.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
cix-kernel-upstream@cixtech.com
Subject: Re: [PATCH 3/3] dts: reset: add support for cix sky1 resets
Date: Fri, 7 Nov 2025 08:19:53 +0100 [thread overview]
Message-ID: <d7770d3e-bc35-4539-a927-0387cdec2b2c@kernel.org> (raw)
In-Reply-To: <20251107033819.587712-4-gary.yang@cixtech.com>
On 07/11/2025 04:38, Gary Yang wrote:
> There are two reset conctrollers on Cix Sky1 Soc.
> One is located in S0 domain, and the other is located
> in S5 domain.
>
> Signed-off-by: Gary Yang <gary.yang@cixtech.com>
> ---
> arch/arm64/boot/dts/cix/sky1.dtsi | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching. For bindings, the preferred subjects are
explained here:
https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters
Please start paying attention to this.
>
> diff --git a/arch/arm64/boot/dts/cix/sky1.dtsi b/arch/arm64/boot/dts/cix/sky1.dtsi
> index d21387224e79..fc68734f37c2 100644
> --- a/arch/arm64/boot/dts/cix/sky1.dtsi
> +++ b/arch/arm64/boot/dts/cix/sky1.dtsi
> @@ -348,6 +348,13 @@ i3c1: i3c@4100000 {
> status = "disabled";
> };
>
> + src_fch: reset-controller@4160000 {
> + compatible = "cix,sky1-rst-fch", "syscon";
> + reg = <0x0 0x04160000 0x0 0x90>;
> + #reset-cells = <1>;
> + status = "okay";
Why?
> + };
> +
> iomuxc: pinctrl@4170000 {
> compatible = "cix,sky1-iomuxc";
> reg = <0x0 0x04170000 0x0 0x1000>;
> @@ -568,6 +575,13 @@ ppi_partition1: interrupt-partition-1 {
> };
> };
>
> + src: reset-controller@16000000 {
> + compatible = "cix,sky1-rst", "syscon";
> + reg = <0x0 0x16000000 0x0 0x1000>;
> + #reset-cells = <1>;
> + status = "okay";
No, really, why?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-07 7:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 3:38 [PATCH 0/3] Add support for Cix Sky1 resets Gary Yang
2025-11-07 3:38 ` [PATCH 1/3] dt-bindings: reset: add sky1 reset controller Gary Yang
2025-11-07 7:17 ` Krzysztof Kozlowski
2025-11-10 5:56 ` 回复: " Gary Yang
2025-11-07 13:25 ` Philipp Zabel
2025-11-10 6:43 ` 回复: " Gary Yang
2025-11-07 3:38 ` [PATCH 2/3] Reset: cix: add support for cix sky1 resets Gary Yang
2025-11-07 7:19 ` Krzysztof Kozlowski
2025-11-10 11:18 ` 回复: " Gary Yang
2025-11-10 11:22 ` Krzysztof Kozlowski
2025-11-10 11:32 ` 回复: " Gary Yang
2025-11-10 11:38 ` Krzysztof Kozlowski
2025-11-10 12:11 ` 回复: " Gary Yang
2025-11-07 13:25 ` Philipp Zabel
2025-11-07 3:38 ` [PATCH 3/3] dts: reset: " Gary Yang
2025-11-07 7:19 ` Krzysztof Kozlowski [this message]
2025-11-10 11:22 ` 回复: " Gary Yang
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=d7770d3e-bc35-4539-a927-0387cdec2b2c@kernel.org \
--to=krzk@kernel.org \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gary.yang@cixtech.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@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).