nfc_targets_found(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ nfc_targets_found(9) ✨

okay bestie, welcome to the Kernel API Manual πŸ’… this one's short but she's important, so let's get into it 🫢


🌸 NAME 🌸

nfc_targets_found β€” the lil function that says "bestie, we found targets" ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

int nfc_targets_found (struct nfc_dev *dev , struct nfc_target *targets
, int n_targets );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the nfc device that found the targets, like the main character who spotted them πŸ‘‘
  • targets β€” array of nfc targets found, literally the whole friend group 🫢
  • n_targets β€” targets array size, aka how many besties are in the group chat πŸ’–

⭐ DESCRIPTION ⭐

so here's the vibe: the device driver must call this function when one or many nfc targets are found. no cap, it's required πŸ™ˆ

and after calling this function? the device driver must stop polling for targets. like, wrap it up, the search is over periodt πŸ’…


πŸ’€ NOTE πŸ’€

listen up, this part matters fr fr πŸ”₯

This function can be called with targets=NULL and n_targets=0 to notify a driver error β€” meaning that the polling operation cannot complete. so yeah, NULL isn't always a bug, sometimes it's just the sad truth 😭

IMPORTANT: this function must not be called from an atomic context. that's a hard no, not a vibe check you can pass 🚫

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. like, don't be that person blocking the whole group chat from typing, okay? πŸ’€


🌈 SEE ALSO 🌈

Kernel file ./net/nfc/core.c β€” go read her, she's iconic πŸ‘‘


okay that's the whole page, you ate that πŸ“ this lil gem lives in ./net/nfc, and she's dated October 2026 β€” save the date bestie, mwah πŸ’œ

πŸ“¦ where this page comes from