![]() (The mechanism to wake a SMC call back up is described in detail below) Receives from HLOS via the get_wq_ctx() call. IRQ, passing to FW the same smc_call_ctx that FW HLOS needs to issue this in response to receiving an Ready to have their requests woken up (`more_pending`). Sleeping SCM calls associated with that wait-queue.Īdditionally, repeat this if there are more wait-queues that are Get the wait-queue context, and wake up either one or all of the The handshake mechanism that HLOS uses to talk to FW about wait-queue N.B.: The "ctx" in the above UID names = "context". These two additional values are passed via the a1 and a2 This is alsoįor HLOS' bookkeeping to wake this call up later. ![]() Identifying the SCM call thus being put to sleep. This is to help HLOS with its ownīookkeeping to wake this sleeping call later.Īdditionally, FW also passes to HLOS `smc_call_ctx` - a UID HLOS to put it to non-interruptible sleep.Īlong with this return value, FW also passes to HLOS `wq_ctx` -Ī unique number (UID) identifying the wait-queue that it has put Or error, FW has placed this call on a wait-queue and has signalled When an SCM call receives this return value instead of success A sleeping SCM callĬan be woken up by an interrupt that the FW raises. Value in addition to success or error: SCM_WAITQ_SLEEP. With a resource lock and puts requests on a wait-queue internally and The firmware currently being used has limited resources, it guards them When the firmware (FW) supports multiple requests per VM, multiple requestsįrom the same/different VM can reach the firmware at the same time. Next in thread: Guru Das Srinagesh: "Re: firmware: qcom: scm: Add wait-queue handling logic".In reply to: Krzysztof Kozlowski: "Re: dt-bindings: firmware: qcom-scm: Add optional interrupt".Previous message: Sibi Sankar: " dt-bindings: firmware: qcom-scm: Add optional interrupt". ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |