STRUCT NFC_MEI_PHY(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

struct nfc_mei_phy β€” bestie, this is the NFC description of the MEI PHY and its interface functions πŸ’– (and yes, it's a struct, we stan a struct)

This page lives in the Kernel API Manual btw, in case you were wondering where you wandered into ✨


✨ SYNOPSIS ✨

struct nfc_mei_phy {
    struct mei_cl_device *cldev;
    struct nfc_hci_dev *hdev;
    wait_queue_head_t send_wq;
    u8 fw_ivn;
    u8 vendor_id;
    u8 radio_type;
    u8 reserved;
    u16 req_id;
    u16 recv_req_id;
    int powered;
    int hard_fault;
 };

okay so that's the whole shape of it, no cap 🫢


πŸ‘‘ Members πŸ‘‘

Every field, every vibe, let's go πŸ’…

  • cldev β€” the mei client device πŸŽ€
  • hdev β€” the nfc hci device, iconic
  • send_wq β€” the send completion wait queue, it's giving patience 🌸
  • fw_ivn β€” NFC Interface Version Number πŸ”₯
  • vendor_id β€” NFC manufacturer ID, who made you bestie 😭
  • radio_type β€” NFC radio type πŸ“»
  • reserved β€” reserved for alignment, it's literally just there for the vibes πŸ¦‹
  • req_id β€” the message counter ⭐
  • recv_req_id β€” the reception message counter, twins fr fr πŸ’œ
  • powered β€” the device is in powered state ⚑
  • hard_fault β€” < 0 if a hardware error occurred and prevents normal operation πŸ’€ (that's the bad one, pay attention)
ngl, if hard_fault is < 0, things are NOT slaying. that's a real hardware error blocking normal operation, so treat it with the respect it deserves πŸ™ˆ

🌈 SEE ALSO 🌈

  • Kernel file ./drivers/nfc/mei_phy.h β€” go read the source, iykyk πŸ“–

and that's the whole page, bestie 🧚 from ./drivers/nfc, dated October 2026 β€” stay slay, stay powered, and may your hard_fault never go negative πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from