NXP PN544 NFC controller
NXP's PN544 near-field communication chip, used in smartphones and other portable devices around the late 2000s and early 2010s to enable contactless payments, tag reading, and peer-to-peer NFC. It connects over I2C or via Intel's MEI interface and was a common building block in handsets of that era.
recommendation
Worth keeping but documenting as legacy hardware. The PN544 is no longer used in new designs — NXP has moved on to the PN7160/PN7161 NCI-based parts, and the kernel's nxp-nci driver is the modern replacement path — but the code still receives occasional fixes (a patch was posted in early 2026), and devices in the field continue to depend on it. An obsolescence note in Kconfig would help users find the right driver for newer NXP NFC silicon.
repository signals
sources
- lore.kernel.org
Recent upstream maintenance still exists for this driver family; a pn544 I2C patch was posted in 2026, so the code is not abandoned.
- nxp.com
PN544 was marketed for mobile phones and portable equipment, indicating an older handset-era NFC controller rather than a current embedded-design part.
- nxp.com
NXP's current active NFC controller line is PN7160/PN7161, showing new designs have moved to newer NCI-based parts.
- git.kernel.org
Upstream nxp-nci covers newer NXP NFC chips such as PN547/PN548/PN7150 families, making it the natural replacement path for new deployments.
codex reasoning notes (technical)
Real driver directory: pn544.c plus I2C/MEI transport glue. `exec_command` on local Kconfig/Makefile identified NXP PN544 and showed MEI/I2C bindings. `lore_file_timeline` on pn544.c and i2c.c showed continued low-volume maintenance through 2025-2026 and no sampled removal thread, so removal/deprecation is not justified. `web.search_query` surfaced NXP's PN544 brochure URL and active PN7160 product page; kernel.org Kconfig URL was added via canonical recall to identify the upstream successor family. Conclusion: legacy hardware with low present-day deployment, but upstream still fixes it occasionally, so keep the driver with obsolescence annotation rather than deprecating or removing it.