Skip to content

RFC unify definition of CLOCK_TICK_RATE across different platforms

Kevin Hilman linux-arm-kernel 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest0 of 5 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 5 patches the cover letter announces are in this archive.

Reviews trailers per patch

PatchKevin Hilman
SeriesA-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [RFC, PATCH 0/5] unify definition of CLOCK_TICK_RATE across different platforms
Quoted 12 lines · Lennert Buytenhek

One of the things preventing building an ARM multiplatform kernel image is the fact that CLOCK_TICK_RATE (and as a consequence, LATCH) is defined differently for each ARM platform.

The patches in this series:
- pull the per-platform CLOCK_TICK_RATE defines from <mach/timex.h> into arch/arm/mach-foo/ (on those platforms that use the CLOCK_TICK_RATE define and/or the LATCH define in their platform support code);
- define CLOCK_TICK_RATE as a platform-independent value in <asm/timex.h>;
- get rid of all <mach/timex.h> include files.

Quoted 1 line

Comments welcome!

Excellent!

For the davinci & OMAP changes: