Re: [PATCH v5 1/2] dt-bindings: mailbox: add binding doc for the ARM SMC/HVC mailbox
From: Jassi Brar <jassisinghbrar@gmail.com>
Date: 2019-08-30 07:21:46
Also in:
linux-devicetree, lkml
From: Jassi Brar <jassisinghbrar@gmail.com>
Date: 2019-08-30 07:21:46
Also in:
linux-devicetree, lkml
On Fri, Aug 30, 2019 at 1:28 AM Peng Fan [off-list ref] wrote:
quoted
quoted
+examples: + - | + sram@910000 { + compatible = "mmio-sram"; + reg = <0x0 0x93f000 0x0 0x1000>; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0 0x0 0x93f000 0x1000>; + + cpu_scp_lpri: scp-shmem@0 { + compatible = "arm,scmi-shmem"; + reg = <0x0 0x200>; + }; + + cpu_scp_hpri: scp-shmem@200 { + compatible = "arm,scmi-shmem"; + reg = <0x200 0x200>; + }; + }; + + firmware { + smc_mbox: mailbox { + #mbox-cells = <1>; + compatible = "arm,smc-mbox"; + method = "smc"; + arm,num-chans = <0x2>; + transports = "mem"; + /* Optional */ + arm,func-ids = <0xc20000fe>, <0xc20000ff>;SMC/HVC is synchronously(block) running in "secure mode", i.e, there can only be one instance running platform wide. Right?I think there could be channel for TEE, and channel for Linux. For virtualization case, there could be dedicated channel for each VM.
I am talking from Linux pov. Functions 0xfe and 0xff above, can't both be active at the same time, right? _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel