[PATCH v6 05/17] powerpc: define get_cycles macro for arch-override

2022-04-27 Thread Jason A. Donenfeld
PowerPC defines a get_cycles() function, but it forgot to do the usual `#define get_cycles get_cycles` dance, making it impossible for generic code to see if an arch-specific function was defined. Cc: Thomas Gleixner Cc: Arnd Bergmann Cc: Michael Ellerman Cc: Benjamin Herrenschmidt Cc: Paul

Re: [RESEND PATCH] Input: joystick/analog - Use get_cycles() on PPC

2018-03-16 Thread Michael Ellerman
Dmitry Torokhov writes: > On Wed, Mar 14, 2018 at 10:17:52PM +1100, Michael Ellerman wrote: >> The analog joystick driver spits a warning at us: >> >> drivers/input/joystick/analog.c:176:2: warning: #warning Precise timer >> not defined for this architecture. >

Re: [RESEND PATCH] Input: joystick/analog - Use get_cycles() on PPC

2018-03-14 Thread Dmitry Torokhov
On Wed, Mar 14, 2018 at 10:17:52PM +1100, Michael Ellerman wrote: > The analog joystick driver spits a warning at us: > > drivers/input/joystick/analog.c:176:2: warning: #warning Precise timer > not defined for this architecture. > > PPC has get_cycles() so use that.

[RESEND PATCH] Input: joystick/analog - Use get_cycles() on PPC

2018-03-14 Thread Michael Ellerman
The analog joystick driver spits a warning at us: drivers/input/joystick/analog.c:176:2: warning: #warning Precise timer not defined for this architecture. PPC has get_cycles() so use that. Signed-off-by: Michael Ellerman --- drivers/input/joystick/analog.c | 2 +- 1 file changed, 1

[RESEND PATCH] input/joystick/analog: Use get_cycles() on PPC

2017-06-07 Thread Michael Ellerman
The analog joystick driver spits a warning at us: drivers/input/joystick/analog.c:176:2: warning: #warning Precise timer not defined for this architecture. PPC has get_cycles() so use that. Signed-off-by: Michael Ellerman --- drivers/input/joystick/analog.c | 2 +- 1 file changed, 1

Re: get_cycles()

2008-04-27 Thread Tony Breeds
On Sun, Apr 27, 2008 at 03:35:54AM -0700, Kevin Diggs wrote: > I'm working on a cpufreq driver for the 750GX so I don't think I have to > worry about being to platform specific. > > Would a compile time configuration be a good idea (hrtimer or > get_cycles() assiste

Re: get_cycles()

2008-04-27 Thread Kevin Diggs
Please don't use platform specific interfaces if you don't have to. You're be insulated from so many things. I'm working on a cpufreq driver for the 750GX so I don't think I have to worry about being to platform specific. Would a compile time configuration be a good idea

Re: get_cycles()

2008-04-26 Thread David Miller
From: Kevin Diggs <[EMAIL PROTECTED]> Date: Sat, 26 Apr 2008 19:39:07 -0700 > This looks pretty cool ... but I don't want to create a dependency on > hrtimer. It doesn't create such a dependency. We use it unconditionally in the generic networking. Please don't use platform specific interfaces

Re: get_cycles()

2008-04-26 Thread Kevin Diggs
David Miller wrote: From: Kevin Diggs <[EMAIL PROTECTED]> Date: Sat, 26 Apr 2008 00:54:11 -0700 Anyone know how to turn get_cycles() into an actual time in a module? ppc_tb_freq does not seem to be exported? You should really be using ktime_t and associated interfaces. This looks

Re: get_cycles()

2008-04-26 Thread David Miller
From: Kevin Diggs <[EMAIL PROTECTED]> Date: Sat, 26 Apr 2008 00:54:11 -0700 > Anyone know how to turn get_cycles() into an actual time in a module? > ppc_tb_freq does not seem to be exported? You should really be using ktime_t and associate

get_cycles()

2008-04-26 Thread Kevin Diggs
H, Anyone know how to turn get_cycles() into an actual time in a module? ppc_tb_freq does not seem to be exported? kevin ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev