Re: 回复: 回复: 回复: [EXT] Re: [PATCH v3 02/17] firmware: scmi: smt: Interrupt communication enable

[Marek Vasut]

On 1/9/25 1:49 AM, Peng Fan wrote:

[...]

>>>>> My commit log may have caused your misunderstanding. If the bit
>> is
>>>>> not set,
>>>> the System Manager will not request doorbell interrupt. The
>> following
>>>> is the code from imx-sm:
>>>>>
>>>>>                if (callee)
>>>>>                {
>>>>>                    /* Generate completion interrupt */
>>>>>                    if ((buf->channelFlags & SMT_COMP_INT) != 0U)
>>>>>                    {
>>>>>                        status = RPC_SMT_DoorbellRing(smtChannel);
>>>>>                    }
>>>>>                }
>>>> Can the SM be updated instead ?
>>>
>>> System Manager not only interacts with U-Boot, but also with
>> Linux/QNX/RTOS. System Manager cannot be changed.
>> How come other SCMI providers (like optee) do not need this kind of
>> change ?
> 
> Could we use a Kconfig option here, saying CONFIG_SCMI_INTR_EN?
> Then to i.MX95, select this Kconfig option and not break others
> saying optee.
> 
> There is less chance for System Manager to change. If you would
> like to do some change, you could do a PR, I could ask owner to
> give a look.
My understanding is that SCMI is supposed to be an ABI and that ABI is 
supposed to be the same across different platforms, correct ?

Therefore, I am wondering why does the MX95 need this special 
workaround, and whether that workaround should be fixed in the SCMI 
server OR whether other platforms need the same change as well ?