Documentation/devicetree/bindings/pinctrl/realtek,rtd1625-pinctrl.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/pinctrl/realtek,rtd1625-pinctrl.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/pinctrl/realtek,rtd1625-pinctrl.yaml- Extension
.yaml- Size
- 10435 bytes
- Lines
- 261
- 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 2025 Realtek Semiconductor Corporation
%YAML 1.2
---
$id: http://devicetree.org/schemas/pinctrl/realtek,rtd1625-pinctrl.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: Realtek DHC RTD1625 Pin Controller
maintainers:
- Tzuyi Chang <tychang@realtek.com>
- Yu-Chun Lin <eleanor.lin@realtek.com>
description:
The Realtek DHC RTD1625 is a high-definition media processor SoC. The
RTD1625 pin controller is used to control pin function, pull-up/down
resistors, drive strength, slew rate, Schmitt trigger, power source
(I/O output voltage), input threshold domain selection and a higher-VIL mode.
properties:
compatible:
items:
- enum:
- realtek,rtd1625-iso-pinctrl
- realtek,rtd1625-main2-pinctrl
- realtek,rtd1625-isom-pinctrl
- realtek,rtd1625-ve4-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, gpio_2, gpio_3, gpio_4, gpio_5, 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,
gpio_21, gpio_22, gpio_23, gpio_24, gpio_25, gpio_28, gpio_29,
gpio_30, gpio_31, gpio_32, gpio_33, gpio_34, gpio_35, gpio_40,
gpio_41, gpio_42, gpio_43, gpio_44, gpio_45, gpio_46, gpio_47,
gpio_48, gpio_49, gpio_50, gpio_51, gpio_52, gpio_53, gpio_54,
gpio_55, gpio_56, gpio_57, gpio_58, gpio_59, gpio_60, gpio_61,
gpio_62, gpio_63, gpio_64, gpio_65, gpio_66, gpio_67, gpio_80,
gpio_81, gpio_82, gpio_83, gpio_84, gpio_85, gpio_86, gpio_87,
gpio_88, gpio_89, gpio_90, gpio_91, gpio_92, gpio_93, gpio_94,
gpio_95, gpio_96, gpio_97, gpio_98, gpio_99, gpio_100,
gpio_101, gpio_102, gpio_103, gpio_104, gpio_105, gpio_106,
gpio_107, gpio_108, gpio_109, gpio_110, gpio_111, gpio_112,
gpio_128, gpio_129, gpio_130, gpio_131, gpio_132, gpio_133,
gpio_134, gpio_135, gpio_136, gpio_137, gpio_138, gpio_139,
gpio_140, gpio_141, gpio_142, gpio_143, gpio_144, gpio_145,
gpio_146, gpio_147, gpio_148, gpio_149, gpio_150, gpio_151,
gpio_152, gpio_153, gpio_154, gpio_155, gpio_156, gpio_157,
gpio_158, gpio_159, gpio_160, gpio_161, gpio_162, gpio_163,
gpio_164, gpio_165, ai_i2s1_loc, ao_i2s1_loc, arm_trace_dbg_en,
csi_vdsel, ejtag_acpu_loc, ejtag_aucpu0_loc, ejtag_aucpu1_loc,
ejtag_pcpu_loc, ejtag_scpu_loc, ejtag_ve2_loc, emmc_clk,
emmc_cmd, emmc_data_0, emmc_data_1, emmc_data_2, emmc_data_3,
emmc_data_4, emmc_data_5, emmc_data_6, emmc_data_7,
emmc_dd_sb, emmc_rst_n, etn_phy_loc, hif_clk, hif_data,
hif_en, hif_rdy, hi_width, i2c6_loc, ir_rx_loc, rgmii_vdsel,
sf_en, spdif_in_mode, spdif_loc, uart0_loc, usb_cc1, usb_cc2,
ve4_uart_loc]
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.