Searched full:agents (Results 1 – 9 of 9) sorted by relevance
60 * IDC[slave_core_id].agents[agent_id].ipc;67 * Each connection is organized into two "agents" ("A" - master core and "B" - slave core).69 * Agents array represents mutually exclusive IPC endpoint access:70 * (A=1/B=0) - agents[0].71 * (A=0/B=1) - agents[1].76 } agents[2]; member
59 * IDC[slave_core_id].agents[agent_id].ipc;66 * Each connection is organized into two "agents" ("A" - master core and "B" - slave core).68 * Agents array represents mutually exclusive IPC endpoint access:69 * (A=1/B=0) - agents[0].70 * (A=0/B=1) - agents[1].75 } agents[2]; member
45 uint32_t msg = IDC[cpu_id].agents[0].ipc.tdr & ~INTEL_ADSP_IPC_BUSY; in ipc_isr()61 IDC[cpu_id].agents[0].ipc.tdr = INTEL_ADSP_IPC_BUSY; in ipc_isr()62 IDC[cpu_id].agents[0].ipc.tda = 0; in ipc_isr()104 IDC[i].agents[0].ipc.ctl = BIT(0); /* IPCTBIE */ in soc_mp_init()232 IDC[core].agents[1].ipc.idr = msg | INTEL_ADSP_IPC_BUSY; in send_ipi()
704 * Sideband peer agents (as well as access control policy owner for survivability).
28 agents and provide the necessary functionality. In some cases, the requests56 This describes how messages are exchanged between agents and the platform.65 A **channel** is the medium through which agents and the platform exchange messages.69 by two different agents for example.97 These messages are used to notify agents of events that take place on
5 messaging between two Xilinx Zynq UltraScale+ MPSoC IPI agents. Each IPI
22 uint8_t hops; /* used by relay agents when booting via relay
110 * to zero so LLDP Rx agents can invalidate the entry related to this node.
