linux-kernel - Re: [PATCH 1/4] dt-bindings: Document new common property: has-inaccessible-regs

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4fc059f0-8aab-4bd2-a7a2-33a532117e71@kernel.org>
Date: Sat, 29 Nov 2025 16:49:11 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Richard Weinberger <richard@....at>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
 linux-omap <linux-omap@...r.kernel.org>,
 devicetree <devicetree@...r.kernel.org>, Arnd Bergmann <arnd@...db.de>,
 Lee Jones <lee@...nel.org>, dakr <dakr@...nel.org>,
 "Rafael J. Wysocki" <rafael@...nel.org>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
 Mark Brown <broonie@...nel.org>, tony <tony@...mide.com>,
 rogerq <rogerq@...nel.org>, khilman <khilman@...libre.com>,
 Andreas Kemnade <andreas@...nade.info>, aaro koskinen
 <aaro.koskinen@....fi>, Conor Dooley <conor+dt@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, robh <robh@...nel.org>
Subject: Re: [PATCH 1/4] dt-bindings: Document new common property:
 has-inaccessible-regs

On 29/11/2025 16:44, Krzysztof Kozlowski wrote:
>>         scm_conf_clocks: clocks {
>>                 #address-cells = <1>;
>>                 #size-cells = <0>;
>>         };      
>> };
>>
>> So, drivers like ti,pbias-dra7 or ti,dra7xx-phy-gmii-sel touch only registers
>> they know about and this works well.
>> But syscon manages the whole register map via regmap, and regmap exposes it all
>> via debugfs.
>>
>> What solution do you propose?
>> Splitting reg = <0x0 0x1400> into many tiny fractions and not using an mfd anymore?
> 
> Fix the driver. In your case, the syscon driver.

BTW, the state of existing TI DRA code is so poor that you don't have
many choices... or rather every choice has drawbacks. If this was proper
DTS, then I would say - define register map, used by regmap, for your
compatible either in syscon driver or dedicated driver (thus new driver
will be the syscon provider for you, just like Google GS101 syscon is
special).

Or maybe this is not syscon at all!

Remember that syscon is a collection of miscellaneous system controller
registers. You should not use syscon for other things, like devices with
incomplete hardware description.

Best regards,
Krzysztof