lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
 <PUZPR06MB588741C462CBBECB9D8BBD0AEF66A@PUZPR06MB5887.apcprd06.prod.outlook.com>
Date: Fri, 6 Feb 2026 02:32:32 +0000
From: Gary Yang <gary.yang@...tech.com>
To: Krzysztof Kozlowski <krzk@...nel.org>, "robh@...nel.org"
	<robh@...nel.org>, "krzk+dt@...nel.org" <krzk+dt@...nel.org>,
	"conor+dt@...nel.org" <conor+dt@...nel.org>, "p.zabel@...gutronix.de"
	<p.zabel@...gutronix.de>, Peter Chen <peter.chen@...tech.com>,
	"unicorn_wang@...look.com" <unicorn_wang@...look.com>, "inochiama@...il.com"
	<inochiama@...il.com>, "alchark@...il.com" <alchark@...il.com>
CC: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, cix-kernel-upstream
	<cix-kernel-upstream@...tech.com>
Subject:
 回复: [PATCH v7 3/3] arm64: dts: cix: add support for cix sky1 resets

Hi Krzysztof:

I'm glad your comments.

> EXTERNAL EMAIL
> 
> On 04/02/2026 03:06, Gary Yang wrote:
> > There are two reset conctrollers on Cix Sky1 Soc. One is located in S0
> > domain, and the other is located in S0 and S5 domain.
> >
> > Signed-off-by: Gary Yang <gary.yang@...tech.com>
> > ---
> >  arch/arm64/boot/dts/cix/sky1.dtsi | 14 ++++++++++++++
> >  1 file changed, 14 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/cix/sky1.dtsi
> > b/arch/arm64/boot/dts/cix/sky1.dtsi
> > index 64b76905cbff..37dca97b6b67 100644
> > --- a/arch/arm64/boot/dts/cix/sky1.dtsi
> > +++ b/arch/arm64/boot/dts/cix/sky1.dtsi
> > @@ -348,6 +348,13 @@ i3c1: i3c@...0000 {
> >                       status = "disabled";
> >               };
> >
> > +             syscon: syscon@...0000 {
> > +                     compatible = "cix,sky1-system-control", "syscon",
> > +                                  "simple-mfd";
> > +                     reg = <0x0 0x4160000 0x0 0x100>;
> > +                     #reset-cells = <1>;
> > +             };
> > +
> >               iomuxc: pinctrl@...0000 {
> >                       compatible = "cix,sky1-pinctrl";
> >                       reg = <0x0 0x04170000 0x0 0x1000>; @@ -568,6
> > +575,13 @@ ppi_partition1: interrupt-partition-1 {
> >                       };
> >               };
> >
> > +             s5_syscon: s5-syscon@...00000 {
> 
> Node names should be generic. See also an explanation and list of examples
> (not exhaustive) in DT specification:
> https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-
> basics.html#generic-names-recommendation
> If you cannot find a name matching your device, please check in kernel sources
> for similar cases or you can grow the spec (via pull request to DT spec repo).
> 
> e.g. syscon
> 

Yes, you're right. This is my bad. I have realized my stupid mistakes.
I get a lot from your comments. Thanks for your advices.
We will fix it on next version.

Best Regards
Gary

> 
> Best regards,
> Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