dmtimer_write(9)
β¨ NAME β¨
Okay bestie, welcome to the dmtimer_write(9) page from the Kernel API Manual π β and the name is literally the whole plot: dmtimer_write writes timer registers in posted and non-posted mode. No cap.
πΈ SYNOPSIS πΈ
void dmtimer_write (struct dmtimer *timer , u32 reg , u32 val );
π ARGUMENTS π
timerβ the timer pointer over which the write operation is to perform. That's your main character timer π.regβ the lowest byte holds the register offset. Just the lowest byte, okay? Don't go thinking the whole thing is the offset π.valβ the data to write into the register. This is the actual payload you're dropping in π.
π¦ DESCRIPTION π¦
So the posted mode bit is encoded in reg β it's literally packed in there, bestie. That means the mode vibe is part of the register value you're passing.
β οΈ In posted mode, the write pending bit must be checked. Otherwise, a write on a register which has a pending write will be lost. Like, gone gone ππ. Do not skip the pending-bit vibe check, fr fr.
π SEE ALSO π
Go give these a read too, bestie:
- Kernel file
./drivers/clocksource/timer-ti-dm.c dmtimer_read(9)omap_dm_timer_request_by_node(9)omap_dm_timer_modify_idlect_mask(9)omap_dm_timer_set_int_disable(9)omap_dm_timer_cap_counter(9)omap_dm_timer_probe(9)omap_dm_timer_remove(9)
Signed with love from the source ./drivers/clocksource, stamped October 2026, on the dmtimer_write(9) page π«Άβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms