linux-toradex.git/arch/arm, branch v3.10.41

ARM: multi_v7_defconfig: enable ARM_ATAG_DTB_COMPAT

2014-05-31T04:52:12+00:00

commit a0396b9bd5a4a7baf598b60d2ca53c605c440a42 upstream.

Without this, legacy platforms that can boot with a multiplatform
kernel but that need the DTB to be appended, won't have a way to pass
firmware-set bootargs to the kernel.

This is needed to boot multi_v7_defconfig on snowball, for instance.

Signed-off-by: Olof Johansson 
Cc: Jason Cooper 
Cc: Kevin Hilman 
Signed-off-by: Greg Kroah-Hartman

arm: multi_v7_defconfig: Enable initrd/initramfs support

2014-05-31T04:52:12+00:00

commit c12d82b84353784f8233c28ee43cec0ac9fbd7d2 upstream.

Add CONFIG_BLK_DEV_INITRD to the defconfig to support
initramfs and initrd.

Signed-off-by: Soren Brinkmann 
Signed-off-by: Michal Simek 
Signed-off-by: Greg Kroah-Hartman

ARM: 7840/1: LPAE: don't reject mapping /dev/mem above 4GB

2014-05-13T11:59:41+00:00

commit 3159f372354e8e1f5dee714663d705dd2c7e0759 upstream.

With LPAE enabled, physical address space is larger than 4GB. Allow mapping any
part of it via /dev/mem by using PHYS_MASK to determine valid range.

PHYS_MASK covers 40 bits with LPAE enabled and 32 bits otherwise.

Reported-by: Vassili Karpov 
Signed-off-by: Sergey Dyasly 
Acked-by: Catalin Marinas 
Signed-off-by: Russell King 
Cc: hujianyang 
Signed-off-by: Greg Kroah-Hartman

ARM: 7728/1: mm: Use phys_addr_t properly for ioremap functions

2014-05-06T14:55:27+00:00

commit 9b97173e785a54c5df0aa23d1e1f680f61e36e43 upstream.

Several of the ioremap functions use unsigned long in places
resulting in truncation if physical addresses greater than
4G are passed in. Change the types of the functions and the
callers accordingly.

Cc: Krzysztof Halasa 
Cc: Arnd Bergmann 
Cc: Stephen Boyd 
Signed-off-by: Laura Abbott 
Signed-off-by: Russell King 
Cc: Wang Nan 
Signed-off-by: Greg Kroah-Hartman

ARM: mvebu: ensure the mdio node has a clock reference on Armada 370/XP

2014-05-06T14:55:27+00:00

commit a6e03dd451c724f785277d8ecca5d1a0b886d892 upstream.

The mvmdio driver accesses some register of the Ethernet unit. It
therefore takes a reference and enables a clock. However, on Armada
370/XP, no clock specification was given in the Device Tree, which
leads the mvmdio driver to fail when being used as a module and loaded
before the mvneta driver: it tries to access a register from a
hardware unit that isn't clocked.

Signed-off-by: Thomas Petazzoni 
Link: https://lkml.kernel.org/r/1395790439-21332-2-git-send-email-thomas.petazzoni@free-electrons.com
Acked-by: Andrew Lunn 
Acked-by: Gregory CLEMENT 
Signed-off-by: Jason Cooper 
Signed-off-by: Greg Kroah-Hartman

ARM: 8030/1: ARM : kdump : add arch_crash_save_vmcoreinfo

2014-05-06T14:55:27+00:00

commit 56b700fd6f1e49149880fb1b6ffee0dca5be45fb upstream.

For vmcore generated by LPAE enabled kernel, user space
utility such as crash needs additional infomation to
parse.

So this patch add arch_crash_save_vmcoreinfo as what PAE enabled
i386 linux does.

Reviewed-by: Will Deacon 
Signed-off-by: Liu Hua 
Signed-off-by: Russell King 
Signed-off-by: Greg Kroah-Hartman

ARM: 8027/1: fix do_div() bug in big-endian systems

2014-05-06T14:55:27+00:00

commit 80bb3ef109ff40a7593d9481c17de9bbc4d7c0e2 upstream.

In big-endian systems, "%1" get the most significant part of the value, cause the instruction to get the wrong result.

When viewing ftrace record in big-endian ARM systems, we found that
the timestamp errors:

