From: "Markus Schneider-Pargmann" <msp@baylibre.com>
To: "Markus Schneider-Pargmann" <msp@baylibre.com>,
"Kumar, Udit" <u-kumar1@ti.com>,
"Richard GENOUD" <richard.genoud@bootlin.com>
Cc: "Tom Rini" <trini@konsulko.com>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"Daniel Schultz" <d.schultz@phytec.de>,
"Anshul Dalal" <anshuld@ti.com>,
"Aristo Chen" <aristo.chen@canonical.com>,
<u-boot@lists.u-boot-project.org>
Subject: Re: [PATCH 3/3] WIP: arm: mach-k3: j722s: Wait for TIFS initialization
Date: Thu, 22 Oct 2026 12:18:16 +0200 [thread overview]
Message-ID: <DMBAGGRGOEEF.1XIHBA6ILOH5J@baylibre.com> (raw)
In-Reply-To: <20261022101558.2474326-3-msp@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
Hi,
On Thu Oct 22, 2026 at 12:15 PM CEST, Markus Schneider-Pargmann wrote:
...
> +/*
> + * Called by spl_early_init() before anything is probed.
> + */
> +static int k3_spl_dm_post_init_f(void)
> +{
> + k3_sysfw_wait_ready();
> + ctrl_mmr_unlock();
> +
> + return 0;
> +}
> +EVENT_SPY_SIMPLE(EVT_DM_POST_INIT_F, k3_spl_dm_post_init_f);
I am wondering if this would work for your situation where the PMIC is
probed immediately?
Best
Markus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 289 bytes --]
prev parent reply other threads:[~2026-10-22 10:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 9:05 [PATCH v2 0/5] K3: wait for TIFS init before CTRL_MMR unlock Markus Schneider-Pargmann
2026-10-16 9:05 ` [PATCH v2 1/5] arm: mach-k3: common: add helper to wait for TIFS initialization Markus Schneider-Pargmann
2026-10-17 2:44 ` Kumar, Udit
2026-10-16 9:05 ` [PATCH v2 2/5] arm: mach-k3: am625: Wait " Markus Schneider-Pargmann
2026-10-16 9:05 ` [PATCH v2 3/5] arm: mach-k3: am62a7: " Markus Schneider-Pargmann
2026-10-16 9:05 ` [PATCH v2 4/5] arm: mach-k3: am62p5: " Markus Schneider-Pargmann
2026-10-16 9:05 ` [PATCH v2 5/5] arm: mach-k3: j722s: " Markus Schneider-Pargmann
2026-10-17 2:40 ` Kumar, Udit
2026-10-19 12:16 ` Richard GENOUD
2026-10-19 13:34 ` Kumar, Udit
2026-10-22 10:15 ` [PATCH 1/3] arm: mach-k3: common: add helper to wait " Markus Schneider-Pargmann
2026-10-22 10:15 ` [PATCH 2/3] dm: core: Add SPL_DM_EVENT Markus Schneider-Pargmann
2026-10-22 10:15 ` [PATCH 3/3] WIP: arm: mach-k3: j722s: Wait for TIFS initialization Markus Schneider-Pargmann
2026-10-22 10:18 ` Markus Schneider-Pargmann [this message]
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=DMBAGGRGOEEF.1XIHBA6ILOH5J@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=richard.genoud@bootlin.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.