STRUCT QCOM_ICC_QOS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ struct qcom_icc_qos(9) ✨

okay bestie, welcome to the Kernel API Manual πŸ’– this one's a struct page, and honestly? it's giving backstage-pass energy. it's the Qualcomm-specific interconnect QoS parameters β€” the little control panel that decides how your traffic gets treated on the bus. no cap, kind of a vibe. πŸ¦‹


🌸 NAME 🌸

struct qcom_icc_qos β€” the Qualcomm specific interconnect QoS parameters, aka the receipts for how each node gets prioritized πŸŽ€


⭐ SYNOPSIS ⭐

like, here's the whole squad, exactly as it shows up in the code:

struct qcom_icc_qos {
    u32 areq_prio;
    u32 prio_level;
    bool limit_commands;
    bool ap_owned;
    int qos_mode;
    int qos_port;
    bool urg_fwd_en;
 };

πŸ’… Members πŸ’…

every field is a main character in its own right, so let's do intros:

  • areq_prio β€” node requests priority πŸ”₯ literally what it says on the tin.
  • prio_level β€” the priority level for bus communication. this is the one that actually tells the bus how important you are, iykyk.
  • limit_commands β€” activate/deactivate limiter mode during runtime πŸ‘‘ yes, at runtime, she's flexible like that.
  • ap_owned β€” indicates if the node is owned by the AP or by the RPM. important distinction, don't get it twisted πŸ’€
  • qos_mode β€” the default qos mode for this node. the baseline vibe check ✨
  • qos_port β€” the qos port number for finding qos registers of this node. it's the address of the whole situation, fr fr.
  • urg_fwd_en β€” enable urgent forwarding 🚨 when you absolutely need your traffic to skip the line.

πŸŽ€ SEE ALSO πŸŽ€

go read these next, bestie, they're in the same friend group:

  • the Kernel file ./drivers/interconnect/qcom/icc-rpm.h struct
  • rpm_clk_resource(9)
  • struct qcom_icc_provider(9)
  • struct qcom_icc_node(9)

and that's the whole page, periodt πŸ’œ before you close the tab: this beauty lives in ./drivers/interconnect/qcom, stamped October 2026 β€” so when you cite it, cite it cute. 🫢🌸

πŸ“¦ where this page comes from