swapper-0   [001] 1325.970000:   0:120:R ==> [001]    16:120:R events/1
events/1-16 [001] 1325.970000:   16:120:S ==> [001]    0:120:R swapper
swapper-0   [000] 1325.1000000:  0:120:R   + [000]    15:120:R events/0
swapper-0   [000] 1325.1000000:  0:120:R ==> [000]    15:120:R events/0
swapper-0   [000] 1326.030000:   0:120:R   + [000]  1150:120:R sshd
swapper-0   [000] 1326.030000:   0:120:R ==> [000]  1150:120:R sshd

When viewed ftrace records, it will call the do_div(n, base) function, which achieved arch/arm/include/asm/div64.h in. When n = 10000000, base = 1000000, in do_div(n, base) will execute "umull %Q0, %R0, %1, %Q2".

Reviewed-by: Dave Martin 
Reviewed-by: Nicolas Pitre 
Signed-off-by: Alex Wu 
Signed-off-by: Xiangyu Lu 
Signed-off-by: Russell King 
Signed-off-by: Greg Kroah-Hartman

ARM: 8007/1: Remove extraneous kcmp syscall ignore

2014-05-06T14:55:26+00:00

commit 95c52fe063351192e0f4ffb70ef9bac1aa26f5a4 upstream.

The kcmp system call was ported to ARM in
commit 3f7d1fe108dbaefd0c57a41753fc2c90b395f458
"ARM: 7665/1: Wire up kcmp syscall".

Fixes: 3f7d1fe108db ("ARM: 7665/1: Wire up kcmp syscall")
Signed-off-by: Christopher Covington 
Signed-off-by: Russell King 
Signed-off-by: Greg Kroah-Hartman

ARM: 7954/1: mm: remove remaining domain support from ARMv6

2014-05-06T14:55:26+00:00

commit b6ccb9803e90c16b212cf4ed62913a7591e79a39 upstream.

CPU_32v6 currently selects CPU_USE_DOMAINS if CPU_V6 and MMU. This is
because ARM 1136 r0pX CPUs lack the v6k extensions, and therefore do
not have hardware thread registers. The lack of these registers requires
the kernel to update the vectors page at each context switch in order to
write a new TLS pointer. This write must be done via the userspace
mapping, since aliasing caches can lead to expensive flushing when using
kmap. Finally, this requires the vectors page to be mapped r/w for
kernel and r/o for user, which has implications for things like put_user
which must trigger CoW appropriately when targetting user pages.

The upshot of all this is that a v6/v7 kernel makes use of domains to
segregate kernel and user memory accesses. This has the nasty
side-effect of making device mappings executable, which has been
observed to cause subtle bugs on recent cores (e.g. Cortex-A15
performing a speculative instruction fetch from the GIC and acking an
interrupt in the process).

This patch solves this problem by removing the remaining domain support
from ARMv6. A new memory type is added specifically for the vectors page
which allows that page (and only that page) to be mapped as user r/o,
kernel r/w. All other user r/o pages are mapped also as kernel r/o.
Patch co-developed with Russell King.

Signed-off-by: Will Deacon 
Signed-off-by: Russell King 
Signed-off-by: Greg Kroah-Hartman

ARM: dts: Keep G3D regulator always on for exynos5250-arndale

2014-05-06T14:55:26+00:00

commit bfeda827278f09f4db35877e5f1ca9c149ca2890 upstream.

Apparently, if G3D regulator is powered off, the SoC cannot enter low
power modes and just hangs. This patch fixes this by keeping the
regulator always on when the system is running, as suggested by Exynos 4
User's Manual in case of Exynos4210/4x12 SoCs (Exynos5250 UM does not
have such note, but observed behavior seems to confirm that it is true
for this SoC as well).

This fixes an issue preventing Arndale board from entering sleep mode
observed since commit

346f372f7b72a0 clk: exynos5250: Add CLK_IGNORE_UNUSED flag for pmu clock

that landed in kernel 3.10, which has fixed the clock driver to make the
SoC actually try to enter the sleep mode.

Signed-off-by: Tomasz Figa 
Acked-by: Kyungmin Park 
Tested-by: Tushar Behera 
Signed-off-by: Kukjin Kim 
Signed-off-by: Greg Kroah-Hartman