ENUM NFC_COMMANDS(9)

💖 enum nfc_commands(9) 💖

okay so, bestie, welcome to the kernel API manual — this is the page for enum nfc_commands, which is literally just the list of every nfc command your kernel understands. yes, every single one. buckle up 🎀

✨ NAME ✨

enum nfc_commands — the supported nfc commands, periodt 💅

🌸 SYNOPSIS 🌸

enum nfc_commands {
    NFC_CMD_UNSPEC ,
    NFC_CMD_GET_DEVICE ,
    NFC_CMD_DEV_UP ,
    NFC_CMD_DEV_DOWN ,
    NFC_CMD_DEP_LINK_UP ,
    NFC_CMD_DEP_LINK_DOWN ,
    NFC_CMD_START_POLL ,
    NFC_CMD_STOP_POLL ,
    NFC_CMD_GET_TARGET ,
    NFC_EVENT_TARGETS_FOUND ,
    NFC_EVENT_DEVICE_ADDED ,
    NFC_EVENT_DEVICE_REMOVED ,
    NFC_EVENT_TARGET_LOST ,
    NFC_EVENT_TM_ACTIVATED ,
    NFC_EVENT_TM_DEACTIVATED ,
    NFC_CMD_LLC_GET_PARAMS ,
    NFC_CMD_LLC_SET_PARAMS ,
    NFC_CMD_ENABLE_SE ,
    NFC_CMD_DISABLE_SE ,
    NFC_CMD_LLC_SDREQ ,
    NFC_EVENT_LLC_SDRES ,
    NFC_CMD_FW_DOWNLOAD ,
    NFC_EVENT_SE_ADDED ,
    NFC_EVENT_SE_REMOVED ,
    NFC_EVENT_SE_CONNECTIVITY ,
    NFC_EVENT_SE_TRANSACTION ,
    NFC_CMD_GET_SE ,
    NFC_CMD_SE_IO ,
    NFC_CMD_ACTIVATE_TARGET ,
    NFC_CMD_VENDOR ,
    NFC_CMD_DEACTIVATE_TARGET

};

look at her go 😭 so many little constants. and like, some of them are CMDs and some are EVENTs — that's not a typo, that's the whole vibe of this enum, ok? 👑

🦋 Constants 🦋

• NFC_CMD_UNSPEC — the unspecified command. the "idk what this is" of commands 🙈
• NFC_CMD_GET_DEVICE — request info about a device (needs NFC_ATTR_DEVICE_INDEX), or do a dump request to get a list of all nfc devices. two-for-one deal ✨
• NFC_CMD_DEV_UP — turn on the nfc device (needs NFC_ATTR_DEVICE_INDEX). wakey wakey 💖
• NFC_CMD_DEV_DOWN — turn off the nfc device (needs NFC_ATTR_DEVICE_INDEX). nini 😴
• NFC_CMD_DEP_LINK_UP — no description in the original, it just says -- undescribed -- 💀 the devs really said "you'll find out"
• NFC_CMD_DEP_LINK_DOWN — same situation, also -- undescribed -- 🙈
• NFC_CMD_START_POLL — start polling for targets using the protocols you pass in (needs NFC_ATTR_DEVICE_INDEX and NFC_ATTR_PROTOCOLS). both, bestie, not one 🔥
• NFC_CMD_STOP_POLL — stop polling for targets (needs NFC_ATTR_DEVICE_INDEX) ✋
• NFC_CMD_GET_TARGET — dump every target that the previous poll found (needs NFC_ATTR_DEVICE_INDEX) 🎯
• NFC_EVENT_TARGETS_FOUND — event fired when a new target is found; it sends NFC_ATTR_DEVICE_INDEX ⭐
• NFC_EVENT_DEVICE_ADDED — event fired when a new device is registered (yes, the original spells it "registred", we're leaving that exactly as-is 😭); it sends NFC_ATTR_DEVICE_NAME, NFC_ATTR_DEVICE_INDEX and NFC_ATTR_PROTOCOLS 🫶
• NFC_EVENT_DEVICE_REMOVED — event fired when a device is removed; it sends NFC_ATTR_DEVICE_INDEX 🌈
• NFC_EVENT_TARGET_LOST — -- undescribed --, another mystery icon 👻
• NFC_EVENT_TM_ACTIVATED — event fired when the adapter is activated in target mode 🔥
• NFC_EVENT_TM_DEACTIVATED — event fired when the adapter is deactivated from target mode 🧊
• NFC_CMD_LLC_GET_PARAMS — request the LTO, RW, and MIUX parameters for a device 🎀
• NFC_CMD_LLC_SET_PARAMS — set one or more of the LTO, RW, and MIUX parameters for a device. ok this one's got rules, so listen up: LTO must be set before the link is up, otherwise -EINPROGRESS gets returned. RW and MIUX can be set at anytime and will be passed in subsequent CONNECT and CC messages. and if one of the passed parameters is wrong, none of them get set and you get -EINVAL back. all-or-nothing energy, we respect it 💅
• NFC_CMD_ENABLE_SE — enable the physical link to a specific secure element. once it's enabled, that secure element handles card emulation mode — like, starting a poll from a device that has a secure element enabled means we want to do SE based card emulation 🃏
• NFC_CMD_DISABLE_SE — disable the physical link to a specific secure element 🚫
• NFC_CMD_LLC_SDREQ — -- undescribed -- bestie the docs are simply not there 🫠
• NFC_EVENT_LLC_SDRES — also -- undescribed --, twin of the one above 💀
• NFC_CMD_FW_DOWNLOAD — a request to load/flash firmware, or an event to inform that some firmware was loaded. dual-purpose queen 👑
• NFC_EVENT_SE_ADDED — event fired when a new secure element is discovered. typically this gets sent whenever there's a new NFC controller with either an embedded SE or an UICC one connected to it through SWP ✨
• NFC_EVENT_SE_REMOVED — event fired when a secure element is removed from the system, as a consequence of e.g. an NFC controller being unplugged 🔌
• NFC_EVENT_SE_CONNECTIVITY — fired whenever a secure element is requesting connectivity access. for example, a UICC SE may need to talk to a sleeping modem and will notify that need by sending this event — and then it's up to userspace to decide whether it wakes the modem up or not 😴 your call, bestie
• NFC_EVENT_SE_TRANSACTION — sent when an application running on a specific SE notifies us about the end of a transaction. the parameter for this event is the application ID (AID) 🧾
• NFC_CMD_GET_SE — dump all discovered secure elements from an NFC controller 📋
• NFC_CMD_SE_IO — send/receive APDUs to/from the selected secure element 🔁
• NFC_CMD_ACTIVATE_TARGET — request the NFC controller to reactivate the target 🌟
• NFC_CMD_VENDOR — vendor specific command, meant to be implemented directly from the driver so it can support hardware specific operations. driver girlies, this one's yours 🔧
• NFC_CMD_DEACTIVATE_TARGET — request the NFC controller to deactivate the target 🌙

🔍 SEE ALSO 🔍

Kernel file ./include/uapi/linux/nfc.h and enum nfc_attrs(9) — go read that one next, iykyk 👀

and that's the page!! 🫶 shoutout to ./include/uapi/linux, October 2026 for the source and the date — mwah, love u, thanks for the enum 💖✨🎀