drivers/nfc/pn544/Kconfig

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

File Facts

System: Linux kernel
Corpus path: drivers/nfc/pn544/Kconfig
Extension: [no extension]
Size: 956 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_PN544
	tristate
	select CRC_CCITT
	help
	  NXP PN544 core driver.
	  This is a driver based on the HCI NFC kernel layers and
	  will thus not work with NXP libnfc library.

config NFC_PN544_I2C
	tristate "NXP PN544 device support (I2C)"
	depends on NFC_HCI && I2C && NFC_SHDLC
	select NFC_PN544
	help
	  This module adds support for the NXP pn544 i2c interface.
	  Select this if your platform is using the i2c bus.

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

config NFC_PN544_MEI
	tristate "NXP PN544 device support (MEI)"
	depends on NFC_HCI && NFC_MEI_PHY
	select NFC_PN544
	help
	  This module adds support for the mei interface of adapters using
	  NXP pn544 chipsets.  Select this if your pn544 chipset
	  is handled by Intel's Management Engine Interface on your platform.

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