qcom_icc_aggregate(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… qcom_icc_aggregate β€” the Kernel API Manual glow-up ✨

okay so bestie, welcome to the Kernel API Manual entry for qcom_icc_aggregate πŸŽ€ this is the function that aggregates bw for buckets indicated by tag. yes, "buckets." yes, "tag." we're doing interconnect things and we're doing them gorgeously πŸ’–


✨ NAME ✨

qcom_icc_aggregate β€” aggregate bw for buckets indicated by tag πŸ¦‹

like, it takes your bandwidth numbers and files them into the right little bucket based on the tag. iconic behavior honestly πŸ‘‘


🌸 SYNOPSIS 🌸

int qcom_icc_aggregate (struct icc_node *node , u32 tag , u32 avg_bw ,
u32 peak_bw , u32 *agg_avg , u32 *agg_peak );

that's the whole signature, no cap. int going in, int coming out, and a whole lotta u32 in between 😭


🧚 ARGUMENTS 🧚

okay so every single one of these, let's go 🫢

  • node β€” node to aggregate. the main character of this whole operation ngl ⭐
  • tag β€” tag to indicate which buckets to aggregate. it's giving "which folder do I put this in" energy πŸŽ€
  • avg_bw β€” new bw to sum aggregate. this one gets summed, bestie βž•
  • peak_bw β€” new bw to max aggregate. this one gets maxed, not summed, don't mix them up πŸ’€
  • agg_avg β€” existing aggregate avg bw val. like, the avg val that's already there πŸ™ˆ
  • agg_peak β€” existing aggregate peak bw val. the peak val that's already there πŸ”₯
lowkey important: avg_bw sums and peak_bw maxes. two different verbs, two different buckets, one function. iykyk πŸ’…

πŸ‘‘ SEE ALSO πŸ‘‘

go read these next, bestie, they're all in the Kernel file ./drivers/interconnect/qcom/icc-rpmh.c 🌈


πŸ’œ the cute sign-off πŸ’œ

this page lives in ./drivers/interconnect/qcom, dated October 2026, and it's page qcom_icc_aggregate(9) of the Kernel API Manual β€” that's the whole footer, mwah, slay, periodt πŸ’–βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from