linux.git/arch/c6x/kernel, branch v3.18.72

c6x/ptrace: Remove useless PTRACE_SETREGSET implementation

2017-04-22T05:14:59+00:00

commit fb411b837b587a32046dc4f369acb93a10b1def8 upstream.

gpr_set won't work correctly and can never have been tested, and the
correct behaviour is not clear due to the endianness-dependent task
layout.

So, just remove it.  The core code will now return -EOPNOTSUPPORT when
trying to set NT_PRSTATUS on this architecture until/unless a correct
implementation is supplied.

Signed-off-by: Dave Martin 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

C6x: time: Ensure consistency in __init

2015-05-17T23:12:28+00:00

[ Upstream commit f4831605f2dacd12730fe73961c77253cc2ea425 ]

time_init invokes timer64_init (which is __init annotation)
since all of these are invoked at init time, lets maintain
consistency by ensuring time_init is marked appropriately
as well.

This fixes the following warning with CONFIG_DEBUG_SECTION_MISMATCH=y

WARNING: vmlinux.o(.text+0x3bfc): Section mismatch in reference from the function time_init() to the function .init.text:timer64_init()
The function time_init() references
the function __init timer64_init().
This is often because time_init lacks a __init
annotation or the annotation of timer64_init is wrong.

Fixes: 546a39546c64 ("C6X: time management")
Signed-off-by: Nishanth Menon 
Signed-off-by: Mark Salter 
Signed-off-by: Sasha Levin

c6x: Use sigsp()

2014-08-06T11:04:07+00:00

Use sigsp() instead of the open coded variant.

Signed-off-by: Richard Weinberger 
Acked-by: Mark Salter

c6x: Use get_signal() signal_setup_done()

2014-08-06T11:02:12+00:00

Use the more generic functions get_signal() signal_setup_done()
for signal delivery.

Tested-by: Mark Salter 
Acked-by: Mark Salter 
Signed-off-by: Richard Weinberger

c6x: convert fdt pointers to opaque pointers

2014-04-30T05:59:12+00:00

The architecture code does not need to access the internals of the FDT
blob, so make the pointer to it void *.

Signed-off-by: Rob Herring 
Cc: Mark Salter 
Cc: Aurelien Jacquiot 
Cc: linux-c6x-dev@linux-c6x.org
Tested-by: Grant Likely

of: remove early_init_dt_setup_initrd_arch

2013-10-09T16:39:01+00:00

All arches do essentially the same thing now for
early_init_dt_setup_initrd_arch, so it can now be removed.

Signed-off-by: Rob Herring 
Acked-by: Vineet Gupta 
Cc: Russell King 
Cc: Mark Salter 
Cc: Aurelien Jacquiot 
Cc: James Hogan 
Cc: Michal Simek 
Cc: Ralf Baechle 
Cc: Jonas Bonn 
Cc: Benjamin Herrenschmidt 
Cc: Paul Mackerras 
Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Cc: "H. Peter Anvin" 
Cc: x86@kernel.org
Cc: Chris Zankel 
Cc: Max Filippov 
Acked-by: Grant Likely

c6x: use early_init_dt_scan

2013-10-09T16:38:12+00:00

Convert c6x to use new early_init_dt_scan function.

Signed-off-by: Rob Herring 
Acked-by: Mark Salter 
Cc: Aurelien Jacquiot 
Cc: linux-c6x-dev@linux-c6x.org

c6x: use boot_command_line instead of private c6x_command_line

2013-10-09T16:37:27+00:00

Save some pointless copying of the kernel command line and just use
boot_command_line instead.

Also remove default_command_line as it is not referenced anywhere, and
the DT code already handles the default command line.

Signed-off-by: Rob Herring 
Tested-by: Mark Salter 
Acked-by: Mark Salter 
Cc: Aurelien Jacquiot 
Cc: linux-c6x-dev@linux-c6x.org
Reviewed-by: Grant Likely

of: consolidate definition of early_init_dt_alloc_memory_arch()

2013-08-28T20:18:32+00:00

Most architectures use the same implementation. Collapse the common ones
into a single weak function that can be overridden.

Signed-off-by: Grant Likely

of: Specify initrd location using 64-bit

2013-07-24T10:10:01+00:00

On some PAE architectures, the entire range of physical memory could reside
outside the 32-bit limit.  These systems need the ability to specify the
initrd location using 64-bit numbers.

This patch globally modifies the early_init_dt_setup_initrd_arch() function to
use 64-bit numbers instead of the current unsigned long.

There has been quite a bit of debate about whether to use u64 or phys_addr_t.
It was concluded to stick to u64 to be consistent with rest of the device
tree code. As summarized by Geert, "The address to load the initrd is decided
by the bootloader/user and set at that point later in time. The dtb should not
be tied to the kernel you are booting"

More details on the discussion can be found here:
https://lkml.org/lkml/2013/6/20/690
https://lkml.org/lkml/2012/9/13/544

Signed-off-by: Santosh Shilimkar 
Acked-by: Rob Herring 
Acked-by: Vineet Gupta 
Acked-by: Jean-Christophe PLAGNIOL-VILLARD 
Signed-off-by: Grant Likely