# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2 --- $id: http://devicetree.org/schemas/soc/tegra/nvidia,tegra20-pmc.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# title: Tegra Power Management Controller (PMC) maintainers: - Thierry Reding - Jonathan Hunter properties: compatible: enum: - nvidia,tegra20-pmc - nvidia,tegra30-pmc - nvidia,tegra114-pmc - nvidia,tegra124-pmc - nvidia,tegra210-pmc reg: maxItems: 1 clock-names: items: # Tegra clock of the same name - const: pclk # 32 KHz clock input - const: clk32k_in clocks: maxItems: 2 '#clock-cells': const: 1 description: | Tegra PMC has clk_out_1, clk_out_2, and clk_out_3. PMC also has blink control which allows 32Khz clock output to Tegra blink pad. Consumer of PMC clock should specify the desired clock by having the clock ID in its "clocks" phandle cell with PMC clock provider. See include/dt-bindings/soc/tegra-pmc.h for the list of Tegra PMC clock IDs. '#interrupt-cells': const: 2 description: Specifies number of cells needed to encode an interrupt source. interrupt-controller: true nvidia,invert-interrupt: $ref: /schemas/types.yaml#/definitions/flag description: Inverts the PMU interrupt signal. The PMU is an external Power Management Unit, whose interrupt output signal is fed into the PMC. This signal is optionally inverted, and then fed into the ARM GIC. The PMC is not involved in the detection or handling of this interrupt signal, merely its inversion. nvidia,core-power-req-active-high: $ref: /schemas/types.yaml#/definitions/flag description: core power request active-high nvidia,sys-clock-req-active-high: $ref: /schemas/types.yaml#/definitions/flag description: system clock request active-high nvidia,combined-power-req: $ref: /schemas/types.yaml#/definitions/flag description: combined power request for CPU and core nvidia,cpu-pwr-good-en: $ref: /schemas/types.yaml#/definitions/flag description: CPU power good signal from external PMIC to PMC is enabled nvidia,suspend-mode: $ref: /schemas/types.yaml#/definitions/uint32 description: the suspend mode that the platform should use oneOf: - description: LP0, CPU + Core voltage off and DRAM in self-refresh const: 0 - description: LP1, CPU voltage off and DRAM in self-refresh const: 1 - description: LP2, CPU voltage off const: 2 nvidia,cpu-pwr-good-time: $ref: /schemas/types.yaml#/definitions/uint32 description: CPU power good time in microseconds nvidia,cpu-pwr-off-time: $ref: /schemas/types.yaml#/definitions/uint32 description: CPU power off time in microseconds nvidia,core-pwr-good-time: $ref: /schemas/types.yaml#/definitions/uint32-array description: core power good time in microseconds items: - description: oscillator stable time - description: power stable time nvidia,core-pwr-off-time: $ref: /schemas/types.yaml#/definitions/uint32 description: core power off time in microseconds nvidia,lp0-vec: $ref: /schemas/types.yaml#/definitions/uint32-array description: | Starting address and length of LP0 vector. The LP0 vector contains the warm boot code that is executed by AVP when resuming from the LP0 state. The AVP (Audio-Video Processor) is an ARM7 processor and always being the first boot processor when chip is power on or resume from deep sleep mode. When the system is resumed from the deep sleep mode, the warm boot code will restore some PLLs, clocks and then brings up CPU0 for resuming the system. items: - description: starting address of LP0 vector - description: length of LP0 vector core-supply: description: phandle to voltage regulator connected to the SoC core power rail core-domain: type: object description: The vast majority of hardware blocks of Tegra SoC belong to a core power domain, which has a dedicated voltage rail that powers the blocks. additionalProperties: false properties: operating-points-v2: description: Should contain level, voltages and opp-supported-hw property. The supported-hw is a bitfield indicating SoC speedo or process ID mask. "#power-domain-cells": const: 0 required: - operating-points-v2 - "#power-domain-cells" i2c-thermtrip: type: object description: On Tegra30, Tegra114 and Tegra124 if i2c-thermtrip subnode exists, hardware-triggered thermal reset will be enabled. additionalProperties: false properties: nvidia,i2c-controller-id: $ref: /schemas/types.yaml#/definitions/uint32 description: ID of I2C controller to send poweroff command to PMU. Valid values are described in section 9.2.148 "APBDEV_PMC_SCRATCH53_0" of the Tegra K1 Technical Reference Manual. nvidia,bus-addr: $ref: /schemas/types.yaml#/definitions/uint32 description: bus address of the PMU on the I2C bus nvidia,reg-addr: $ref: /schemas/types.yaml#/definitions/uint32 description: PMU I2C register address to issue poweroff command nvidia,reg-data: $ref: /schemas/types.yaml#/definitions/uint32 description: power-off command to write to PMU nvidia,pinmux-id: $ref: /schemas/types.yaml#/definitions/uint32 description: Pinmux used by the hardware when issuing power-off command. Defaults to 0. Valid values are described in section 12.5.2 "Pinmux Support" of the Tegra4 Technical Reference Manual. required: - nvidia,i2c-controller-id - nvidia,bus-addr - nvidia,reg-addr - nvidia,reg-data powergates: type: object additionalProperties: false description: | This node contains a hierarchy of power domain nodes, which should match the powergates on the Tegra SoC. Each powergate node represents a power- domain on the Tegra SoC that can be power-gated by the Tegra PMC. Hardware blocks belonging to a power domain should contain "power-domains" property that is a phandle pointing to corresponding powergate node. The name of the powergate node should be one of the below. Note that not every powergate is applicable to all Tegra devices and the following list shows which powergates are applicable to which devices. Please refer to Tegra TRM for mode details on the powergate nodes to use for each power-gate block inside Tegra. Name Description Devices Applicable -------------------------------------------------------------- 3d 3D Graphics Tegra20/114/124/210 3d0 3D Graphics 0 Tegra30 3d1 3D Graphics 1 Tegra30 aud Audio Tegra210 dfd Debug Tegra210 dis Display A Tegra114/124/210 disb Display B Tegra114/124/210 heg 2D Graphics Tegra30/114/124/210 iram Internal RAM Tegra124/210 mpe MPEG Encode All nvdec NVIDIA Video Decode Engine Tegra210 nvjpg NVIDIA JPEG Engine Tegra210 pcie PCIE Tegra20/30/124/210 sata SATA Tegra30/124/210 sor Display interfaces Tegra124/210 ve2 Video Encode Engine 2 Tegra210 venc Video Encode Engine All vdec Video Decode Engine Tegra20/30/114/124 vic Video Imaging Compositor Tegra124/210 xusba USB Partition A Tegra114/124/210 xusbb USB Partition B Tegra114/124/210 xusbc USB Partition C Tegra114/124/210 patternProperties: "^[a-z0-9]+$": type: object additionalProperties: false properties: clocks: minItems: 1 maxItems: 10 resets: minItems: 1 maxItems: 8 power-domains: maxItems: 1 '#power-domain-cells': const: 0 description: Must be 0. required: - clocks - resets - '#power-domain-cells' pinmux: type: object additionalProperties: type: object description: | This is a pad configuration node. On Tegra SoCs a pad is a set of pins which are configured as a group. The pin grouping is a fixed attribute of the hardware. The PMC can be used to set pad power state and signaling voltage. A pad can be either in active or power down mode. The support for power state and signaling voltage configuration varies depending on the pad in question. 3.3V and 1.8V signaling voltages are supported on pins where software controllable signaling voltage switching is available. The pad configuration state nodes are placed under the pmc node and they are referred to by the pinctrl client properties. For more information see: Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt The pad name should be used as the value of the pins property in pin configuration nodes. The following pads are present on Tegra124 and Tegra132: audio, bb, cam, comp, csia, csb, cse, dsi, dsib, dsic, dsid, hdmi, hsic, hv, lvds, mipi-bias, nand, pex-bias, pex-clk1, pex-clk2, pex-cntrl, sdmmc1, sdmmc3, sdmmc4, sys_ddc, uart, usb0, usb1, usb2, usb_bias The following pads are present on Tegra210: audio, audio-hv, cam, csia, csib, csic, csid, csie, csif, dbg, debug-nonao, dmic, dp, dsi, dsib, dsic, dsid, emmc, emmc2, gpio, hdmi, hsic, lvds, mipi-bias, pex-bias, pex-clk1, pex-clk2, pex-cntrl, sdmmc1, sdmmc3, spi, spi-hv, uart, usb0, usb1, usb2, usb3, usb-bias additionalProperties: false properties: pins: $ref: /schemas/types.yaml#/definitions/string-array description: Must contain name of the pad(s) to be configured. low-power-enable: $ref: /schemas/types.yaml#/definitions/flag description: Configure the pad into power down mode. low-power-disable: $ref: /schemas/types.yaml#/definitions/flag description: Configure the pad into active mode. power-source: $ref: /schemas/types.yaml#/definitions/uint32 description: | Must contain either TEGRA_IO_PAD_VOLTAGE_1V8 or TEGRA_IO_PAD_VOLTAGE_3V3 to select between signaling voltages. The values are defined in: include/dt-bindings/pinctrl/pinctrl-tegra-io-pad.h Power state can be configured on all Tegra124 and Tegra132 pads. None of the Tegra124 or Tegra132 pads support signaling voltage switching. All of the listed Tegra210 pads except pex-cntrl support power state configuration. Signaling voltage switching is supported on the following Tegra210 pads: audio, audio-hv, cam, dbg, dmic, gpio, pex-cntrl, sdmmc1, sdmmc3, spi, spi-hv, uart required: - pins required: - compatible - reg - clock-names - clocks - '#clock-cells' allOf: - if: properties: compatible: contains: const: nvidia,tegra124-pmc then: properties: pinmux: additionalProperties: type: object properties: pins: items: enum: [ audio, bb, cam, comp, csia, csb, cse, dsi, dsib, dsic, dsid, hdmi, hsic, hv, lvds, mipi-bias, nand, pex-bias, pex-clk1, pex-clk2, pex-cntrl, sdmmc1, sdmmc3, sdmmc4, sys_ddc, uart, usb0, usb1, usb2, usb_bias ] - if: properties: compatible: contains: const: nvidia,tegra210-pmc then: properties: pinmux: additionalProperties: type: object properties: pins: items: enum: [ audio, audio-hv, cam, csia, csib, csic, csid, csie, csif, dbg, debug-nonao, dmic, dp, dsi, dsib, dsic, dsid, emmc, emmc2, gpio, hdmi, hsic, lvds, mipi-bias, pex-bias, pex-clk1, pex-clk2, pex-cntrl, sdmmc1, sdmmc3, spi, spi-hv, uart, usb0, usb1, usb2, usb3, usb-bias ] additionalProperties: false dependencies: "nvidia,suspend-mode": ["nvidia,core-pwr-off-time", "nvidia,cpu-pwr-off-time"] "nvidia,core-pwr-off-time": ["nvidia,core-pwr-good-time"] "nvidia,cpu-pwr-off-time": ["nvidia,cpu-pwr-good-time"] examples: - | #include #include #include pmc@7000e400 { compatible = "nvidia,tegra210-pmc"; reg = <0x7000e400 0x400>; core-supply = <®ulator>; clocks = <&tegra_car TEGRA210_CLK_PCLK>, <&clk32k_in>; clock-names = "pclk", "clk32k_in"; #clock-cells = <1>; nvidia,invert-interrupt; nvidia,suspend-mode = <0>; nvidia,cpu-pwr-good-time = <0>; nvidia,cpu-pwr-off-time = <0>; nvidia,core-pwr-good-time = <4587 3876>; nvidia,core-pwr-off-time = <39065>; nvidia,core-power-req-active-high; nvidia,sys-clock-req-active-high; pd_core: core-domain { operating-points-v2 = <&core_opp_table>; #power-domain-cells = <0>; }; powergates { pd_audio: aud { clocks = <&tegra_car TEGRA210_CLK_APE>, <&tegra_car TEGRA210_CLK_APB2APE>; resets = <&tegra_car 198>; power-domains = <&pd_core>; #power-domain-cells = <0>; }; pd_xusbss: xusba { clocks = <&tegra_car TEGRA210_CLK_XUSB_SS>; resets = <&tegra_car TEGRA210_CLK_XUSB_SS>; power-domains = <&pd_core>; #power-domain-cells = <0>; }; }; };