Based on kernel version 6.11
. Page generated on 2024-09-24 08:21 EST
.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 | # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2 --- $id: http://devicetree.org/schemas/firmware/xilinx/xlnx,zynqmp-firmware.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# title: Xilinx firmware driver maintainers: - Nava kishore Manne <nava.kishore.manne@amd.com> description: The zynqmp-firmware node describes the interface to platform firmware. ZynqMP has an interface to communicate with secure firmware. Firmware driver provides an interface to firmware APIs. Interface APIs can be used by any driver to communicate to PMUFW(Platform Management Unit). These requests include clock management, pin control, device control, power management service, FPGA service and other platform management services. properties: compatible: oneOf: - description: For implementations complying for Zynq Ultrascale+ MPSoC. const: xlnx,zynqmp-firmware - description: For implementations complying for Versal. const: xlnx,versal-firmware - description: For implementations complying for Versal NET. items: - enum: - xlnx,versal-net-firmware - const: xlnx,versal-firmware method: description: | The method of calling the PM-API firmware layer. Permitted values are. - "smc" : SMC #0, following the SMCCC - "hvc" : HVC #0, following the SMCCC $ref: /schemas/types.yaml#/definitions/string-array enum: - smc - hvc "#power-domain-cells": const: 1 clock-controller: $ref: /schemas/clock/xlnx,versal-clk.yaml# description: The clock controller is a hardware block of Xilinx versal clock tree. It reads required input clock frequencies from the devicetree and acts as clock provider for all clock consumers of PS clocks.list of clock specifiers which are external input clocks to the given clock controller. type: object gpio: $ref: /schemas/gpio/xlnx,zynqmp-gpio-modepin.yaml# description: The gpio node describes connect to PS_MODE pins via firmware interface. type: object soc-nvmem: $ref: /schemas/nvmem/xlnx,zynqmp-nvmem.yaml# description: The ZynqMP MPSoC provides access to the hardware related data like SOC revision, IDCODE and specific purpose efuses. type: object pcap: $ref: /schemas/fpga/xlnx,zynqmp-pcap-fpga.yaml description: The ZynqMP SoC uses the PCAP (Processor Configuration Port) to configure the Programmable Logic (PL). The configuration uses the firmware interface. type: object pinctrl: $ref: /schemas/pinctrl/xlnx,zynqmp-pinctrl.yaml# description: The pinctrl node provides access to pinconfig and pincontrol functionality available in firmware. type: object power-management: $ref: /schemas/power/reset/xlnx,zynqmp-power.yaml# description: The zynqmp-power node describes the power management configurations. It will control remote suspend/shutdown interfaces. type: object reset-controller: $ref: /schemas/reset/xlnx,zynqmp-reset.yaml# description: The reset-controller node describes connection to the reset functionality via firmware interface. type: object versal-fpga: $ref: /schemas/fpga/xlnx,versal-fpga.yaml# description: Compatible of the FPGA device. type: object zynqmp-aes: $ref: /schemas/crypto/xlnx,zynqmp-aes.yaml# description: The ZynqMP AES-GCM hardened cryptographic accelerator is used to encrypt or decrypt the data with provided key and initialization vector. type: object required: - compatible additionalProperties: false examples: - | #include <dt-bindings/power/xlnx-zynqmp-power.h> firmware { zynqmp_firmware: zynqmp-firmware { #power-domain-cells = <1>; soc-nvmem { compatible = "xlnx,zynqmp-nvmem-fw"; nvmem-layout { compatible = "fixed-layout"; #address-cells = <1>; #size-cells = <1>; soc_revision: soc-revision@0 { reg = <0x0 0x4>; }; }; }; gpio { compatible = "xlnx,zynqmp-gpio-modepin"; gpio-controller; #gpio-cells = <2>; }; pcap { compatible = "xlnx,zynqmp-pcap-fpga"; }; pinctrl { compatible = "xlnx,zynqmp-pinctrl"; }; power-management { compatible = "xlnx,zynqmp-power"; interrupts = <0 35 4>; }; reset-controller { compatible = "xlnx,zynqmp-reset"; #reset-cells = <1>; }; }; }; sata { power-domains = <&zynqmp_firmware PD_SATA>; }; versal-firmware { compatible = "xlnx,versal-firmware"; method = "smc"; versal_fpga: versal-fpga { compatible = "xlnx,versal-fpga"; }; xlnx_aes: zynqmp-aes { compatible = "xlnx,zynqmp-aes"; }; versal_clk: clock-controller { #clock-cells = <1>; compatible = "xlnx,versal-clk"; clocks = <&ref>, <&pl_alt_ref>; clock-names = "ref", "pl_alt_ref"; }; }; ... |