From: "Markus Schneider-Pargmann" <msp@baylibre.com>
To: "Simon Glass" <sjg@chromium.org>, <msp@baylibre.com>
Cc: <u-boot@lists.u-boot-project.org>,
"Tom Rini" <trini@konsulko.com>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"Daniel Schultz" <d.schultz@phytec.de>,
"Udit Kumar" <u-kumar1@ti.com>,
"Richard Genoud" <richard.genoud@bootlin.com>,
"Anshul Dalal" <anshuld@ti.com>,
"Aristo Chen" <aristo.chen@canonical.com>,
"Kory Maincent" <kory.maincent@bootlin.com>,
"Paresh Bhagat" <p-bhagat@ti.com>,
"Julien Panis" <jpanis@baylibre.com>
Subject: Re: [PATCH v3 2/6] dm: core: Add SPL_DM_EVENT
Date: Mon, 02 Nov 2026 10:26:44 +0100 [thread overview]
Message-ID: <DMKM8ZUYIQG2.J82LOEGKW71T@baylibre.com> (raw)
In-Reply-To: <CAFLszTi54DouCiL-JPo_1NztwBbRNve-dyQjo-s1Od-kQCG71Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
Hi Simon,
On Sat Oct 31, 2026 at 7:44 PM CET, Simon Glass wrote:
> Hi Markus,
>
> On 2026-10-30T12:27:40+11:00, Markus Schneider-Pargmann
> <msp@baylibre.com> wrote:
>> dm: core: Add SPL_DM_EVENT
>>
>> Add an option to allow DM_EVENT in SPL.
>
> Please can you say why this is needed, i.e. that the K3 SoCs want a
> spy on EVT_DM_POST_INIT_F in SPL, so they can unlock CTRL_MMR after
> TIFS is ready but before any device is probed. It is also worth a
> sentence that CONFIG_IS_ENABLED(DM_EVENT) is currently always false in
> SPL, so with this option dm_init_and_scan() and device_notify() start
> sending events there too.
>
>> diff --git a/drivers/core/Kconfig b/drivers/core/Kconfig
>> @@ -117,6 +117,16 @@ config DM_EVENT
>> +config SPL_DM_EVENT
>> + bool
>> + depends on SPL_DM
>> + select SPL_EVENT
>
> SPL_EVENT is inside 'if EVENT' in common/Kconfig, so it depends on
> EVENT. That is fine on K3, since ARCH_K3 selects both, but another
> board selecting SPL_DM_EVENT without EVENT would get an
> unmet-dependency warning. DM_EVENT selects EVENT, so I suggest adding
> 'select EVENT' here too.
Thanks for your review, good points, I will fix both.
Best
Markus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 289 bytes --]
next prev parent reply other threads:[~2026-11-02 9:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 12:27 [PATCH v3 0/6] K3: wait for TIFS init before CTRL_MMR unlock Markus Schneider-Pargmann
2026-10-30 12:27 ` [PATCH v3 1/6] arm: mach-k3: common: add helper to wait for TIFS initialization Markus Schneider-Pargmann
2026-11-03 7:59 ` Richard GENOUD
2026-10-30 12:27 ` [PATCH v3 2/6] dm: core: Add SPL_DM_EVENT Markus Schneider-Pargmann
2026-10-31 18:44 ` Simon Glass
2026-11-02 9:26 ` Markus Schneider-Pargmann [this message]
2026-11-02 17:15 ` Tom Rini
2026-11-02 20:44 ` Markus Schneider-Pargmann
2026-10-30 12:27 ` [PATCH v3 3/6] arm: mach-k3: am625: Wait for TIFS initialization Markus Schneider-Pargmann
2026-10-30 12:27 ` [PATCH v3 4/6] arm: mach-k3: am62a7: " Markus Schneider-Pargmann
2026-10-30 12:27 ` [PATCH v3 5/6] arm: mach-k3: am62p5: " Markus Schneider-Pargmann
2026-10-30 12:27 ` [PATCH v3 6/6] arm: mach-k3: j722s: " Markus Schneider-Pargmann
2026-11-03 7:58 ` Richard GENOUD
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=DMKM8ZUYIQG2.J82LOEGKW71T@baylibre.com \
--to=msp@baylibre.com \
--cc=anshuld@ti.com \
--cc=aristo.chen@canonical.com \
--cc=d.schultz@phytec.de \
--cc=ilias.apalodimas@linaro.org \
--cc=jpanis@baylibre.com \
--cc=kory.maincent@bootlin.com \
--cc=p-bhagat@ti.com \
--cc=richard.genoud@bootlin.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.u-boot-project.org \
--cc=u-kumar1@ti.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