linux.git/arch/m68k/kernel/time.c, branch v4.16

sched/headers: Prepare for new header dependencies before moving code to

2017-03-02T07:42:27+00:00

We are going to split  out of , which
will have to be picked up from a couple of .c files.

Create a trivial placeholder  file that just
maps to  to make this patch obviously correct and
bisectable.

Include the new header in the files that are going to need it.

Acked-by: Linus Torvalds 
Cc: Mike Galbraith 
Cc: Peter Zijlstra 
Cc: Thomas Gleixner 
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Ingo Molnar

rtc: m68k: provide ioctl for q40

2016-06-03T22:23:22+00:00

The q40 platform is the only machine in the kernel that provides
RTC_PLL_GET/RTC_PLL_SET ioctl commands in its rtc through the
mach_get_rtc_pll/mach_set_rtc_pll callbacks.

However, this currenctly works only in the old-style genrtc
driver, not the (somewhat) modern rtc-generic driver replacing
it. This adds an ioctl implementation to the m68k generic_rtc_ops
in order to let both drivers provide the same API.

After this, we should be able to remove support for genrtc
from the m68k architecture.

Signed-off-by: Arnd Bergmann 
Acked-by: Geert Uytterhoeven 
Tested-by: Geert Uytterhoeven 
Signed-off-by: Alexandre Belloni

rtc: m68k: provide rtc_class_ops directly

2016-06-03T22:23:05+00:00

The rtc-generic driver provides an architecture specific
wrapper on top of the generic rtc_class_ops abstraction,
and m68k has another abstraction on top, which is a bit
silly.

This changes the m68k rtc-generic device to provide its
rtc_class_ops directly, to reduce the number of layers
by one.

Signed-off-by: Arnd Bergmann 
Acked-by: Geert Uytterhoeven 
Tested-by: Geert Uytterhoeven 
Signed-off-by: Alexandre Belloni

m68k: Export mach_random_get_entropy to modules

2014-07-11T08:37:53+00:00

When a module calls random_get_entropy():

    ERROR: "mach_random_get_entropy" [crypto/drbg.ko] undefined!
    make[1]: *** [__modpost] Error 1

Signed-off-by: Geert Uytterhoeven

m68k: Add infrastructure for machine-specific random_get_entropy()

2013-11-26T10:09:24+00:00

On m68k, get_cycles() (the default implementation for random_get_entropy())
always returns zero, providing no entropy for the random driver.

Add a hook where platforms can provide their own implementation, and wire
it up in the infrastructure provided by commit
61875f30daf60305712e25b209ef41ced2635bad ("random: allow architectures to
optionally define random_get_entropy()").

Signed-off-by: Geert Uytterhoeven

PTR_RET is now PTR_ERR_OR_ZERO(): Replace most.

2013-07-15T01:55:01+00:00

Sweep of the simple cases.

Cc: netdev@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org
Cc: linux-arm-kernel@lists.infradead.org
Cc: Julia Lawall 
Signed-off-by: Rusty Russell 
Acked-by: David S. Miller 
Acked-by: Benjamin Herrenschmidt

m68k: set arch_gettimeoffset directly

2012-12-24T16:36:34+00:00

remove m68k's mach_gettimeoffset function pointer, and instead directly
set the arch_gettimeoffset function pointer. This requires multiplying
all function results by 1000, since the removed m68k_gettimeoffset() did
this. Also, s/unsigned long/u32/ just to make the function prototypes
exactly match that of arch_gettimeoffset.

Cc: Joshua Thompson 
Cc: Sam Creasey 
Acked-by: Geert Uytterhoeven 
Acked-by: Phil Blundell 
Signed-off-by: Stephen Warren

time: convert arch_gettimeoffset to a pointer

2012-12-24T16:36:07+00:00

Currently, whenever CONFIG_ARCH_USES_GETTIMEOFFSET is enabled, each
arch core provides a single implementation of arch_gettimeoffset(). In
many cases, different sub-architectures, different machines, or
different timer providers exist, and so the arch ends up implementing
arch_gettimeoffset() as a call-through-pointer anyway. Examples are
ARM, Cris, M68K, and it's arguable that the remaining architectures,
M32R and Blackfin, should be doing this anyway.

Modify arch_gettimeoffset so that it itself is a function pointer, which
the arch initializes. This will allow later changes to move the
initialization of this function into individual machine support or timer
drivers. This is particularly useful for code in drivers/clocksource
which should rely on an arch-independant mechanism to register their
implementation of arch_gettimeoffset().

This patch also converts the Cris architecture to set arch_gettimeoffset
directly to the final implementation in time_init(), because Cris already
had separate time_init() functions per sub-architecture. M68K and ARM
are converted to set arch_gettimeoffset to the final implementation in
later patches, because they already have function pointers in place for
this purpose.

Cc: Russell King 
Cc: Mike Frysinger 
Cc: Mikael Starvik 
Cc: Hirokazu Takata 
Cc: Thomas Gleixner 
Acked-by: Geert Uytterhoeven 
Acked-by: Jesper Nilsson 
Acked-by: John Stultz 
Signed-off-by: Stephen Warren

m68k: Use PTR_RET rather than if(IS_ERR(...)) + PTR_ERR

2012-08-18T13:16:00+00:00

The semantic patch that makes this change is available
in scripts/coccinelle/api/ptr_ret.cocci.

More information about semantic patching is available at
http://coccinelle.lip6.fr/

Signed-off-by: Thomas Meyer 
Signed-off-by: Geert Uytterhoeven

m68k: fix inclusion of arch_gettimeoffset for non-MMU 68k classic CPU types

2012-06-12T01:58:26+00:00

When building for non-MMU based classic 68k CPU types (like the 68328 for
example) you get a compilation error:

  CC      arch/m68k/kernel/time.o
arch/m68k/kernel/time.c:91:5: error: redefinition of ‘arch_gettimeoffset’
include/linux/time.h:145:19: note: previous definition of ‘arch_gettimeoffset’ was here

The arch_gettimeoffset() code is included when building for these CPU types,
but it shouldn't be. Those machine types do not have
CONFIG_ARCH_USES_GETTIMEOFFSET set.

The fix is simply to conditionally include the arch_gettimeoffset() code on
that same config setting that specifies its use or not.

Signed-off-by: Greg Ungerer 
Acked-by: Geert Uytterhoeven