clk_register_clkdev(9)

📦 version 7.3.1, in nixpkgs unstable

💅 clk_register_clkdev (kernel API manual, bestie edition) ✨

okay so this is clk_register_clkdev(9) from the Kernel API Manual — yes, that manual, the one your kernel-dev bestie keeps yelling about. sit down, hydrate, and let's get into it 🫶

🌸 NAME 🌸

clk_register_clkdev — register one clock lookup for a struct clk 💖

like, one (1) lookup. not a million. one. iconic behavior honestly.

⭐ SYNOPSIS ⭐

int clk_register_clkdev (struct clk *clk , const char *con_id , const
char *dev_id );

that's the whole vibe right there 👑

🎀 ARGUMENTS 🎀

  • clk — the struct clk you're associating with all the clk_lookups. this is the main character of the operation ngl 🌟
  • con_id — the connection ID string on the device. it's giving "who am i to this device" energy 💫
  • dev_id — a string describing the device name. name tag but for hardware 🏷️

🦋 DESCRIPTION 🦋

con_id or dev_id may be NULL as a wildcard, just as in the rest of clkdev. yup — NULL is your wildcard bestie, same rules as everywhere else in clkdev, no cap 💅

so here's the cute part: to make things easier for mass registration, we detect error clks from a previous clk_register call, and return the error code for those. literally we're checking the vibes of the last call for you 🔍

and why? because this is to permit this function to be called immediately after clk_register. back-to-back. no breathing room. periodt 🫶

⚠️ real talk: the NULL wildcard thing is for real and it applies to con_id or dev_id — but the error-clk detection only works because it's reading the result of a previous clk_register call. call it right after and you're golden ✨

🌈 SEE ALSO 🌈

kernel file ./drivers/clk/clkdev.c — plus these certified bangers:

go read them, iykyk 💜

and that's the whole page, bestie 🎀 huge shoutout to ./drivers/clk for hosting this file, and to October 2026 for the timestamp — mwah, love u, see u in the next manpage 💖✨🦋

📦 where this page comes from