~thopiekar/emgd/+git/linux:yocto-3.4-emgd-1.14

Last commit made on 2012-07-17
Get this branch:
git clone -b yocto-3.4-emgd-1.14 https://git.launchpad.net/~thopiekar/emgd/+git/linux

Branch merges

Branch information

Name:
yocto-3.4-emgd-1.14
Repository:
lp:~thopiekar/emgd/+git/linux

Recent commits

86643bd... by Nitin A Kamble <email address hidden>

emgd/pvr: get it building with v3.4 kernel

Add emgd config option (DRM_EGD) and modify Makefiles for in-tree
builds.

rebased to v3.4 code

Fix build errors caused by changes to kernel interfaces introduced by
linux 3.2 such as:

error: 'THIS_MODULE' undeclared here (not in a function)

due to a missing THIS_MODULE definition which can be found in linux/export.h.

It also fixes a ream of errors like:

error: expected ')' before string constant

due to missing MODULE_PARM_DESC definition which can be found in
linux/moduleparam.h, included by linux/module.h, needed also for
MODULE_AUTHOR, etc.

variable name "pitch" from drm_framebuffer structure has changed
to "pitches" array in v3.4 kernel soruces.

avoid errors like these:
emgd_fbcon.c:128:28: error: 'struct drm_framebuffer' has no member named 'pitch'

Signed-off-by: Tom Zanussi <email address hidden>
Signed-off-by: Nitin A Kamble <email address hidden>

731a7a3... by Nitin A Kamble <email address hidden>

yocto/emgd: emgd 1.14 driver

The starting-point code that subsequent patches will modify. This is
a straight copy of the code in the emgd 1.14 emgd driver, specifically
IEMGD_HEAD_Linux/common/drm/emgd_drm.tgz from
LIN_IEMGD_1_14_GOLD_2443.tgz, the 'Linux Tar Ball' release downloaded
from http://edc.intel.com/Software/Downloads/EMGD/.

Signed-off-by: Nitin A Kamble <email address hidden>
Signed-off-by: Tom Zanussi <email address hidden>

7eb5fbf... by Bruce Ashfield <email address hidden>

kgit: creating baseline state

Signed-off-by: Bruce Ashfield <email address hidden>

f18a511... by Greg Kroah-Hartman <email address hidden>

Linux 3.4.1

3e5f29b... by Laxman Kumar Dewangan

i2c: tegra: notify transfer-complete after clearing status.

commit c889e91d2cc22123f20f40dde0c0a91856a20eea upstream.

The notification of the transfer complete by calling complete()
should be done after clearing all interrupt status.
This avoids the race condition of misconfigure the i2c controller
in multi-core environment.

Signed-off-by: Laxman Dewangan <email address hidden>
Acked-by: Stephen Warren <email address hidden>
Signed-off-by: Wolfram Sang <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

16d815f... by Marcus Folkesson <email address hidden>

i2c: davinci: Free requested IRQ in remove

commit 9868a060ccf769c08ec378a9829137e272e9a92c upstream.

The freed IRQ is not necessary the one requested in probe.
Even if it was, with two or more i2c-controllers it will fails anyway.

Signed-off-by: Marcus Folkesson <email address hidden>
Signed-off-by: Wolfram Sang <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

07e2c71... by Andi Kleen <email address hidden>

MCE: Fix vm86 handling for 32bit mce handler

commit a129a7c84582629741e5fa6f40026efcd7a65bd4 upstream.

When running on 32bit the mce handler could misinterpret
vm86 mode as ring 0. This can affect whether it does recovery
or not; it was possible to panic when recovery was actually
possible.

Fix this by always forcing vm86 to look like ring 3.

Signed-off-by: Andi Kleen <email address hidden>
Signed-off-by: Tony Luck <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

91aecc8... by Stephen Warren

ARM: dt: tegra cardhu: fix typo in SDHCI node name

commit 1dfebb426cfd16e2080f8c95e00ca2462f2325d4 upstream.

Cardhu's eMMC controller is on sdhci@78000600, not sdhci@78000400.
Fix the typo. This roughly doubles the IO performance, since the
support-8bit property actually takes effect.

Signed-off-by: Stephen Warren <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

8209f1c... by Dima Zavin <email address hidden>

ARM: 7409/1: Do not call flush_cache_user_range with mmap_sem held

commit 435a7ef52db7d86e67a009b36cac1457f8972391 upstream.

We can't be holding the mmap_sem while calling flush_cache_user_range
because the flush can fault. If we fault on a user address, the
page fault handler will try to take mmap_sem again. Since both places
acquire the read lock, most of the time it succeeds. However, if another
thread tries to acquire the write lock on the mmap_sem (e.g. mmap) in
between the call to flush_cache_user_range and the fault, the down_read
in do_page_fault will deadlock.

[will: removed drop of vma parameter as already queued by rmk (7365/1)]

Acked-by: Catalin Marinas <email address hidden>
Signed-off-by: Dima Zavin <email address hidden>
Signed-off-by: John Stultz <email address hidden>
Signed-off-by: Will Deacon <email address hidden>
Signed-off-by: Russell King <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

6019ae7... by Dima Zavin <email address hidden>

ARM: 7365/1: drop unused parameter from flush_cache_user_range

commit 4542b6a0fa6b48d9ae6b41c1efeb618b7a221b2a upstream.

vma isn't used and flush_cache_user_range isn't a standard macro that
is used on several archs with the same prototype. In fact only unicore32
has a macro with the same name (with an identical implementation and no
in-tree users).

This is a part of a patch proposed by Dima Zavin (with Message-id:
<email address hidden>) that didn't get
accepted.

Cc: Dima Zavin <email address hidden>
Acked-by: Catalin Marinas <email address hidden>
Signed-off-by: Uwe Kleine-König <email address hidden>
Signed-off-by: Russell King <email address hidden>
Cc: Will Deacon <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>