drivers/nvmem/layouts/Kconfig
Source file repositories/reference/linux-study-clean/drivers/nvmem/layouts/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/nvmem/layouts/Kconfig- Extension
[no extension]- Size
- 897 bytes
- Lines
- 43
- Domain
- Driver Families
- Bucket
- drivers/nvmem
- 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
config NVMEM_LAYOUTS
bool
depends on OF
if NVMEM_LAYOUTS
menu "Layout Types"
config NVMEM_LAYOUT_SL28_VPD
tristate "Kontron sl28 VPD layout support"
select CRC8
help
Say Y here if you want to support the VPD layout of the Kontron
SMARC-sAL28 boards.
If unsure, say N.
config NVMEM_LAYOUT_ONIE_TLV
tristate "ONIE tlv support"
select CRC32
help
Say Y here if you want to support the Open Compute Project ONIE
Type-Length-Value standard table.
If unsure, say N.
config NVMEM_LAYOUT_U_BOOT_ENV
tristate "U-Boot environment variables layout"
select CRC32
select GENERIC_NET_UTILS
help
U-Boot stores its setup as environment variables. This driver adds
support for verifying & exporting such data. It also exposes variables
as NVMEM cells so they can be referenced by other drivers.
If unsure, say N.
endmenu
endif
Annotation
- Atlas domain: Driver Families / drivers/nvmem.
- 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.