linux-kernel - Re: [V1 2/2] drivers soc: add support for ST stm32mp13xx family

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: <c682e4da-ae75-4e93-bbf1-a68f31bd15de@enneenne.com>
Date: Tue, 20 May 2025 11:01:55 +0200
From: Rodolfo Giometti <giometti@...eenne.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Maxime Coquelin <mcoquelin.stm32@...il.com>,
 Alexandre Torgue <alexandre.torgue@...s.st.com>,
 Eric Fourmont <eric.fourmont-ext@...com>,
 Yann GAUTIER <yann.gautier@...s.st.com>, linux-kernel@...r.kernel.org
Subject: Re: [V1 2/2] drivers soc: add support for ST stm32mp13xx family

On 19/05/25 20:34, Krzysztof Kozlowski wrote:
> On 19/05/2025 15:08, Rodolfo Giometti wrote:

[snip]

>> +
>> +static int __init stm32mp13_soc_get_idc(u32 *idc)
>> +{
>> +	struct device_node *np;
>> +	void __iomem *regs;
>> +	static const struct of_device_id devids[] = {
>> +		{ .compatible = "st,stm32mp157-syscfg" },
> 
> No, don't add compatibles for other devices into the driver functions.
> Use standard methods for binding, like every driver does.

I need to access a region assigned to another driver very early on boot, and 
this is the only way I've found to solve the problem. Can you please give me an 
example of these standard binding methods?

Thanks in advance,

Rodolfo

-- 
GNU/Linux Solutions                  e-mail: giometti@...eenne.com
Linux Device Driver                          giometti@...ux.it
Embedded Systems                     phone:  +39 349 2432127
UNIX programming