drivers/pinctrl/mediatek/pinctrl-mtk-mt8135.h
Source file repositories/reference/linux-study-clean/drivers/pinctrl/mediatek/pinctrl-mtk-mt8135.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/pinctrl/mediatek/pinctrl-mtk-mt8135.h- Extension
.h- Size
- 51338 bytes
- Lines
- 1904
- Domain
- Driver Families
- Bucket
- drivers/pinctrl
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/pinctrl/pinctrl.hpinctrl-mtk-common.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#ifndef __PINCTRL_MTK_MT8135_H
#define __PINCTRL_MTK_MT8135_H
#include <linux/pinctrl/pinctrl.h>
#include "pinctrl-mtk-common.h"
static const struct mtk_desc_pin mtk_pins_mt8135[] = {
MTK_PIN(PINCTRL_PIN(0, "MSDC0_DAT7"),
"D21", "mt8135",
MTK_EINT_FUNCTION(2, 49),
MTK_FUNCTION(0, "GPIO0"),
MTK_FUNCTION(1, "MSDC0_DAT7"),
MTK_FUNCTION(2, "EINT49"),
MTK_FUNCTION(3, "I2SOUT_DAT"),
MTK_FUNCTION(4, "DAC_DAT_OUT"),
MTK_FUNCTION(5, "PCM1_DO"),
MTK_FUNCTION(6, "SPI1_MO"),
MTK_FUNCTION(7, "NALE")
),
MTK_PIN(PINCTRL_PIN(1, "MSDC0_DAT6"),
"D22", "mt8135",
MTK_EINT_FUNCTION(2, 48),
MTK_FUNCTION(0, "GPIO1"),
MTK_FUNCTION(1, "MSDC0_DAT6"),
MTK_FUNCTION(2, "EINT48"),
MTK_FUNCTION(3, "I2SIN_WS"),
MTK_FUNCTION(4, "DAC_WS"),
MTK_FUNCTION(5, "PCM1_WS"),
MTK_FUNCTION(6, "SPI1_CSN"),
MTK_FUNCTION(7, "NCLE")
),
MTK_PIN(PINCTRL_PIN(2, "MSDC0_DAT5"),
"E22", "mt8135",
MTK_EINT_FUNCTION(2, 47),
MTK_FUNCTION(0, "GPIO2"),
MTK_FUNCTION(1, "MSDC0_DAT5"),
MTK_FUNCTION(2, "EINT47"),
MTK_FUNCTION(3, "I2SIN_CK"),
MTK_FUNCTION(4, "DAC_CK"),
MTK_FUNCTION(5, "PCM1_CK"),
MTK_FUNCTION(6, "SPI1_CLK"),
MTK_FUNCTION(7, "NLD4")
),
MTK_PIN(PINCTRL_PIN(3, "MSDC0_DAT4"),
"F21", "mt8135",
MTK_EINT_FUNCTION(2, 46),
MTK_FUNCTION(0, "GPIO3"),
MTK_FUNCTION(1, "MSDC0_DAT4"),
MTK_FUNCTION(2, "EINT46"),
MTK_FUNCTION(3, "A_FUNC_CK"),
MTK_FUNCTION(6, "LSCE1B_2X"),
MTK_FUNCTION(7, "NLD5")
),
MTK_PIN(PINCTRL_PIN(4, "MSDC0_CMD"),
"F20", "mt8135",
MTK_EINT_FUNCTION(2, 41),
MTK_FUNCTION(0, "GPIO4"),
MTK_FUNCTION(1, "MSDC0_CMD"),
MTK_FUNCTION(2, "EINT41"),
MTK_FUNCTION(3, "A_FUNC_DOUT[0]"),
MTK_FUNCTION(5, "USB_TEST_IO[0]"),
MTK_FUNCTION(6, "LRSTB_2X"),
MTK_FUNCTION(7, "NRNB")
),
MTK_PIN(PINCTRL_PIN(5, "MSDC0_CLK"),
"G18", "mt8135",
MTK_EINT_FUNCTION(2, 40),
MTK_FUNCTION(0, "GPIO5"),
MTK_FUNCTION(1, "MSDC0_CLK"),
MTK_FUNCTION(2, "EINT40"),
MTK_FUNCTION(3, "A_FUNC_DOUT[1]"),
MTK_FUNCTION(5, "USB_TEST_IO[1]"),
MTK_FUNCTION(6, "LPTE"),
MTK_FUNCTION(7, "NREB")
),
MTK_PIN(PINCTRL_PIN(6, "MSDC0_DAT3"),
"G21", "mt8135",
MTK_EINT_FUNCTION(2, 45),
MTK_FUNCTION(0, "GPIO6"),
MTK_FUNCTION(1, "MSDC0_DAT3"),
MTK_FUNCTION(2, "EINT45"),
MTK_FUNCTION(3, "A_FUNC_DOUT[2]"),
MTK_FUNCTION(5, "USB_TEST_IO[2]"),
MTK_FUNCTION(6, "LSCE0B_2X"),
MTK_FUNCTION(7, "NLD7")
),
MTK_PIN(PINCTRL_PIN(7, "MSDC0_DAT2"),
"E21", "mt8135",
MTK_EINT_FUNCTION(2, 44),
MTK_FUNCTION(0, "GPIO7"),
Annotation
- Immediate include surface: `linux/pinctrl/pinctrl.h`, `pinctrl-mtk-common.h`.
- Atlas domain: Driver Families / drivers/pinctrl.
- Implementation status: source implementation candidate.
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.