Skip to contentSkip to conversation

unify definition of CLOCK_TICK_RATE across different platforms

RFC PATCH New Lennert Buytenhek 4 participants 4 messages Oct 20, 2010

lore
Share & tools
lore
#0 lore raw

cover unify definition of CLOCK_TICK_RATE across different platforms

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.

Comments welcome!

#1 lore raw

cover unify definition of CLOCK_TICK_RATE across different platforms

Quoted 4 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.

Quoted 8 lines

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.

Excellent!

#2 lore raw

cover unify definition of CLOCK_TICK_RATE across different platforms

In reply to Lennert Buytenhek

2010/10/20 Lennert Buytenhek <[email protected]>:

Quoted 3 lines

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.

That thing has really annoyed me for some time, so thanks!

For all patches touching U300, Ux500.

Yours,
Linus Walleij

#3 lore raw

cover unify definition of CLOCK_TICK_RATE across different platforms

In reply to Lennert Buytenhek
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: