Lines Matching full:lm
23 SM introduces a concept Logic Machine(LM) which is analogous to VM and each has
24 its own instance of SCMI. All normal SCMI calls only apply to that LM. That
25 includes boot, shutdown, reset, suspend, wake, etc. Each LM (e.g. A55 and M7)
26 are completely isolated from the others and each LM has its own communication
40 the LM running the calling agent. That includes boot, shutdown, reset,
42 of agents, it will only get those on that LM. Each LM is completely isolated
46 machines (LM). It is usually used to allow one LM(e.g. OSPM) to manage
47 another LM which is usually an offload or accelerator engine. Notifications
49 LM. The LMM protocol provides commands to:
54 - Boot a target LM.
55 - Shutdown a target LM (gracefully or forcibly).
56 - Reset a target LM (gracefully or forcibly).
57 - Wake a target LM from suspend.
58 - Suspend a target LM (gracefully).
59 - Read boot/shutdown/reset information for a target LM.
60 - Get notifications when a target LM boots or shuts down (e.g. LM 'X' requested
61 notification of LM 'Y' boots or shuts down, when LM 'Y' boots or shuts down,
62 SCMI firmware will send notification to LM 'X').
64 'Graceful' means asking LM itself to shutdown/reset/etc (e.g. sending
69 'Forceful' means the SM will force shutdown/reset/etc the LM. It is sync
70 command that the SUCCESS of the command means the LM has been successfully
114 | |field limitations, the max number of LM is 16. The minimum |
161 | |for the LM specified by lmid. |
163 |uint32 lmid |Identifier of the LM whose identification is requested. |
171 |uint32 state | Current state of the LM |
175 |char name[16] | A NULL terminated ASCII string with the LM name, of up |
197 |int32 status |SUCCESS: if LM boots successfully started. |
201 | |the LM specified by lmid. |
229 | |graceful reset or LM successfully resets in forceful reset.|
233 | |the LM specified by lmid. |
261 | |graceful request or LM successfully shutdown in forceful |
266 | |the LM specified by lmid. |
287 |int32 status |SUCCESS: if LM wake command successfully returns. |
291 | |the LM specified by lmid. |
312 |int32 status |SUCCESS: if LM suspend command successfully returns. |
316 | |the LM specified by lmid. |
381 |int32 status |SUCCESS: if the reset reason of the LM successfully |
396 | |Logical Machine(LM) ID that causes the BOOT of this LM |
415 | |Logical Machine(LM) ID that causes the BOOT of this LM |
446 |int32 status |SUCCESS: if LM successfully powers on. |
450 | |the LM specified by lmid. |
467 |uint32 cpuid |ID of the CPU inside the LM |
485 | |the reset vector for the CPU in the LM. |
527 |uint32 lmid |Identifier for the LM that caused the transition. |
529 |uint32 eventlm |Identifier of the LM this event refers to. |
531 |uint32 flags |LM events: |
534 | |1 LM has awakened. |
537 | |1 LM has suspended. |
540 | |1 LM has shutdown. |
543 | |1 LM has booted. |
560 - Set an alarm (per LM) in seconds
569 each. However, RTC alarms are maintained for each LM and the hardware is
570 programmed with the next nearest alarm time. So only one agent in an LM should
955 auxiliary CPUs in a target LM (e.g. additional cores in an AP cluster or
1282 - Read boot/shutdown/reset information for the LM or the system.
1557 | |Set to 0 to return the LM reason |