nfc_target_lost(9)

📦 version 7.3.1, in nixpkgs unstable

💜 nfc_target_lost(9) 💜

okay bestie, welcome to the Kernel API Manual, section 9 — this is the little page that tells you how to break the news that a target ghosted the field 🦋

✨ NAME ✨

nfc_target_lost — the "hey, that activated target just dipped out of the field" announcement 💨

✨ SYNOPSIS ✨

int nfc_target_lost (struct nfc_dev *dev , u32 target_idx );

no cap, that's the whole signature 🫶

✨ ARGUMENTS ✨

  • dev — the nfc device that had the activated target in field. like, the one that's gonna be emotionally affected by the loss 😭
  • target_idx — the nfc index of the target. its little ID number, so everyone knows which target left 👑

✨ DESCRIPTION ✨

so here's the situation: the device driver must call this function when the activated target goes out of the field. that's it, that's the job — being the messenger 🧚

⚠️ IMPORTANT ⚠️ bestie please read this part, it's giving serious: this function must not be called from an atomic context. literally do not. 🙈 in addition, it must also not be called from a context that would prevent the NFC Core to call other nfc ops entry point concurrently. so like... don't block the NFC Core from doing its other nfc ops entry point calls at the same time, ykwim? respect the concurrency, periodt 💅

✨ SEE ALSO ✨

the kernel file lives at ./net/nfc/core.c — go say hi to it, it's iconic 🌈

and it's friends with literally everyone:

okay that's the whole page, ily, go call nfc_target_lost responsibly and never from an atomic context 💖✨

mwah 💋

this cutie was brought to you by ./net/nfc, dated October 2026, and honestly it's still nfc_target_lost(9) at heart 🎀🦋💜

📦 where this page comes from