STRUCT PDS_CORE_DEV_IDENTIFY_COMP(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ struct pds_core_dev_identify_comp(9) πŸŽ€

okay so bestie, welcome to the Kernel API Manual β€” yes, we're doing kernel API manual pages now, and honestly? it's giving main character energy. this one's about struct pds_core_dev_identify_comp, the completion side of the device identify command. pull up a chair, we're gonna read it together πŸ’–


✨ NAME ✨

struct pds_core_dev_identify_comp β€” the completion struct for the device identify command. the after picture. the "we asked, the device answered" moment πŸ¦‹


🌸 SYNOPSIS 🌸

struct pds_core_dev_identify_comp {
    u8 status;
    u8 ver;
 };

that's the whole thing. two little u8s carrying the entire follow-up convo, no cap ✨


πŸ’… Members πŸ’…

  • status β€” how the command actually went. it's an enum pds_core_status_code, so go look over there if you wanna know what the values mean. it's literally the vibe check of the whole operation 🫢
  • ver β€” the version of identify that the device hands back to you. the device's own little flex πŸ”₯

🌈 Description 🌈

okay so here's the tea: the actual device identification info β€” and that's struct pds_core_dev_identity, just so we're clear β€” can be found chilling in cmd_regs->data. like, that's where it lives, that's its home 🏠

But (and this is the important part, don't skip it πŸ™ˆ): while you're reading those results, the driver should keep the devcmd interface locked. not optional, not a suggestion β€” locked. think of it like holding the door while your bestie grabs her stuff, except the door is a devcmd interface and the stuff is identification data πŸ’€

ngl this is the kind of caveat that seems small and then bites you. keep the lock. periodt πŸ’…

⭐ SEE ALSO ⭐

the whole extended friend group, honestly β€” every one of these is a real one:

  • Kernel file ./include/linux/pds/pds_core_if.h πŸ‘‘
  • struct pds_core_drv_identity(9)
  • enum pds_core_dev_capability(9)
  • struct pds_core_dev_identity(9)
  • struct pds_core_dev_identify_cmd(9)
  • struct pds_core_dev_reset_cmd(9)
  • struct pds_core_dev_reset_comp(9)
  • struct pds_core_dev_init_cmd(9)
  • struct pds_core_dev_init_comp(9)
  • struct pds_core_fw_download_cmd(9)
  • struct pds_core_fw_download_comp(9)
  • enum pds_core_fw_control_oper(9)
  • enum pds_core_fw_slot(9)
  • struct pds_core_fw_control_cmd(9)
  • struct pds_core_fw_control_comp(9)
  • enum pds_core_vf_link_status(9)
  • struct pds_core_vf_setattr_cmd(9)
  • struct pds_core_vf_getattr_cmd(9)
  • struct pds_core_vf_ctrl_cmd(9)
  • struct pds_core_vf_ctrl_comp(9)
  • struct pds_core_send_pkg_data_cmd(9)
  • struct pds_core_send_pkg_data_comp(9)
  • struct pds_core_component_tbl(9)
  • struct pds_core_send_component_tbl_cmd(9)
  • struct pds_core_send_component_tbl_comp(9)
  • enum pds_core_send_component_op(9)
  • struct pds_core_flash_component(9)
  • struct pds_core_send_component_cmd(9)
  • struct pds_core_send_component_comp(9)
  • enum pds_core_fw_component_type(9)
  • enum pds_core_component_info_flags(9)
  • struct pds_core_fw_component_info(9)
  • struct pds_core_component_list_info(9)
  • struct pds_core_get_component_info_cmd(9)
  • struct pds_core_get_component_info_comp(9)
  • struct pds_core_finalize_update_cmd(9)
  • struct pds_core_finalize_update_comp(9)
  • struct pds_core_match_record_desc_cmd(9)
  • struct pds_core_match_record_desc_comp(9)
  • enum pds_core_host_mem_oper(9)
  • struct pds_core_host_mem_cmd(9)
  • struct pds_core_host_mem_comp(9)
  • struct pds_core_dev_hwstamp_regs(9)
  • struct pds_core_dev_info_regs(9)
  • struct pds_core_dev_cmd_regs(9)
  • struct pds_core_dev_regs(9)

go read them all, i'll wait πŸ§šπŸ’œ


and that's the page!! sourced straight from ./include/linux/pds, dated October 2026 β€” so like, future-dated, iconic behavior honestly πŸ’€βœ¨ slay, go lock that devcmd interface, ily bye πŸŽ€πŸŒˆ

πŸ“¦ where this page comes from