drivers/nfc/st-nci/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/nfc/st-nci/Kconfig
Extension: [no extension]
Size: 981 bytes
Lines: 32
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_ST_NCI
	tristate
	help
	  STMicroelectronics NFC NCI chips core driver. It implements the chipset
	  NCI logic and hooks into the NFC kernel APIs. Physical layers will
	  register against it.

config NFC_ST_NCI_I2C
	tristate "STMicroelectronics ST NCI NFC driver (I2C)"
	depends on NFC_NCI && I2C
	select NFC_ST_NCI
	help
	  This module adds support for an I2C interface to the
	  STMicroelectronics NFC NCI chips family.
	  Select this if your platform is using the i2c bus.

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

config NFC_ST_NCI_SPI
	tristate "STMicroelectronics ST NCI NFC driver (SPI)"
	depends on NFC_NCI && SPI
	select NFC_ST_NCI
	help
	  This module adds support for an SPI interface to the
	  STMicroelectronics NFC NCI chips family.
	  Select this if your platform is using the spi bus.

	  If you choose to build a module, it'll be called st-nci_spi.
	  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.