drivers/clocksource/sh_cmt.c

File Facts

System

Linux kernel

Corpus path

drivers/clocksource/sh_cmt.c

Extension

.c

Size

29557 bytes

Lines

1190

Domain

Driver Families

Bucket

drivers/clocksource

Inferred role

Driver Families: exported/initcall integration point

Status

integration implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/clk.h
• linux/clockchips.h
• linux/clocksource.h
• linux/delay.h
• linux/err.h
• linux/init.h
• linux/interrupt.h
• linux/io.h
• linux/iopoll.h
• linux/ioport.h
• linux/irq.h
• linux/module.h
• linux/of.h
• linux/platform_device.h
• linux/pm_domain.h
• linux/pm_runtime.h
• linux/sh_timer.h
• linux/slab.h
• linux/spinlock.h
• asm/platform_early.h

Detected Declarations

• struct sh_cmt_device
• struct sh_cmt_info
• struct sh_cmt_channel
• struct sh_cmt_device
• enum sh_cmt_model
• function sh_cmt_read16
• function sh_cmt_read32
• function sh_cmt_write16
• function sh_cmt_write32
• function sh_cmt_read_cmstr
• function sh_cmt_write_cmstr
• function sh_cmt_read_cmcsr
• function sh_cmt_write_cmcsr
• function sh_cmt_read_cmcnt
• function sh_cmt_write_cmcnt
• function sh_cmt_write_cmcor
• function sh_cmt_get_counter
• function sh_cmt_start_stop_ch
• function sh_cmt_enable
• function sh_cmt_disable
• function sh_cmt_clock_event_program_verify
• function __sh_cmt_set_next
• function sh_cmt_set_next
• function sh_cmt_interrupt
• function sh_cmt_start_clocksource
• function sh_cmt_stop_clocksource
• function sh_cmt_start_clockevent
• function sh_cmt_stop_clockevent
• function sh_cmt_clocksource_read
• function sh_cmt_clocksource_enable
• function sh_cmt_clocksource_disable
• function sh_cmt_clocksource_suspend
• function sh_cmt_clocksource_resume
• function sh_cmt_register_clocksource
• function sh_cmt_clock_event_start
• function sh_cmt_clock_event_shutdown
• function sh_cmt_clock_event_set_state
• function sh_cmt_clock_event_set_oneshot
• function sh_cmt_clock_event_set_periodic
• function sh_cmt_clock_event_next
• function sh_cmt_clock_event_suspend
• function sh_cmt_clock_event_resume
• function sh_cmt_register_clockevent
• function sh_cmt_register
• function sh_cmt_setup_channel
• function sh_cmt_map_memory
• function sh_cmt_setup
• function sh_cmt_probe

Annotated Snippet

subsys_initcall(sh_cmt_init);
module_exit(sh_cmt_exit);

MODULE_AUTHOR("Magnus Damm");
MODULE_DESCRIPTION("SuperH CMT Timer Driver");

Annotation

• Immediate include surface: `linux/clk.h`, `linux/clockchips.h`, `linux/clocksource.h`, `linux/delay.h`, `linux/err.h`, `linux/init.h`, `linux/interrupt.h`, `linux/io.h`.
• Detected declarations: `struct sh_cmt_device`, `struct sh_cmt_info`, `struct sh_cmt_channel`, `struct sh_cmt_device`, `enum sh_cmt_model`, `function sh_cmt_read16`, `function sh_cmt_read32`, `function sh_cmt_write16`, `function sh_cmt_write32`, `function sh_cmt_read_cmstr`.
• Atlas domain: Driver Families / drivers/clocksource.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.