STRUCT PDS_CORE_DEV_IDENTIFY_CMD(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct pds_core_dev_identify_cmd(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual πŸŽ€ β€” this little page is all about struct pds_core_dev_identify_cmd, aka the driver/device identify command. yes it's a kernel thing. yes it's iconic. let's get into it ✨


🌸 NAME 🌸

struct pds_core_dev_identify_cmd β€” the Driver/device identify command. that's it, that's the vibe πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

the whole struct, exactly as it lives, no cap:

struct pds_core_dev_identify_cmd {
    u8 opcode;
    u8 ver;
};

two whole fields. tiny struct, main character energy πŸ‘‘


πŸŽ€ Members πŸŽ€

okay so here's what's inside, one by one 🫢

  • opcode β€” this is the Opcode PDS_CORE_CMD_IDENTIFY. that's literally what it holds πŸ’…
  • ver β€” the Highest version of identify supported by driver. highkey important to get right ⭐

πŸ’œ Description πŸ’œ

so what does this thing actually want? it Expects to find driver identification info (that'd be struct pds_core_drv_identity) hanging out in cmd_regs->data πŸ“ like, that's where it's looking, bestie.

and the Driver should keep the devcmd interface locked while preparing the driver info πŸ”’ β€” no cap, don't let go of that lock until the info's ready. it's giving "hold the door" energy 😭

fr fr, keep that devcmd interface locked while you prep the driver info. that part is not optional, it's the whole mood πŸ™ˆ

🌈 SEE ALSO 🌈

the full friend group, everybody's here, nobody left out πŸ’–:

  • 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_comp(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)

okay that's the whole page, bestie 🧚 and before you close the tab β€” the fine print at the bottom says this one lives at ./include/linux/pds, dated October 2026, and the footer still calls it struct pds_c...identify_cmd(9) because the terminal's just dramatic like that πŸ’€ slay. bye bestie, go identify some devices πŸ’–βœ¨

πŸ“¦ where this page comes from