omap init_early changes for irq and timer init
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest6 of 10 patches 0 repliesNew
6 of 10 patches are in this archive. The cover letter announces 10.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/10 | omap: Use separate init_irq functions to avoid cpu_is_omap tests early | +0 | 2 replies | |
| 3/10 | omap: Move dmtimer defines to dmtimer.h | +0 | 1 reply | |
| 4/10 | omap: Make a subset of dmtimer functions into inline functions | +0 | 1 reply | |
| 4/10 | omap: Make a subset of dmtimer functions into inline functions | +0 | 1 reply | |
| 5/10 | omap2+: Use dmtimer macros for clockevent | +0 | 1 reply | |
| 6/10 | omap2+: Remove gptimer_wakekup for now | +0 | 1 reply |
Reviews trailers per patch
1 of 6 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Kevin Hilman |
|---|---|
| Series | R-b |
| 1/10 | R-b |
| 3/10 | |
| 4/10 | |
| 4/10 | |
| 5/10 | |
| 6/10 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 00/10] omap init_early changes for irq and timer init
Quoted 8 lines · Tony Lindgren
This series continues the work to only initialize minimal omap code in
init_earlyand to cut down dependencies to code that should be initialized later. It also cleans up the omap2+ timer init code to prepare things for the later patches.After this series further patches can make the dmtimer code a regular device driver. Later on we can also move the clockource init happen earlier to make
sched_clockwork properly withCONFIG_PRINTK_TIME.
This series looks OK to me.
My primary concerns were around the duplication of code between early/system timers and the "real" device driver. But it now looks like those early timers will also be doing individual init using hwmod and clock framework, so any duplication can be avoided.
Kevin