From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Sumit Garg <sumit.garg@kernel.org>, Rob Herring <robh+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, andersson@kernel.org,
konradybcio@kernel.org, abelvesa@kernel.org, mani@kernel.org,
linux-kernel@vger.kernel.org,
Sumit Garg <sumit.garg@oss.qualcomm.com>
Subject: Re: [PATCH] soc: qcom: ice: Avoid probe deferring for un-supported ICE feature
Date: Fri, 30 Jan 2026 10:59:18 +0100 [thread overview]
Message-ID: <4f629971-94cb-44aa-9502-4f5ebfd63937@oss.qualcomm.com> (raw)
In-Reply-To: <aXx_UDTkdYHY04FR@sumit-xelite>
On 1/30/26 10:52 AM, Sumit Garg wrote:
> On Fri, Jan 30, 2026 at 10:34:26AM +0100, Konrad Dybcio wrote:
>> On 1/30/26 10:11 AM, Sumit Garg wrote:
>>> From: Sumit Garg <sumit.garg@oss.qualcomm.com>
>>>
>>> ICE related SCM calls may not be supported in every TZ environment like
>>> OP-TEE or a no-TZ environment too. So let's try to avoid probe deferring
>>> when it's known that ICE feature isn't supported.
>>>
>>> This problem only came to notice after the inline encryption drivers were
>>> enabled in the arm64 defconfig by: commit 5f37788adedd ("arm64: defconfig:
>>> Enable SCSI UFS Crypto and Block Inline encryption drivers").
>>>
>>> Fixes: 2afbf43a4aec ("soc: qcom: Make the Qualcomm UFS/SDCC ICE a dedicated driver")
>>> Signed-off-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
>>> ---
>>> drivers/soc/qcom/ice.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/soc/qcom/ice.c b/drivers/soc/qcom/ice.c
>>> index b203bc685cad..ab9586b8caf5 100644
>>> --- a/drivers/soc/qcom/ice.c
>>> +++ b/drivers/soc/qcom/ice.c
>>> @@ -652,7 +652,7 @@ static struct qcom_ice *of_qcom_ice_get(struct device *dev)
>>> dev_err(dev, "Cannot get ice instance from %s\n",
>>> dev_name(&pdev->dev));
>>> platform_device_put(pdev);
>>> - return ERR_PTR(-EPROBE_DEFER);
>>> + return NULL;
>>
>> Wouldn't this wreck the "actually need to defer" case, i.e.
>>
>>
>> qcom,ufs probes first
>> calls devm_of_qcom_ice_get()
>> "ice" reg is missing, non-legacy case
>> qcom,ice is absent (not yet probed)
>> return NULL
>>
>> ...
>>
>> qcom,ice probes
>>
>> ?
>
> Since qcom,ufs depends on qcom,ice via a phandle, so isn't the probe
> orderering automatically taken care off? Or that isn't the case here?
No, that's guaranteed by devlink only with certain properties.
In this case though, I think it could make sense to add it to the
"suppliers" list in drivers/of/property.c.
I don't know if vendors adding their custom properties there is a
pattern that +Rob will be happy about though..
Konrad
next prev parent reply other threads:[~2026-01-30 9:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 9:11 Sumit Garg
2026-01-30 9:34 ` Konrad Dybcio
2026-01-30 9:52 ` Sumit Garg
2026-01-30 9:59 ` Konrad Dybcio [this message]
2026-01-30 11:36 ` Sumit Garg
2026-01-30 11:55 ` Konrad Dybcio
2026-01-30 12:29 ` Sumit Garg
2026-01-30 12:36 ` Konrad Dybcio
2026-02-02 8:32 ` Sumit Garg
2026-02-02 10:51 ` Manivannan Sadhasivam
2026-02-02 10:55 ` Manivannan Sadhasivam
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=4f629971-94cb-44aa-9502-4f5ebfd63937@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sumit.garg@kernel.org \
--cc=sumit.garg@oss.qualcomm.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®