drivers/nfc/st21nfca/Kconfig

Source file repositories/reference/linux-study-clean/drivers/nfc/st21nfca/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/nfc/st21nfca/Kconfig
Extension: [no extension]
Size: 627 bytes
Lines: 20
Domain: Driver Families
Bucket: drivers/nfc
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
config NFC_ST21NFCA
	tristate
	select CRC_CCITT
	help
	  STMicroelectronics ST21NFCA core driver. It implements the chipset
	  HCI logic and hooks into the NFC kernel APIs. Physical layers will
	  register against it.

config NFC_ST21NFCA_I2C
	tristate "STMicroelectronics ST21NFCA NFC driver (I2C)"
	depends on NFC_HCI && I2C && NFC_SHDLC
	select NFC_ST21NFCA
	help
	  This module adds support for the STMicroelectronics st21nfca i2c interface.
	  Select this if your platform is using the i2c bus.

	  If you choose to build a module, it'll be called st21nfca_i2c.
	  Say N if unsure.

Annotation

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