All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bratiranjan Acharya <bratiranjan11@gmail.com>
To: aisheng.dong@nxp.com, peng.fan@nxp.com
Cc: pankaj.gupta@nxp.com, ping.bai@nxp.com, imx@lists.linux.dev
Subject: [PATCH v2] soc: imx: imx93_lpm: return -EPROBE_DEFER when SE firmware not ready
Date: Wed, 02 Sep 2026 03:43:16 -0700 (PDT)	[thread overview]
Message-ID: <6a97fdc4.d9789fc0.362adc.c4f2@mx.google.com> (raw)

imx_get_se_data_info() returns NULL during early boot because the
EdgeLock Enclave firmware takes ~900ms to register its services.
Returning -ENODEV here permanently drops the driver with no retry,
leaving DDR DVFS and lpm-cooling non-functional.

Return -EPROBE_DEFER so the driver retries once SE firmware is up.

Tested on i.MX93: probe defers once, succeeds on retry, lpm-cooling
and DDR frequency scaling both operational.

Fixes: 711990e353bb ("LF-13910: soc: imx93: lpm changes to update exported apis")
Signed-off-by: Bratiranjan Acharya <bacharya@enphaseenergy.com>
Reviewed-by: Peng Fan <peng.fan@nxp.com>
---
v2: Add Reviewed-by from Peng Fan
 drivers/soc/imx/imx93_lpm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/soc/imx/imx93_lpm.c b/drivers/soc/imx/imx93_lpm.c
index bfa52ff8f..26d72e3e2 100644
--- a/drivers/soc/imx/imx93_lpm.c
+++ b/drivers/soc/imx/imx93_lpm.c
@@ -621,7 +621,7 @@ static int imx93_lpm_probe(struct platform_device *pdev)
 	se_data = imx_get_se_data_info(SOC_ID_OF_IMX93, 0);
 	if (!se_data) {
 		dev_err(&pdev->dev, "get se-fw2 failed\n");
-		return -ENODEV;
+		return -EPROBE_DEFER;
 	}
 
 	/*
-- 
2.34.1

             reply	other threads:[~2026-09-02 10:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 10:43 Bratiranjan Acharya [this message]
2026-09-11 18:58 ` [PATCH v2] soc: imx: imx93_lpm: return -EPROBE_DEFER when SE firmware not ready Frank Li
2026-11-02  8:50 ` bratiranjan11
2026-11-02  9:08 ` bratiranjan11

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=6a97fdc4.d9789fc0.362adc.c4f2@mx.google.com \
    --to=bratiranjan11@gmail.com \
    --cc=aisheng.dong@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=pankaj.gupta@nxp.com \
    --cc=peng.fan@nxp.com \
    --cc=ping.bai@nxp.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.