drivers/mtd/nand/raw/nand_sandisk.c

File Facts

System

Linux kernel

Corpus path

drivers/mtd/nand/raw/nand_sandisk.c

Extension

.c

Size

630 bytes

Lines

27

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

• internals.h

Detected Declarations

• function sdtnqgama_choose_interface_config
• function sandisk_nand_init

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0-or-later

#include "internals.h"

static int
sdtnqgama_choose_interface_config(struct nand_chip *chip,
				  struct nand_interface_config *iface)
{
	onfi_fill_interface_config(chip, iface, NAND_SDR_IFACE, 0);

	return nand_choose_best_sdr_timings(chip, iface, NULL);
}

static int sandisk_nand_init(struct nand_chip *chip)
{
	if (!strncmp("SDTNQGAMA", chip->parameters.model,
		     sizeof("SDTNQGAMA") - 1))
		chip->ops.choose_interface_config =
			&sdtnqgama_choose_interface_config;

	return 0;
}

const struct nand_manufacturer_ops sandisk_nand_manuf_ops = {
	.init = sandisk_nand_init,
};

Annotation

• Immediate include surface: `internals.h`.
• Detected declarations: `function sdtnqgama_choose_interface_config`, `function sandisk_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.