drivers/mtd/spi-nor/esmt.c
Source file repositories/reference/linux-study-clean/drivers/mtd/spi-nor/esmt.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/mtd/spi-nor/esmt.c- Extension
.c- Size
- 825 bytes
- Lines
- 38
- Domain
- Driver Families
- Bucket
- drivers/mtd
- 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/mtd/spi-nor.hcore.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
/*
* Copyright (C) 2005, Intec Automation Inc.
* Copyright (C) 2014, Freescale Semiconductor, Inc.
*/
#include <linux/mtd/spi-nor.h>
#include "core.h"
static const struct flash_info esmt_nor_parts[] = {
{
.id = SNOR_ID(0x8c, 0x20, 0x16),
.name = "f25l32pa",
.size = SZ_4M,
.flags = SPI_NOR_HAS_LOCK | SPI_NOR_SWP_IS_VOLATILE,
.no_sfdp_flags = SECT_4K,
}, {
.id = SNOR_ID(0x8c, 0x41, 0x16),
.name = "f25l32qa-2s",
.size = SZ_4M,
.flags = SPI_NOR_HAS_LOCK,
.no_sfdp_flags = SECT_4K,
}, {
.id = SNOR_ID(0x8c, 0x41, 0x17),
.name = "f25l64qa",
.size = SZ_8M,
.flags = SPI_NOR_HAS_LOCK,
.no_sfdp_flags = SECT_4K,
}
};
const struct spi_nor_manufacturer spi_nor_esmt = {
.name = "esmt",
.parts = esmt_nor_parts,
.nparts = ARRAY_SIZE(esmt_nor_parts),
};
Annotation
- Immediate include surface: `linux/mtd/spi-nor.h`, `core.h`.
- Atlas domain: Driver Families / drivers/mtd.
- 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.