Re: [RFC PATCH 2/2] firmware: qcom: scm: Handle QSEECOM listener callbacks

[Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>]

On 11/1/26 5:01 PM, Haozhen Li wrote:
> A QSEE app that needs something from the normal world -- nearly
> always file I/O against its secure storage -- does not return from the
> SCM call. Instead the call comes back as QSEECOM_RESULT_INCOMPLETE
> naming the listener the app waits for, and stays that way until the
> normal world answers. Answering is what resumes the app.
> 
> The QSEECOM SCM helpers have no way to answer: the TODO in
> qcom_scm_qseecom_call() turns an incomplete call into a WARN and
> returns success, the app stays parked in TZ, and every later QSEECOM
> call returns -EBUSY until the device is power cycled. The machine
> allowlist in qcom_scm_qseecom_init() exists because of problems of
> this class.

Please extend this RFC with a user, we generally don't merge exported
functions without an in-tree consumer


Konrad