of_ti_clk_register_omap_hw(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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

okay so real talk, this is a page straight out of the Kernel API Manual, and it's about getting your clk_hw_omap clock seen by the clock framework. it's giving backstage-pass energy. let's go πŸŽ€


✨ NAME ✨

of_ti_clk_register_omap_hw β€” registers a clk_hw_omap to the clock framework. that's it, that's the whole vibe πŸ¦‹


🌸 SYNOPSIS 🌸

struct clk * of_ti_clk_register_omap_hw (struct device_node *node ,
       struct clk_hw *hw , const char *con );

like, three args, one return, no drama. periodt.


πŸ’– ARGUMENTS πŸ’–

  • node β€” the device node for this clock. it's the clock's little home address, yk?
  • hw β€” the hardware clock handle. the actual clock in question, the main character πŸ‘‘
  • con β€” the connection ID for this clock. its lil name tag at the function πŸ’…

πŸ”₯ DESCRIPTION πŸ”₯

so what does it do. okay:

  • registers a clk_hw_omap clock to the clock framework (yes, the original page literally says "framewor", we're keeping the lore 😭)
  • adds a clock alias for it
  • adds the list to the available clk_hw_omap type clocks

and the return value? if it worked, you get a handle to the registered clock β€” literally the glow-up receipt ✨. if it didn't work, you get an ERR_PTR value. no in-between, no "maybe", it's giving all or nothing πŸ’€


🌈 SEE ALSO 🌈

go read these next, i promise they're iconic in their own way:


ngl, if you skipped the DESCRIPTION and went straight here, go back up. the ERR_PTR bit matters fr fr πŸ™ˆ

and that's the page! signing off from ./drivers/clk/ti, dated October 2026, living under the very official title of of_ti_clk_register_omap_hw(9). mwah πŸ’‹ stay slay, keep your clocks registered, ily πŸ«ΆπŸ’œβ­

πŸ“¦ where this page comes from