Documentation/devicetree/bindings/pinctrl/nvidia,tegra238-pinmux.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/pinctrl/nvidia,tegra238-pinmux.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/pinctrl/nvidia,tegra238-pinmux.yaml- Extension
.yaml- Size
- 11910 bytes
- Lines
- 220
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: configuration, schema, or hardware description
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
dt-bindings/pinctrl/pinctrl-tegra.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/pinctrl/nvidia,tegra238-pinmux.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: NVIDIA Tegra238 Pinmux Controller
maintainers:
- Thierry Reding <thierry.reding@gmail.com>
- Jon Hunter <jonathanh@nvidia.com>
properties:
compatible:
const: nvidia,tegra238-pinmux
reg:
maxItems: 1
patternProperties:
"^pinmux(-[a-z0-9-]+)?$":
type: object
# pin groups
additionalProperties:
$ref: nvidia,tegra238-pinmux-common.yaml
properties:
nvidia,pins:
items:
enum: [ gpu_pwr_req_pa0, gp_pwm5_pa1, gp_pwm6_pa2, spi3_sck_pa3,
spi3_miso_pa4, spi3_mosi_pa5, spi3_cs0_pa6, spi3_cs1_pa7,
spi1_sck_pb0, spi1_miso_pb1, spi1_mosi_pb2, spi1_cs0_pb3,
spi1_cs1_pb4, pwr_i2c_scl_pc0, pwr_i2c_sda_pc1,
extperiph1_clk_pc2, extperiph2_clk_pc3, cam_i2c_scl_pc4,
cam_i2c_sda_pc5, soc_gpio23_pc6, soc_gpio24_pc7,
soc_gpio27_pd0, soc_gpio55_pd1, soc_gpio29_pd2,
soc_gpio33_pd3, soc_gpio32_pd4, soc_gpio35_pd5,
soc_gpio37_pd6, soc_gpio56_pd7, uart1_tx_pe0,
uart1_rx_pe1, uart1_rts_pe2, uart1_cts_pe3,
soc_gpio13_pf0, soc_gpio14_pf1, soc_gpio15_pf2,
soc_gpio16_pf3, soc_gpio17_pf4, soc_gpio18_pf5,
soc_gpio20_pf6, soc_gpio21_pf7, soc_gpio22_pg0,
soc_gpio06_pg1, uart4_tx_pg2, uart4_rx_pg3,
uart4_rts_pg4, uart4_cts_pg5, soc_gpio41_pg6,
soc_gpio42_pg7, soc_gpio43_ph0, soc_gpio44_ph1,
gen1_i2c_scl_ph2, gen1_i2c_sda_ph3, cpu_pwr_req_ph4,
soc_gpio07_ph5, dap3_clk_pj0, dap3_dout_pj1,
dap3_din_pj2, dap3_fs_pj3, soc_gpio57_pj4,
soc_gpio58_pj5, soc_gpio59_pj6, soc_gpio60_pj7,
soc_gpio45_pk0, soc_gpio46_pk1, soc_gpio47_pk2,
soc_gpio48_pk3, qspi0_sck_pl0, qspi0_io0_pl1,
qspi0_io1_pl2, qspi0_cs_n_pl3, soc_gpio152_pl4,
soc_gpio153_pl5, soc_gpio154_pl6, soc_gpio155_pl7,
soc_gpio156_pm0, soc_gpio157_pm1, soc_gpio158_pm2,
soc_gpio159_pm3, soc_gpio160_pm4, soc_gpio161_pm5,
soc_gpio162_pm6, uart7_tx_pm7, uart7_rx_pn0,
uart7_rts_pn1, uart7_cts_pn2, soc_gpio167_pp0,
soc_gpio168_pp1, soc_gpio169_pp2, soc_gpio170_pp3,
dap4_sclk_pp4, dap4_dout_pp5, dap4_din_pp6, dap4_fs_pp7,
soc_gpio171_pq0, soc_gpio172_pq1, soc_gpio173_pq2,
soc_gpio61_pr0, soc_gpio62_pr1, soc_gpio63_pr2,
soc_gpio64_pr3, soc_gpio65_pr4, soc_gpio66_pr5,
soc_gpio67_pr6, soc_gpio68_pr7, gen4_i2c_scl_ps0,
gen4_i2c_sda_ps1, soc_gpio75_ps2, gen7_i2c_scl_ps3,
gen7_i2c_sda_ps4, soc_gpio78_ps5, gen9_i2c_scl_ps6,
gen9_i2c_sda_ps7, soc_gpio81_pt0, soc_gpio36_pt1,
soc_gpio53_pt2, soc_gpio38_pt3, soc_gpio40_pt4,
soc_gpio34_pt5, usb_vbus_en0_pt6, usb_vbus_en1_pt7,
sdmmc1_clk_pu0, sdmmc1_cmd_pu1, sdmmc1_dat0_pu2,
Annotation
- Immediate include surface: `dt-bindings/pinctrl/pinctrl-tegra.h`.
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.