From: Rodolfo Giometti <giometti@enneenne.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Eric Fourmont <eric.fourmont-ext@st.com>,
Yann GAUTIER <yann.gautier@foss.st.com>,
linux-kernel@vger.kernel.org
Subject: Re: [V1 2/2] drivers soc: add support for ST stm32mp13xx family
Date: Tue, 20 May 2025 11:01:55 +0200 [thread overview]
Message-ID: <c682e4da-ae75-4e93-bbf1-a68f31bd15de@enneenne.com> (raw)
In-Reply-To: <4566f4c1-f4d0-4f32-8fcd-bb3057b5d1fa@kernel.org>
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@enneenne.com
Linux Device Driver giometti@linux.it
Embedded Systems phone: +39 349 2432127
UNIX programming
next prev parent reply other threads:[~2025-05-20 9:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 13:08 [V1 0/2] Add SoC support for stm32mp13xx CPUs Rodolfo Giometti
2025-05-19 13:08 ` [V1 1/2] arm stm32mp131.dtsi: add "encoding_mode" nvmem definition Rodolfo Giometti
2025-05-19 18:35 ` Krzysztof Kozlowski
2025-05-19 18:36 ` Krzysztof Kozlowski
2025-05-20 8:26 ` Yann Gautier
2025-05-20 16:29 ` Yann Gautier
2025-05-19 13:08 ` [V1 2/2] drivers soc: add support for ST stm32mp13xx family Rodolfo Giometti
2025-05-19 18:34 ` Krzysztof Kozlowski
2025-05-20 9:01 ` Rodolfo Giometti [this message]
2025-05-20 9:15 ` Krzysztof Kozlowski
2025-05-20 8:55 ` Alexandre TORGUE
2025-05-26 10:56 ` Rodolfo Giometti
2025-05-20 16:58 ` Yann Gautier
2025-05-21 15:44 ` Rodolfo Giometti
2025-05-21 16:37 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c682e4da-ae75-4e93-bbf1-a68f31bd15de@enneenne.com \
--to=giometti@enneenne.com \
--cc=alexandre.torgue@foss.st.com \
--cc=eric.fourmont-ext@st.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=yann.gautier@foss.st.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®