Searched full:scmi (Results 1 – 13 of 13) sorted by relevance
| /Documentation/ABI/testing/ |
| D | debugfs-scmi | 1 What: /sys/kernel/debug/scmi/<n>/instance_name
5 Description: The name of the underlying SCMI instance <n> described by
6 all the debugfs accessors rooted at /sys/kernel/debug/scmi/<n>,
7 expressed as the full name of the top DT SCMI node under which
8 this SCMI instance is rooted.
11 What: /sys/kernel/debug/scmi/<n>/atomic_threshold_us
16 on this SCMI instance <n>, the threshold above which any SCMI
22 What: /sys/kernel/debug/scmi/<n>/transport/type
27 SCMI instance <n>.
30 What: /sys/kernel/debug/scmi/<n>/transport/is_atomic
[all …]
|
| D | debugfs-scmi-raw | 1 What: /sys/kernel/debug/scmi/<n>/raw/message
5 Description: SCMI Raw synchronous message injection/snooping facility; write
6 a complete SCMI synchronous command message (header included)
8 backend SCMI server for instance <n>.
16 What: /sys/kernel/debug/scmi/<n>/raw/message_async
20 Description: SCMI Raw asynchronous message injection/snooping facility; write
21 a complete SCMI asynchronous command message (header included)
23 backend SCMI server for instance <n>.
34 What: /sys/kernel/debug/scmi/<n>/raw/errors
38 Description: SCMI Raw message errors facility; any kind of timed-out or
[all …]
|
| /Documentation/devicetree/bindings/firmware/ |
| D | arm,scmi.yaml | 5 $id: http://devicetree.org/schemas/firmware/arm,scmi.yaml#
8 title: System Control and Management Interface (SCMI) Message Protocol
14 The SCMI is intended to allow agents such as OSPM to manage various functions
19 the SCMI as described in ARM document number ARM DEN 0056 ("ARM System Control
26 - $ref: /schemas/firmware/nxp,imx95-scmi.yaml
30 const: scmi
34 - description: SCMI compliant firmware with mailbox transport
36 - const: arm,scmi
37 - description: SCMI compliant firmware with ARM SMC/HVC transport
39 - const: arm,scmi-smc
[all …]
|
| D | nxp,imx95-scmi.yaml | 5 $id: http://devicetree.org/schemas/firmware/nxp,imx95-scmi.yaml#
8 title: i.MX95 System Control and Management Interface(SCMI) Vendor Protocols Extension
15 $ref: '/schemas/firmware/arm,scmi.yaml#/$defs/protocol-node'
23 $ref: '/schemas/firmware/arm,scmi.yaml#/$defs/protocol-node'
|
| D | nxp,imx95-scmi-pinctrl.yaml | 5 $id: http://devicetree.org/schemas/firmware/nxp,imx95-scmi-pinctrl.yaml#
8 title: i.MX System Control and Management Interface (SCMI) Pinctrl Protocol
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | fsl,mu.yaml | 182 scmi-sram-section@0 {
183 compatible = "arm,scmi-shmem";
187 scmi-sram-section@80 {
188 compatible = "arm,scmi-shmem";
|
| D | arm,mhu.yaml | 140 scmi {
141 compatible = "arm,scmi";
|
| /Documentation/devicetree/bindings/arm/stm32/ |
| D | stm32.yaml | 99 - st,stm32mp157c-ed1-scmi
101 - st,stm32mp157a-dk1-scmi
103 - st,stm32mp157c-dk2-scmi
111 - const: st,stm32mp157c-ev1-scmi
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | st,stm32-rproc.yaml | 185 /* Hold boot managed using SCMI reset controller */
186 resets = <&scmi MCU_R>, <&scmi MCU_HOLD_BOOT_R>;
|
| /Documentation/i2c/busses/ |
| D | i2c-i801.rst | 140 The first thing to try is the "i2c-scmi" ACPI driver. It could be that the
142 i2c-scmi driver works for you, just forget about the i2c-i801 driver and
143 don't try to unhide the ICH SMBus. Even if i2c-scmi doesn't work, you
|
| /Documentation/devicetree/bindings/net/ |
| D | brcm,asp-v2.0.yaml | 113 clocks = <&scmi 14>;
|
| /Documentation/devicetree/bindings/arm/ |
| D | cpus.yaml | 319 PM domain provider, must be "psci". For SCMI based platforms, the name
320 corresponding to the index of an SCMI performance domain provider, must be
|
| /Documentation/devicetree/bindings/sram/ |
| D | sram.yaml | 90 - arm,scmi-shmem
|