linux-kernel - Re: 回复: [PATCH v8 1/3] dt-bindings: soc: cix: document the simple-mfd syscon on Sky1 SoC

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <2c7ebaf4-5f0c-4712-bf7b-d5b2fa6e5366@kernel.org>
Date: Tue, 10 Feb 2026 08:32:57 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Gary Yang <gary.yang@...tech.com>, "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: Re: 回复: [PATCH v8 1/3] dt-bindings: soc: cix: document the simple-mfd syscon on Sky1 SoC

On 10/02/2026 04:37, Gary Yang wrote:
>>> +examples:
>>> +  - |
>>> +    syscon@...00000 {
>>> +      compatible = "cix,sky1-s5-system-control", "syscon";
>>> +      reg = <0x16000000 0x1000>;
>>> +      #reset-cells = <1>;
>>> +    };
>>> diff --git a/include/dt-bindings/reset/cix,sky1-rst-fch.h
>>> b/include/dt-bindings/reset/cix,sky1-rst-fch.h
>>
>> Filename must match compatible.
>>
>> I am pretty sure I gave such feedback to Cix before....
>>
> 
> Yes, You're right. I remember it. But please allow us to explain it.
> This header file contains many macros for reset signals. We intend to use syscon as a common module.
> So it is not only reset controller, it can also be used by other modules in futher. If the file named by syscon, 
> Maybe make confuse. All right?

Really? How?

Not able to find the header because it is randomly named would confuse
more. You don't get exceptions from the rules. Multiple people before
also asked for some special naming for whatever reasons. It's the last
time I am asking you of it. Read the docs and follow it and we really do
not care what internally you want, because you are contributing to
GENERIC kernel so you must follow common and generic rules.


Best regards,
Krzysztof