drivers/nfc/nxp-nci/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/nfc/nxp-nci/Kconfig
Extension: [no extension]
Size: 780 bytes
Lines: 26
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_NXP_NCI
	tristate "NXP-NCI NFC driver"
	depends on NFC_NCI
	help
	  Generic core driver for NXP NCI chips such as the NPC100 (PN547),
	  NPC300 (PN548) or PN7150 families.
	  This is a driver based on the NCI NFC kernel layers and
	  will thus not work with NXP libnfc library.

	  To compile this driver as a module, choose m here. The module will
	  be called nxp_nci.
	  Say N if unsure.

config NFC_NXP_NCI_I2C
	tristate "NXP-NCI I2C support"
	depends on NFC_NXP_NCI && I2C
	help
	  This module adds support for an I2C interface to the NXP NCI
	  chips.
	  Select this if your platform is using the I2C bus.

	  To compile this driver as a module, choose m here. The module will
	  be called nxp_nci_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.