STRUCT QCOM_ICC_QOS(9)
β¨ 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.hstruct 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms