linux-kernel - Re: [PATCH v2 2/3] dt-bindings: mfd: Add Realtek MISC system controller

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: <38d7aacd-1c05-4040-8575-bdec0587e08f@kernel.org>
Date: Mon, 17 Nov 2025 14:31:45 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Yu-Chun Lin [林祐君] <eleanor.lin@...ltek.com>,
 "afaerber@...e.de" <afaerber@...e.de>, "robh@...nel.org" <robh@...nel.org>,
 "krzk+dt@...nel.org" <krzk+dt@...nel.org>,
 "conor+dt@...nel.org" <conor+dt@...nel.org>, "lee@...nel.org"
 <lee@...nel.org>, James Tai [戴志峰]
 <james.tai@...ltek.com>
Cc: "linux-arm-kernel@...ts.infradead.org"
 <linux-arm-kernel@...ts.infradead.org>,
 "linux-realtek-soc@...ts.infradead.org"
 <linux-realtek-soc@...ts.infradead.org>,
 "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 CY_Huang[黃鉦晏] <cy.huang@...ltek.com>,
 Stanley Chang[昌育德] <stanley_chang@...ltek.com>
Subject: Re: [PATCH v2 2/3] dt-bindings: mfd: Add Realtek MISC system
 controller

On 17/11/2025 13:41, Yu-Chun Lin [林祐君] wrote:
>>>
>>
>> None of them. You need SoC specific compatibles which can be used as
>> fallbacks for SoC specific compatibles. There is plenty of examples for this
>> already, but anyway this does not solve the problem that you still did not
>> properly describe the hardware but instead use your downstream as
>> arguments.
>>
>> This will get you nowhere.
> 
> To implement this fallback structure, my understanding is that the
> SoC-level DTSI should override the node and prepend its SoC-specific
> Compatible, while the common DTSI only provides the family-level
> compatible.
> 
> /* common DTSI */
> misc: syscon@... {
>     compatible = "realtek,kent-misc", "syscon", "simple-mfd";

No. You changed nothing. How does this differ from options I disagreed with?

Anyway, there is no such SoC as "kent" and I was clear - you need SoC
compatibles.

Define what is your SoC first.

Best regards,
Krzysztof