rk3x_i2c_clk_notifier_cb(9)

okay so bestie, welcome to the Kernel API Manual — this page is all about rk3x_i2c_clk_notifier_cb(9), and it's giving clock rate change callback realness 💅✨

💖 NAME 💖

rk3x_i2c_clk_notifier_cb — the Clock rate change callback. literally that's the name, no cap 🎀

🌸 SYNOPSIS 🌸

       int rk3x_i2c_clk_notifier_cb (struct notifier_block *nb , unsigned long
       event , void *data );

🦋 ARGUMENTS 🦋

• nb — pointer to notifier block 🫶
• event — notification reason 👀
• data — pointer to notification data object ✨

🎀 DESCRIPTION 🎀

so the callback does a vibe check on whether a valid bus frequency can be generated after the change. if it can, the change gets acknowledged ✅; if not, the change is aborted 🛑.

also highkey important: new dividers are written to the HW in the pre- or post change notification, depending on the scaling direction — yes, that's the clock math tea ☕💅

and for the receipts: code adapted from i2c-cadence.c 📝

⭐ RETURN ⭐

• NOTIFY_STOP — the rate change should be aborted 🛑
• NOTIFY_OK — acknowledge the change ✅
• NOTIFY_DONE — the notification is considered irrelevant 🫠

🌈 SEE ALSO 🌈

Kernel file: ./drivers/i2c/busses/i2c-rk3x.c

• struct i2c_spec_values(9)
• struct rk3x_i2c_calced_timings(9)
• struct rk3x_i2c_soc_data(9)
• struct rk3x_i2c(9)
• rk3x_i2c_start(9)
• rk3x_i2c_stop(9)
• rk3x_i2c_prepare_read(9)
• rk3x_i2c_fill_transmit_buf(9)
• rk3x_i2c_get_spec(9)
• rk3x_i2c_v0_calc_timings(9)
• rk3x_i2c_v1_calc_timings(9)
• rk3x_i2c_setup(9)

mwah 💋 this page is signed off from ./drivers/i2c/busses, dated October 2026, and it's the rk3x_i2c_clk_notifier_cb(9) page — catch u later, bestie! 🫶💖