linux.git/arch/sh/kernel/cpu/sh5, branch v3.14

sh: Don't set plat_sci_port scbrr_algo_id field

2013-12-24T12:49:43+00:00

The field will be removed from the sh-sci driver. Don't set it and let
the driver handle baud rate calculation internally.

Signed-off-by: Laurent Pinchart 
Signed-off-by: Simon Horman

sh: Declare SCIF register base and IRQ as resources

2013-12-24T12:49:43+00:00

Passing the register base address and IRQ through platform data is
deprecated. Use resources instead.

Signed-off-by: Laurent Pinchart 
Signed-off-by: Simon Horman

sh: delete __cpuinit usage from all sh files

2013-07-14T23:36:53+00:00

The __cpuinit type of throwaway sections might have made sense
some time ago when RAM was more constrained, but now the savings
do not offset the cost and complications.  For example, the fix in
commit 5e427ec2d0 ("x86: Fix bit corruption at CPU resume time")
is a good example of the nasty type of bugs that can be created
with improper use of the various __init prefixes.

After a discussion on LKML[1] it was decided that cpuinit should go
the way of devinit and be phased out.  Once all the users are gone,
we can then finally remove the macros themselves from linux/init.h.

Note that some harmless section mismatch warnings may result, since
notify_cpu_starting() and cpu_up() are arch independent (kernel/cpu.c)
are flagged as __cpuinit  -- so if we remove the __cpuinit from
arch specific callers, we will also get section mismatch warnings.
As an intermediate step, we intend to turn the linux/init.h cpuinit
content into no-ops as early as possible, since that will get rid
of these warnings.  In any case, they are temporary and harmless.

This removes all the arch/sh uses of the __cpuinit macros from
all C files.  Currently sh does not have any __CPUINIT used in
assembly files.

[1] https://lkml.org/lkml/2013/5/20/589

Cc: Paul Mundt 
Cc: linux-sh@vger.kernel.org
Signed-off-by: Paul Gortmaker

sh: switch to generic kernel_thread()/kernel_execve()

2012-10-23T02:31:01+00:00

Signed-off-by: Al Viro

sh: Fix up TIF_NOTIFY_RESUME sans TIF_SIGPENDING handling.

2012-09-18T08:04:37+00:00

As Al notes, we missed a TIF_NOTIFY_RESUME check which caused any
handlers without TIF_SIGPENDING also set to skip the notification:

	Looks like while it is in the relevant masks *and* checked in
	do_notify_resume() both on 32bit and 64bit variants since commit
	ab99c733ae73cce31f2a2434f7099564e5a73d95 ("sh: Make syscall tracer
	use tracehook notifiers, add TIF_NOTIFY_RESUME.") they are
	actually *not* reached without simulataneous SIGPENDING, since
	the actual glue in the callers had not been updated back then and
	still checks for _TIF_SIGPENDING alone when deciding whether to
	hit do_notify_resume() or not.

Reported-by: Nobuhiro Iwamatsu 
Signed-off-by: Al Viro 
Tested-by: Nobuhiro Iwamatsu 
Signed-off-by: Paul Mundt

Merge branch 'sh/multi-unwinders' into sh-latest

2012-06-13T03:12:14+00:00

sh: use the new generic strnlen_user() function

2012-06-13T01:28:37+00:00

This discards both the _32 and _64 versions in favour of the consolidated
generic one.

Signed-off-by: Paul Mundt

sh: switch to generic strncpy_from_user().

2012-06-13T01:28:16+00:00

This kills off the special sh32/64 versions and adopts the generic
version. It should be possible to optimize this for SH-4A unaligned
loads, but this is a corner case that can be supported incrementally.

Signed-off-by: Paul Mundt

sh64: Convert to unwinder API.

2012-05-24T06:03:46+00:00

This switches over to use the sh unwinder API which brings it all in line
with the general sh routines (which we shuffle around at the same time),
and lets us kill off more sh64-specific cruft.

Signed-off-by: Paul Mundt

sh64: Invert page fault fast-path error path values.

2012-05-14T07:44:45+00:00

This brings the sh64 version in line with the sh32 one with regards to
how errors are handled. Base work for further unification of the
implementations.

Signed-off-by: Paul Mundt