n801x: Whitespace cleanup for GPS building

Change-Id: I602a49e54c507a5dc01e0f4639dbf6930bc9cc2d
[2/2] smdk4412: Remove exFAT

To be replaced with FUSE based exFAT implementation

Change-Id: Ie1d9590f605538f44b24628a89187eac4e945273
defconfigs: Rename n8013 to n801x

Change-Id: I9122292f8dcb6b909e2a47fc5aefeec0c9587da6
defconfigs: Disable keyboard dock driver for Note 10.1 devices

This driver always reports itself as present even when the keyboard
is not.  This causes the software keyboard to be disabled.  Almost no
one has this accessory anyway - so disable it until someone who
actually has a keyboard to test with can fix this broken driver.

Change-Id: I5b5350d01b77da63d915004b6d525088ca74e0f7
mach-p4notepq: Fix build when SEC_KEYBOARD_DOCK is disabled

Change-Id: I64d65a24060969926cae330c161216e37f9c0923
n80xx: Add missing components from I9300 update12 display merge

Change-Id: I5da7d1a90999f08346f3df783f1fb31470bccb26
mach-u1: Fix building issues after display patches

It fixed building for smdk4210 family after merging in
I5da7d1a90999f08346f3df783f1fb31470bccb26

Change-Id: Ia07292f105fc3a5df2d38a4088a85f55f4bfdfa7
mach-u1: Fix building for i9100

I broke it with Ia07292f105fc3a5df2d38a4088a85f55f4bfdfa7

Change-Id: Ifb7c7f199af31bde47ba3edef8360e1ac3fd3e86
defconfigs: Regenerate to sync up with current Kconfig setup

Change-Id: Ie2943611d5cc17baeba797ca7cb5ce8cda3459a0
Revert out display patches that broke the 4210 family

I screwed up royally by not adding other 4210ers to the review
for that big 4412 display patch.

As a result, 4210s are in bad shape.  Revert the partial fix attempts
and the patch that broke everything, and we'll redo this again with
proper review.

I got back from vacation 3 weeks ago and I already need another one,
this is clear evidence of it.  :(

Revert "mach-u1: Fix building for i9100"

This reverts commit 128d8d86e9308b6fab6106cf12c6ee1697b81571.

Revert "mach-u1: Fix building issues after display patches"

This reverts commit 6765f1bc45f4e0bdd52667e2ac29a5c22d76c322.

Revert "n80xx: Add missing components from I9300 update12 display merge"

This reverts commit f5131eb7b8b1a2501dc34b5c759b04306553ff41.

Change-Id: I3ab1f0a6c11ad918beff1d2202b244286d6d6d95
Finish merging in I9300 update12 display components

was: n80xx: Add missing components from I9300 update12 display merge

However, it clearly impacts way more than n80xx, and last time we tried
this we forgot to add more 4210 users for review.

Time to try this again with more time taken...

PS2: Squash the following changesets into this patch.

mach-u1: Fix building issues after display patches
mach-u1: Fix building for i9100

PS3: Fix build for n7000, remove midas-lcd.h.

Change-Id: I612769a24b16b84528cca3fccfc6a8778087315e
i9100/i777: Fix default paneldata

The default paneldata in the I9300 update12 source is wrong for the devices
we support, and in fact, in the process of merging it, we wound up creating
uninitialized default data.  This resulted in the kernel crashing when
ld9040.get_lcdtype was 0x0

Instead, use u1_panel_pdata from panel-u1.c like the pre-update12 kernel
as our default.

Change-Id: I22cc5b685f1907e79975e1cdd48c5fb61383172c
Signed-off-by: Andrew Dodd <atd7@cornell.edu>
smdk4412: Provide available freq sysfs for exynos.

Needed for the frequency slider in Performance Settings to work properly.

Change-Id: If01258234d216a1ee37fb7b090c012b3d6cd09be
smdk4412: add support for Galaxy Note 8 (N5110 and N5100)

Change-Id: I65dbba8d998ffceec77ad5458e1f12771a75446b
smdk4412: Boeffla Sound 1.6.5

Change-Id: I05aed9e86a5ddc8eb917e253afa1768dda79f089
config: update local version

update local build reference name to OMNI

Signed-off-by: Humberto Borba <humberos@gmail.com>
Change-Id: I60963de1e22e777d46f1f0c21d61cf3e2ecb21dd
Fix smdk4412 kernel compilation with Linaro 4.10
smdk4412: sound: update soc & codecs

Change-Id: Ia4f8e7ba69b27a241f202f3218d1b163d9c6879b
Revert "smdk4412: sound: update soc & codecs"

One:  Despite claiming to be a sound commit, this contains changes outside of sound/soc - WTF?

Two: Despite containing no changes for mc1n2 compared to Samsung's baseline, mc1n2 drivers were merely copypastaed on top of the current one, reverting out all of our own changes (such as I777 micswap support)

This is a candidate for complete revert unless someone can explain to me why a sound commit is dicking around with cpufreq and we can also determine whether any other fixes were clobbered by this patch.

This reverts commit 084c4ed422875e4f64f4fe362f30a06750641f36.

Change-Id: I3d14b083692f821e5523b61b972ae5f68a5775bc
n_tty: Fix n_tty_write crash when echoing in raw mode

The tty atomic_write_lock does not provide an exclusion guarantee for
the tty driver if the termios settings are LECHO & !OPOST.  And since
it is unexpected and not allowed to call TTY buffer helpers like
tty_insert_flip_string concurrently, this may lead to crashes when
concurrect writers call pty_write. In that case the following two
writers:
* the ECHOing from a workqueue and
* pty_write from the process
race and can overflow the corresponding TTY buffer like follows.

If we look into tty_insert_flip_string_fixed_flag, there is:
  int space = __tty_buffer_request_room(port, goal, flags);
  struct tty_buffer *tb = port->buf.tail;
  ...
  memcpy(char_buf_ptr(tb, tb->used), chars, space);
  ...
  tb->used += space;

so the race of the two can result in something like this:
              A                                B
__tty_buffer_request_room
                                  __tty_buffer_request_room
memcpy(buf(tb->used), ...)
tb->used += space;
                                  memcpy(buf(tb->used), ...) ->BOOM

B's memcpy is past the tty_buffer due to the previous A's tb->used
increment.

Since the N_TTY line discipline input processing can output
concurrently with a tty write, obtain the N_TTY ldisc output_lock to
serialize echo output with normal tty writes.  This ensures the tty
buffer helper tty_insert_flip_string is not called concurrently and
everything is fine.

Note that this is nicely reproducible by an ordinary user using
forkpty and some setup around that (raw termios + ECHO). And it is
present in kernels at least after commit
d945cb9cce20ac7143c2de8d88b187f62db99bdc (pty: Rework the pty layer to
use the normal buffering logic) in 2.6.31-rc3.

js: add more info to the commit log
js: switch to bool
js: lock unconditionally
js: lock only the tty->ops->write call

References: CVE-2014-0196
Reported-and-tested-by: Jiri Slaby <jslaby@suse.cz>
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: <stable@vger.kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[bwh: Backported to 3.4: output_lock is a member of struct tty_struct]

Change-Id: I9530780b811e0ce9b0216e943822210b3131a8d6