From a735108cb04fe29aa12fbbc90dec6d46fc9637fd Mon Sep 17 00:00:00 2001 From: Ashish Bhimanpalliwar Date: Thu, 26 Aug 2021 20:19:43 +0530 Subject: [PATCH] bindings: Adding pinctrl bindings to support vm on Kalama Adding pinctrl bindings to support vm on Kalama. This is snapshot of bindings from 'commit 53311cb5fada ("Merge "ARM: dts: msm: Remove Waipio GenC GPU strings"")' from device tree project msm-5.10 branch. Change-Id: Ifa51cd9cab904d52fadef418881d79d78d1c07b1 --- bindings/gunyah/qcom,hypervisor.yml | 177 ++++++++++++++++++ bindings/pinctrl/qcom,kalama-vm-pinctrl.yaml | 127 +++++++++++++ .../virt/gunyah/qcom,gh-vm-loader-sec.yaml | 36 ++++ 3 files changed, 340 insertions(+) create mode 100644 bindings/gunyah/qcom,hypervisor.yml create mode 100644 bindings/pinctrl/qcom,kalama-vm-pinctrl.yaml create mode 100644 bindings/virt/gunyah/qcom,gh-vm-loader-sec.yaml diff --git a/bindings/gunyah/qcom,hypervisor.yml b/bindings/gunyah/qcom,hypervisor.yml new file mode 100644 index 00000000..a95f6ace --- /dev/null +++ b/bindings/gunyah/qcom,hypervisor.yml @@ -0,0 +1,177 @@ +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/gunyah/qcom,hypervisor.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Hypervisor node to define virtual devices and other services. + +maintainers: + - Murali Nalajala + +description: |+ + Top-level node named /hypervisor that describes virtual devices and other + services. + +properties: + compatible: + oneOf: + items: + - const: qcom,gunyah-hypervisor-1.0 + - const: qcom,gunyah-hypervisor + + properties: + "#address-cells": + const: 2 + "#size-cells": + description: must be 0, because capability IDs are not memory address + ranges and do not have a size. + const: 0 + + +required: +- compatible +- "#address-cells" +- "#size-cells" + + +description: |+ + The VM Identification is a virtual node that conveys to the VM information + about itself in the context of the hypervisor-based system and may be + present as a child of the /hypervisor node + +properties: + compatible: + oneOf: + description: |+ + Must contain the VM-ID compatible string, which is provisionally + specified as "qcom,gunyah-vm-id". This should be preceded by + a string that specifies the VM ID API version, which is currently + 1.0, thus "qcom,gunyah-vm-id-1.0". + items: + - const: qcom,gunyah-vm-id-1.0 + - const: qcom,gunyah-vm-id + + properties: + qcom,vendor: + description: must contain the VM vendor string, for example: "Qualcomm Technologies, Inc.". + $ref: /schemas/types.yaml#/definitions/string + + qcom,vmid: + $ref: /schemas/types.yaml#/definitions/uint32 + description: must contain the hypervisor VMID of the VM, as + a 32-bit value + + qcom,owner-vmid: + $ref: /schemas/types.yaml#/definitions/uint32 + description: Contains the hypervisor VMID of the VM’s owner. The owner + is the VM that allocated and created the VM. VMs directly + managed by the resource manager, such as the HLOS do not + have an owner. + + qcom,image-name: + $ref: /schemas/types.yaml#/definitions/string + description: contains the VM image name string. + + qcom,swid: + $ref: /schemas/types.yaml#/definitions/uint32 + description: must contain the Qualcomm Technologies, Inc. PIL software ID value. + +required: +- compatible +- qcom,vmid +- qcom,owner-vmid + + +description: |+ + Resource Manager node which is required to communicate to Resource + Manager VM using RM Message Queues. + +properties: + compatible: + oneOf: + description: + The resource manager RPC communicate link is required to be in the + device-tree of a VM at boot, without it, a VM may be unable to + communicate with the Resource Manager. Resource Manager VM can + support implementation of various versions i.e 1.0 or 2.0 + + items: + - const: qcom,resource-manager-1-0 + - const: qcom,resource-manager + - const: qcom,gunyah-message-queue + - const: qcom,haven-capability + + interrupts: + maxItems: 2 + + reg: + maxItems: 2 + + qcom,is-full-duplex: + $ref: /schemas/types.yaml#/definitions/flag + description: This node is a pair of message queues i.e. Tx and Rx + + qcom,tx-message-size: + $ref: /schemas/types.yaml#/definitions/uint32 + description: maximum message size in bytes, >= 240 bytes for RM IPC + + qcom,tx-queue-depth: + $ref: /schemas/types.yaml#/definitions/uint32 + description: depth(size) of transmit queue in hypervisor + + qcom,rx-message-size: + $ref: /schemas/types.yaml#/definitions/uint32 + description: maximum message size in bytes, >= 240 bytes for RM IPC + + qcom,rx-queue-depth: + $ref: /schemas/types.yaml#/definitions/uint32 + description: depth(size) of receive queue in hypervisor + + qcom,console-dev: + $ref: /schemas/types.yaml#/definitions/flag + description: if set, the resource-manger will accept console logs + from the VM + + qcom,free-irq-start: + $ref: /schemas/types.yaml#/definitions/uint32 + description: first VIRQ number which is free for virtual interrupt + use. Here SPI 0 = VIRQ 32. + +required: +- compatible +- interrupts +- reg +- qcom,is-full-duplex + +examples: + - | + hypervisor { + #address-cells = <2>; + #size-cells = <0>; + compatible = "qcom,gunyah-hypervisor-1.0", "qcom,gunyah-hypervisor", + "simple-bus"; + name = "hypervisor"; + + qcom,gunyah-vm { + compatible = "qcom,gunyah-vm-id-1.0", "qcom,gunyah-vm-id"; + qcom,vendor = "Qualcomm Technologies, Inc."; + qcom,vmid = <45>; + qcom,owner-vmid = <3>; + }; + + qcom,resource-manager-rpc@0000000000000001 { + compatible = "qcom,resource-manager-1-0", "qcom,resource-manager", + "qcom,gunyah-message-queue", "qcom,haven-capability"; + interrupts = , /* TX full IRQ */ + ; /* RX empty IRQ */ + reg = <0x00000000 0x00000000>, <0x00000000 0x00000001>; + /* TX, RX cap ids */ + qcom,is-full-duplex; + qcom,free-irq-start = <0>; + qcom,tx-queue-depth = <8>; + qcom,tx-message-size = <0xf0>; + qcom,rx-queue-depth = <8>; + qcom,rx-message-size = <0xf0>; + }; + }; + diff --git a/bindings/pinctrl/qcom,kalama-vm-pinctrl.yaml b/bindings/pinctrl/qcom,kalama-vm-pinctrl.yaml new file mode 100644 index 00000000..6e6623cb --- /dev/null +++ b/bindings/pinctrl/qcom,kalama-vm-pinctrl.yaml @@ -0,0 +1,127 @@ +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/bindings/pinctrl/qcom,kalama-vm-pinctrl.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Qualcomm Technologies, Inc. KALAMA VM TLMM block + +maintainers: + +description: | + This binding describes the Top Level Mode Multiplexer block for VM. + +properties: + compatible: + const: qcom,kalama-vm-pinctrl + + reg: + items: + - description: Base address of TLMM register space + - description: Size of TLMM register space + + interrupts-extended: + Value type: + Definition: reference to the interrupts that match interrupt-names + + interrupt-controller: true + + '#interrupt-cells': + const: 2 + + gpio-controller: true + + '#gpio-cells': + const: 2 + + gpios: + description: array of gpio pin number required by VM TLMM clients + +Please refer to ../gpio/gpio.txt and ../interrupt-controller/interrupts.txt for +a general description of GPIO and interrupt bindings. + +Please refer to pinctrl-bindings.txt in this directory for details of the +common pinctrl bindings used by client devices, including the meaning of the +phrase "pin configuration node". + +The pin configuration nodes act as a container for an arbitrary number of +subnodes. Each of these subnodes represents some desired configuration for a +pin, a group, or a list of pins or groups. This configuration can include the +mux function to select on those pin(s)/group(s), and various pin configuration +parameters, such as pull-up, drive strength, etc. + + +# PIN CONFIGURATION NODES +patternPropetries: + '^.*$': + if: + type: object + then: + properties: + pins: + description: + List of gpio pins affected by the properties specified in + this subnode. + items: + oneOf: + - pattern: "^gpio([0-9]|[1-9][0-9]|1[0-9][0-9]|20[0-9])" + - enum: [ sdc2_clk, sdc2_cmd, sdc2_data, ufs_reset ] + minItems: 1 + maxItems: 36 + function: + description: + Specify the alternative function to be configured for the + specified pins. Functions are only valid for gpio pins. + enum: [gpio, aon_cam, atest_char, atest_char0, atest_char1, atest_char2, atest_char3, + atest_usb0, atest_usb00, atest_usb01, atest_usb02, atest_usb03, audio_ref, cam_mclk, + cci_async, cci_i2c, cci_timer0, cci_timer1, cci_timer2, cci_timer3, cci_timer4, + cmu_rng0, cmu_rng1, cmu_rng2, cmu_rng3, coex_uart1, coex_uart2, cri_trng, cri_trng0, + cri_trng1, dbg_out, ddr_bist, ddr_pxi0, ddr_pxi1, ddr_pxi2, ddr_pxi3, dp_hot, gcc_gp1, + gcc_gp2, gcc_gp3, ibi_i3c, jitter_bist, mdp_vsync, mdp_vsync0, mdp_vsync1, mdp_vsync2, + mdp_vsync3, mi2s0_data0, mi2s0_data1, mi2s0_sck, mi2s0_ws, mi2s2_data0, mi2s2_data1, + mi2s2_sck, mi2s2_ws, mss_grfc0, mss_grfc1, mss_grfc10, mss_grfc11, mss_grfc12, + mss_grfc2, mss_grfc3, mss_grfc4, mss_grfc5, mss_grfc6, mss_grfc7, mss_grfc8, mss_grfc9, + nav_0, nav_1, nav_2, pcie0_clkreqn, pcie1_clkreqn, phase_flag0, phase_flag1, + phase_flag10, phase_flag11, phase_flag12, phase_flag13, phase_flag14, phase_flag15, + phase_flag16, phase_flag17, phase_flag18, phase_flag19, phase_flag2, phase_flag20, + phase_flag21, phase_flag22, phase_flag23, phase_flag24, phase_flag25, phase_flag26, + phase_flag27, phase_flag28, phase_flag29, phase_flag3, phase_flag30, phase_flag31, + phase_flag4, phase_flag5, phase_flag6, phase_flag7, phase_flag8, phase_flag9, pll_bist, + pll_clk, pri_mi2s, prng_rosc0, prng_rosc1, prng_rosc2, prng_rosc3, qdss_cti, qdss_gpio, + qdss_gpio0, qdss_gpio1, qdss_gpio10, qdss_gpio11, qdss_gpio12, qdss_gpio13, qdss_gpio14, + qdss_gpio15, qdss_gpio2, qdss_gpio3, qdss_gpio4, qdss_gpio5, qdss_gpio6, qdss_gpio7, + qdss_gpio8, qdss_gpio9, qlink0_enable, qlink0_request, qlink0_wmss, qlink1_enable, + qlink1_request, qlink1_wmss, qlink2_enable, qlink2_request, qlink2_wmss, qspi0, qspi1, + qspi2, qspi3, qspi_clk, qspi_cs, qup0, qup1, qup10, qup11, qup12, qup13, qup14, qup15, + qup16, qup17, qup18, qup19, qup2, qup20, qup21, qup3, qup4, qup5, qup6, qup7, qup8, + qup9, qup_l4, qup_l5, qup_l6, sd_write, sdc40, sdc41, sdc42, sdc43, sdc4_clk, sdc4_cmd, + sec_mi2s, tb_trig, tgu_ch0, tgu_ch1, tgu_ch2, tgu_ch3, tmess_prng0, tmess_prng1, + tmess_prng2, tmess_prng3, tsense_pwm1, tsense_pwm2, uim0_clk, uim0_data, uim0_present, + uim0_reset, uim1_clk, uim1_data, uim1_present, uim1_reset, usb2phy_ac, usb_phy, vfr_0, + vfr_1, vsense_trigger] + drive-strength: + enum: [2, 4, 6, 8, 10, 12, 14, 16] + default: 2 + description: + Selects the drive strength for the specified pins, in mA. + bias-pull-down: true + bias-pull-up: true + bias-disable: true + output-high: true + output-low: true + required: + - pins + - function + additionalProperties: false + +examples: + - | + tlmm: pinctrl@03000000 { + compatible = "qcom,kalama-vm-pinctrl"; + reg = <0x03000000 0xdc2000>; + interrupts-extended = <0 208 0>; + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <2>; + gpios = /bits/ 16 <0 1>; + }; diff --git a/bindings/virt/gunyah/qcom,gh-vm-loader-sec.yaml b/bindings/virt/gunyah/qcom,gh-vm-loader-sec.yaml new file mode 100644 index 00000000..5ca1c904 --- /dev/null +++ b/bindings/virt/gunyah/qcom,gh-vm-loader-sec.yaml @@ -0,0 +1,36 @@ +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/virt/gunyah/qcom,gh-vm-loader-sec.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Gunyah Secure Guest VM Loader + +maintainers: + - Prakruthi Deepak Heragu + - Murali Nalajala + +properties: + compatible: + const: qcom,gh-vm-loader-sec + + qcom,no-shutdown: + description: Specify if this is a critical VM that doesn't support shutdown + + image_to_be_loaded: + $ref: /schemas/types.yaml#/definitions/string + +required: + - compatible + - qcom,pas-id + - qcom,firmware-name + - memory-region + +examples: + - |+ + qcom,gh_vm_loader_sec { + compatible = "qcom,gh-vm-loader-sec"; + qcom,pas-id = <28>; + qcom,firmware-name = "trustedvm"; + memory-region = <&trust_ui_vm_mem>; + }; +...