ENUM PDS_CORE_DEV_CAPABILITY(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ enum pds_core_dev_capability(9) ✨

okay so this is a page straight out of the Kernel API Manual β€” yes, the actual kernel docs, we're being fancy today πŸ’… β€” and it's all about the little enum that tells you what a device is capable of. tiny enum, big main character energy πŸ‘‘


🌸 NAME 🌸

enum pds_core_dev_capability β€” literally just the device capabilities, bestie. that's the whole vibe check πŸ¦‹


πŸŽ€ SYNOPSIS πŸŽ€

enum pds_core_dev_capability {
    PDS_CORE_DEV_CAP_PLDM_FW_UPDATE ,
    PDS_CORE_DEV_CAP_HOST_MEM

};

look at her. two constants. flawless. no notes πŸ”₯


πŸ’œ CONSTANTS πŸ’œ

  • PDS_CORE_DEV_CAP_PLDM_FW_UPDATE β€” this one means the device only supports firmware update via PLDM. only. exclusively. no cap, that's the whole route πŸ›£οΈ
  • PDS_CORE_DEV_CAP_HOST_MEM β€” and this one means the device supports host memory for firmware use ✨ your host, doing fw favours 🫢

πŸ¦‹ SEE ALSO πŸ¦‹

if you wanna go deeper (and you do, iykyk), start with the kernel file ./include/linux/pds/pds_core_if.h, and then honestly just binge the whole connected universe:

  • struct pds_core_drv_identity(9)
  • struct pds_core_dev_identity(9)
  • struct pds_core_dev_identify_cmd(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)

like. that's a lot of lore. go read it. i'll wait πŸ’€


ngl the whole page is short and sweet, so there's no scary warnings here β€” just two constants and a reading list longer than your tbr pile πŸ“š

okay that's the page!! this one came from ./include/linux/pds and it's dated October 2026, so mark your calendar bestie πŸ—“οΈπŸ’– mwah, go forth and identify those devices 🧚✨

πŸ“¦ where this page comes from