drivers/pinctrl/tegra/Makefile

File Facts

System

Linux kernel

Corpus path

drivers/pinctrl/tegra/Makefile

Extension

[no extension]

Size

676 bytes

Lines

14

Domain

Driver Families

Bucket

drivers/pinctrl

Inferred role

Driver Families: build/configuration rule

Status

atlas-only

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.

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
obj-$(CONFIG_PINCTRL_TEGRA)		+= pinctrl-tegra.o
obj-$(CONFIG_PINCTRL_TEGRA20)		+= pinctrl-tegra20.o
obj-$(CONFIG_PINCTRL_TEGRA30)		+= pinctrl-tegra30.o
obj-$(CONFIG_PINCTRL_TEGRA114)		+= pinctrl-tegra114.o
obj-$(CONFIG_PINCTRL_TEGRA124)		+= pinctrl-tegra124.o
obj-$(CONFIG_PINCTRL_TEGRA210)		+= pinctrl-tegra210.o
obj-$(CONFIG_PINCTRL_TEGRA186)		+= pinctrl-tegra186.o
obj-$(CONFIG_PINCTRL_TEGRA194)		+= pinctrl-tegra194.o
obj-$(CONFIG_PINCTRL_TEGRA234)		+= pinctrl-tegra234.o
obj-$(CONFIG_PINCTRL_TEGRA238)		+= pinctrl-tegra238.o
obj-$(CONFIG_PINCTRL_TEGRA264)		+= pinctrl-tegra264.o
obj-$(CONFIG_PINCTRL_TEGRA_XUSB)	+= pinctrl-tegra-xusb.o

Annotation

• Atlas domain: Driver Families / drivers/pinctrl.
• 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.