drivers/memstick/Kconfig

File Facts

System

Linux kernel

Corpus path

drivers/memstick/Kconfig

Extension

[no extension]

Size

649 bytes

Lines

28

Domain

Driver Families

Bucket

drivers/memstick

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-only
#
# MemoryStick subsystem configuration
#

menuconfig MEMSTICK
	tristate "Sony MemoryStick card support"
	help
	  Sony MemoryStick is a proprietary storage/extension card protocol.

	  If you want MemoryStick support, you should say Y here and also
	  to the specific driver for your MemoryStick interface.

if MEMSTICK

config MEMSTICK_DEBUG
	bool "MemoryStick debugging"
	help
	  This is an option for use by developers; most people should
	  say N here.  This enables MemoryStick core and driver debugging.


source "drivers/memstick/core/Kconfig"

source "drivers/memstick/host/Kconfig"

endif # MEMSTICK

Annotation

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