drivers/mtd/nand/raw/nand_esmt.c
Source file repositories/reference/linux-study-clean/drivers/mtd/nand/raw/nand_esmt.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/mtd/nand/raw/nand_esmt.c- Extension
.c- Size
- 1387 bytes
- Lines
- 60
- 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/rawnand.hinternals.h
Detected Declarations
function Copyrightfunction esmt_nand_init
Annotated Snippet
switch (chip->id.data[4] & 0x3) {
case 0x0:
requirements.strength = 4;
break;
case 0x1:
requirements.strength = 2;
break;
case 0x2:
requirements.strength = 1;
break;
default:
WARN(1, "Could not get ECC info");
requirements.step_size = 0;
break;
}
}
nanddev_set_ecc_requirements(base, &requirements);
}
static int esmt_nand_init(struct nand_chip *chip)
{
if (nand_is_slc(chip))
/*
* It is known that some ESMT SLC NANDs have been shipped
* with the factory bad block markers in the first or last page
* of the block, instead of the first or second page. To be on
* the safe side, let's check all three locations.
*/
chip->options |= NAND_BBM_FIRSTPAGE | NAND_BBM_SECONDPAGE |
NAND_BBM_LASTPAGE;
return 0;
}
const struct nand_manufacturer_ops esmt_nand_manuf_ops = {
.detect = esmt_nand_decode_id,
.init = esmt_nand_init,
};
Annotation
- Immediate include surface: `linux/mtd/rawnand.h`, `internals.h`.
- Detected declarations: `function Copyright`, `function esmt_nand_init`.
- 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.