OMAP2+: hwmod/clockevent: allow late-init of individual hwmods
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 of 8 patches 0 repliesNew
2 of 8 patches are in this archive. The cover letter announces 8.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 7/8 | OMAP2+: hwmod: add ability to late-init individual hwmods | +0 | 1 reply | |
| 8/8 | OMAP2+: clockevent: late-init GPTIMER clockevent hwmodright before timer init | +0 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/8] OMAP2+: hwmod/clockevent: allow late-init of individual hwmods
Quoted 9 lines · Paul Walmsley
Hello,
This series adds the ability to late-initialize individual hwmods. The goal here is for clockevent (and eventually clocksource) hwmods to be late-initialized individually, and right before they are needed, in the timer init code. Then
omap_hwmod_late_init(), which late-inits the rest of the hwmods, is intended to run as an initcall -- much later in the boot process.
Sounds good to me!
Tony