[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <89150929-873f-4d09-9cec-727f92572d17@oss.qualcomm.com>
Date: Tue, 21 Oct 2025 11:27:52 +0200
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Debraj Mukhopadhyay <quic_dmukhopa@...cinc.com>, quic_neersoni@...cinc.com,
andersson@...nel.org, konradybcio@...nel.org,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] qcom: ice: Prevent client probe failures on unsupported
ICE
On 10/21/25 6:03 AM, Debraj Mukhopadhyay wrote:
> Storage clients (ex. UFS and MMC) invoke of_qcom_ice_get() to obtain the
> handle from ICE (Inline Crypto Engine) driver. Currently if ICE is
> unsupported, the return code from probe could prevent the client
> initialization which is a bug. To fix this a new flag
> qcom_ice_create_error is introduced which caches the error encountered
> during ICE probe.
Probe currently only happens if the ICE node is present in the DT and
referred to from the storage controller. What does this patch solve?
Konrad
>
> The qcom_ice_create() and of_qcom_ice_get() functions are updated to
> return -EOPNOTSUPP when ICE is unsupported, allowing clients to proceed
> without ICE.
>
> For other failures, such as ICE not yet initialized, the existing
> behavior (e.g., -EPROBE_DEFER) is retained to ensure proper error
> handling.
>
> This improves error signaling and ensures that client initialization is
> not blocked unnecessarily.
>
> Signed-off-by: Debraj Mukhopadhyay <quic_dmukhopa@...cinc.com>
> ---
Powered by blists - more mailing lists