Documentation/devicetree/bindings/pinctrl/realtek,rtd1315e-pinctrl.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/pinctrl/realtek,rtd1315e-pinctrl.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/pinctrl/realtek,rtd1315e-pinctrl.yaml- Extension
.yaml- Size
- 7168 bytes
- Lines
- 192
- 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
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
# Copyright 2023 Realtek Semiconductor Corporation
%YAML 1.2
---
$id: http://devicetree.org/schemas/pinctrl/realtek,rtd1315e-pinctrl.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Realtek DHC RTD1315E Pin Controller
maintainers:
- TY Chang <tychang@realtek.com>
description:
The Realtek DHC RTD1315E is a high-definition media processor SoC. The
RTD1315E pin controller is used to control pin function, pull up/down
resistor, drive strength, schmitt trigger and power source.
properties:
compatible:
const: realtek,rtd1315e-pinctrl
reg:
maxItems: 1
patternProperties:
'-pins$':
type: object
allOf:
- $ref: pincfg-node.yaml#
- $ref: pinmux-node.yaml#
properties:
pins:
items:
enum: [ gpio_0, gpio_1, emmc_rst_n, emmc_dd_sb, emmc_clk, emmc_cmd,
gpio_6, gpio_7, gpio_8, gpio_9, gpio_10, gpio_11, gpio_12,
gpio_13, gpio_14, gpio_15, gpio_16, gpio_17, gpio_18, gpio_19,
gpio_20, emmc_data_0, emmc_data_1, emmc_data_2, usb_cc2, gpio_25,
gpio_26, gpio_27, gpio_28, gpio_29, gpio_30, gpio_31, gpio_32,
gpio_33, gpio_34, gpio_35, hif_data, hif_en, hif_rdy, hif_clk,
gpio_dummy_40, gpio_dummy_41, gpio_dummy_42, gpio_dummy_43,
gpio_dummy_44, gpio_dummy_45, gpio_46, gpio_47, gpio_48, gpio_49,
gpio_50, usb_cc1, emmc_data_3, emmc_data_4, ir_rx, ur0_rx, ur0_tx,
gpio_57, gpio_58, gpio_59, gpio_60, gpio_61, gpio_62, gpio_dummy_63,
gpio_dummy_64, gpio_dummy_65, gpio_66, gpio_67, gpio_68, gpio_69,
gpio_70, gpio_71, gpio_72, gpio_dummy_73, emmc_data_5, emmc_data_6,
emmc_data_7, gpio_dummy_77, gpio_78, gpio_79, gpio_80, gpio_81,
ur2_loc, gspi_loc, hi_width, sf_en, arm_trace_dbg_en,
ejtag_aucpu_loc, ejtag_acpu_loc, ejtag_vcpu_loc, ejtag_scpu_loc,
dmic_loc, vtc_dmic_loc, vtc_tdm_loc, vtc_i2si_loc, tdm_ai_loc,
ai_loc, spdif_loc, hif_en_loc, scan_switch, wd_rset, boot_sel,
reset_n, testmode ]
function:
enum: [ gpio, nf, emmc, ao, gspi_loc0, gspi_loc1, uart0, uart1,
uart2_loc0, uart2_loc1, i2c0, i2c1, i2c4, i2c5, pcie1,
etn_led, etn_phy, spi, pwm0_loc0, pwm0_loc1, pwm1_loc0,
pwm1_loc1, pwm2_loc0, pwm2_loc1, pwm3_loc0, pwm3_loc1,
spdif_optical_loc0, spdif_optical_loc1, usb_cc1, usb_cc2,
sd, dmic_loc0, dmic_loc1, ai_loc0, ai_loc1, tdm_ai_loc0,
tdm_ai_loc1, hi_loc0, hi_m, vtc_i2so, vtc_i2si_loc0,
vtc_i2si_loc1, vtc_dmic_loc0, vtc_dmic_loc1, vtc_tdm_loc0,
vtc_tdm_loc1, dc_fan, pll_test_loc0, pll_test_loc1,
ir_rx, uart2_disable, gspi_disable, hi_width_disable,
hi_width_1bit, sf_disable, sf_enable, scpu_ejtag_loc0,
scpu_ejtag_loc1, scpu_ejtag_loc2, scpu_ejtag_loc3,
acpu_ejtag_loc0, acpu_ejtag_loc1, acpu_ejtag_loc2,
vcpu_ejtag_loc0, vcpu_ejtag_loc1, vcpu_ejtag_loc2,
aucpu_ejtag_loc0, aucpu_ejtag_loc1, aucpu_ejtag_loc2,
gpu_ejtag, iso_tristate, dbg_out0, dbg_out1, standby_dbg,
Annotation
- 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.