clk_hw_init_rate_request(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… clk_hw_init_rate_request(9) β€” from the Kernel API Manual, bestie

okay so this is a page about one tiny function that sets up your rate request before you go ask the clock core for a favour. it's a void function, meaning it does the thing and gives you nothing back β€” and honestly? iconic behaviour. no return value, no drama, just vibes and a correctly-initialised struct. πŸŽ€


✨ NAME ✨

clk_hw_init_rate_request β€” Initializes a clk_rate_request

like literally that's it, that's the whole job. it takes your empty little struct and fills it in so you can go submit it. πŸ¦‹


🌸 SYNOPSIS 🌸

void clk_hw_init_rate_request (const struct clk_hw *hw , struct
       clk_rate_request *req , unsigned long rate );

three things go in, nothing comes out. void main character energy fr fr. πŸ’«


πŸŽ€ ARGUMENTS πŸŽ€

  • hw β€” the clk you're repping, aka the one you wanna submit a rate request for πŸ‘‘
  • req β€” the clk_rate_request structure you want to initialise. this is the glow-up target, she's about to get all her fields filled in πŸ’…
  • rate β€” the rate you're requesting. the number. the goal. the dream. ⭐

πŸ’– DESCRIPTION πŸ’–

so what it does: Initializes a clk_rate_request structure to submit to __clk_determine_rate or similar functions.

that's the whole flex, bestie β€” it's the setup step, not the main event. you prep the clk_rate_request here, then hand it off to __clk_determine_rate or whatever similar function is on duty that day. think of it as doing your hair before the party: the party is __clk_determine_rate, and this function is you with the curling iron. ✨🫢

ngl it's a small function but it's load-bearing, so don't skip it. πŸ™ˆ


πŸ¦‹ SEE ALSO πŸ¦‹

first up, the source, so you can go read the real thing: Kernel file ./drivers/clk/clk.c

and now the full link-up, no cap, every single one:

like… that's the whole clock family reunion right there. every cousin showed up. πŸ’€πŸ”₯


seriously though bestie, that's a lot of neighbours β€” if you're poking at rate stuff, at least skim __clk_determine_rate(9) and clk_hw_forward_rate_request(9) so you know where your freshly-initialised struct is actually headed. 🫢

and that's the page!! mwah πŸ’‹ this one lives under ./drivers/clk and it's dated October 2026 β€” so go forth, init your clk_rate_request, and slay. πŸ‘‘πŸŒΈβœ¨

πŸ“¦ where this page comes from