Linux 3.4.10 - 3.4.75

Signed-off-by: Lens-F <tnoah12@gmail.com>

Conflicts:
	Makefile
	arch/arm/include/asm/pgtable.h
	arch/arm/kernel/perf_event_v7.c
	arch/arm/kernel/smp.c
	arch/arm/kernel/stacktrace.c
	arch/arm/kernel/traps.c
	arch/arm/mach-imx/hotplug.c
	arch/arm/mm/dma-mapping.c
	arch/arm/vfp/vfpmodule.c
	arch/powerpc/platforms/85xx/p1022_ds.c
	arch/x86/boot/compressed/Makefile
	arch/x86/kernel/reboot.c
	block/elevator.c
	block/genhd.c
	block/scsi_ioctl.c
	drivers/ata/ata_piix.c
	drivers/base/power/runtime.c
	drivers/base/regmap/regmap-debugfs.c
	drivers/bluetooth/ath3k.c
	drivers/bluetooth/btusb.c
	drivers/char/hw_random/core.c
	drivers/char/random.c
	drivers/gpu/drm/i915/intel_lvds.c
	drivers/gpu/drm/radeon/atombios_crtc.c
	drivers/gpu/drm/radeon/atombios_encoders.c
	drivers/gpu/drm/radeon/evergreen.c
	drivers/gpu/drm/radeon/ni.c
	drivers/gpu/drm/radeon/radeon_asic.h
	drivers/gpu/drm/vmwgfx/vmwgfx_gmr.c
	drivers/hid/hid-core.c
	drivers/hid/hid-ids.h
	drivers/hid/usbhid/hid-core.c
	drivers/hid/usbhid/hid-quirks.c
	drivers/infiniband/ulp/srp/ib_srp.c
	drivers/input/joystick/xpad.c
	drivers/iommu/amd_iommu.c
	drivers/md/dm-crypt.c
	drivers/md/dm-ioctl.c
	drivers/md/dm-table.c
	drivers/md/dm.c
	drivers/media/video/gspca/gspca.c
	drivers/mfd/mfd-core.c
	drivers/mmc/card/block.c
	drivers/mmc/core/mmc.c
	drivers/mmc/host/sdhci.c
	drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c
	drivers/net/ethernet/smsc/smc91x.h
	drivers/net/macvtap.c
	drivers/net/tun.c
	drivers/net/usb/asix.c
	drivers/net/usb/qmi_wwan.c
	drivers/net/wireless/ath/ath9k/xmit.c
	drivers/net/wireless/rt2x00/rt2800usb.c
	drivers/remoteproc/Kconfig
	drivers/scsi/scsi.c
	drivers/scsi/scsi_error.c
	drivers/scsi/scsi_lib.c
	drivers/scsi/scsi_scan.c
	drivers/scsi/scsi_sysfs.c
	drivers/scsi/sd.c
	drivers/scsi/sd.h
	drivers/tty/n_tty.c
	drivers/tty/tty_io.c
	drivers/usb/class/cdc-acm.c
	drivers/usb/core/devices.c
	drivers/usb/core/devio.c
	drivers/usb/core/hub.c
	drivers/usb/core/quirks.c
	drivers/usb/core/urb.c
	drivers/usb/gadget/f_mass_storage.c
	drivers/usb/gadget/u_ether.c
	drivers/usb/host/ehci-hcd.c
	drivers/usb/host/ehci-hub.c
	drivers/usb/host/ehci-pci.c
	drivers/usb/host/pci-quirks.c
	drivers/usb/host/pci-quirks.h
	drivers/usb/host/xhci-hub.c
	drivers/usb/host/xhci-mem.c
	drivers/usb/host/xhci-pci.c
	drivers/usb/host/xhci-plat.c
	drivers/usb/host/xhci-ring.c
	drivers/usb/host/xhci.c
	drivers/usb/host/xhci.h
	drivers/usb/serial/cp210x.c
	drivers/usb/serial/ftdi_sio.c
	drivers/usb/serial/ftdi_sio_ids.h
	drivers/usb/serial/option.c
	drivers/usb/serial/qcserial.c
	drivers/usb/serial/ti_usb_3410_5052.c
	drivers/usb/serial/usb-serial.c
	drivers/usb/storage/scsiglue.c
	drivers/usb/storage/unusual_devs.h
	drivers/video/fbmem.c
	drivers/virtio/virtio_ring.c
	fs/buffer.c
	fs/cifs/cifs_unicode.c
	fs/cifs/cifsacl.c
	fs/cifs/cifsencrypt.c
	fs/cifs/cifssmb.c
	fs/cifs/connect.c
	fs/cifs/inode.c
	fs/cifs/sess.c
	fs/dcache.c
	fs/debugfs/inode.c
	fs/ecryptfs/file.c
	fs/ecryptfs/inode.c
	fs/ecryptfs/mmap.c
	fs/eventpoll.c
	fs/exec.c
	fs/ext4/Kconfig
	fs/ext4/balloc.c
	fs/ext4/ext4.h
	fs/ext4/ext4_jbd2.h
	fs/ext4/extents.c
	fs/ext4/ialloc.c
	fs/ext4/inode.c
	fs/ext4/mballoc.c
	fs/ext4/move_extent.c
	fs/ext4/namei.c
	fs/ext4/resize.c
	fs/ext4/super.c
	fs/ext4/xattr.c
	fs/fat/inode.c
	fs/fuse/fuse_i.h
	fs/fuse/inode.c
	fs/jbd2/commit.c
	fs/lockd/svc.c
	fs/locks.c
	fs/nfs/idmap.c
	fs/nfsd/nfsctl.c
	fs/nfsd/nfssvc.c
	fs/notify/inotify/inotify_user.c
	fs/select.c
	fs/splice.c
	fs/super.c
	fs/sysfs/dir.c
	fs/ubifs/dir.c
	fs/udf/super.c
	include/asm-generic/pgtable.h
	include/drm/drm_pciids.h
	include/linux/binfmts.h
	include/linux/cpu.h
	include/linux/efi.h
	include/linux/ftrace.h
	include/linux/ftrace_event.h
	include/linux/hrtimer.h
	include/linux/if_vlan.h
	include/linux/ipc_namespace.h
	include/linux/kernel-page-flags.h
	include/linux/kref.h
	include/linux/ktime.h
	include/linux/mm.h
	include/linux/mm_types.h
	include/linux/mmc/card.h
	include/linux/mmzone.h
	include/linux/moduleparam.h
	include/linux/mtd/nand.h
	include/linux/page-flags.h
	include/linux/posix_types.h
	include/linux/radix-tree.h
	include/linux/rculist.h
	include/linux/rculist_nulls.h
	include/linux/sched.h
	include/linux/skbuff.h
	include/linux/snmp.h
	include/linux/splice.h
	include/linux/swapops.h
	include/linux/time.h
	include/linux/usb.h
	include/linux/usb/ch9.h
	include/linux/usb/hcd.h
	include/linux/virtio.h
	include/linux/wait.h
	include/media/v4l2-ctrls.h
	include/net/cfg80211.h
	include/net/cipso_ipv4.h
	include/net/dst.h
	include/net/inetpeer.h
	include/net/ip.h
	include/net/ip_fib.h
	include/net/netfilter/nf_conntrack_ecache.h
	include/net/sock.h
	include/scsi/scsi_device.h
	include/sound/core.h
	include/sound/pcm.h
	include/trace/events/random.h
	init/main.c
	kernel/async.c
	kernel/audit_tree.c
	kernel/cgroup.c
	kernel/cpu.c
	kernel/events/core.c
	kernel/exit.c
	kernel/fork.c
	kernel/futex.c
	kernel/hrtimer.c
	kernel/irq/spurious.c
	kernel/module.c
	kernel/panic.c
	kernel/posix-cpu-timers.c
	kernel/power/suspend.c
	kernel/rcutree.c
	kernel/resource.c
	kernel/sched/core.c
	kernel/sched/sched.h
	kernel/smp.c
	kernel/sys.c
	kernel/time/clockevents.c
	kernel/time/tick-sched.c
	kernel/time/timekeeping.c
	kernel/timer.c
	kernel/trace/trace.c
	kernel/workqueue.c
	lib/dynamic_queue_limits.c
	lib/kobject.c
	lib/radix-tree.c
	lib/random32.c
	mm/memblock.c
	mm/mempolicy.c
	mm/migrate.c
	mm/mmap.c
	mm/mmu_notifier.c
	mm/oom_kill.c
	mm/page_alloc.c
	mm/pagewalk.c
	mm/shmem.c
	mm/vmscan.c
	net/bluetooth/sco.c
	net/core/datagram.c
	net/core/dev.c
	net/core/flow_dissector.c
	net/core/neighbour.c
	net/core/sock.c
	net/ipv4/af_inet.c
	net/ipv4/esp4.c
	net/ipv4/igmp.c
	net/ipv4/inetpeer.c
	net/ipv4/ip_fragment.c
	net/ipv4/ip_sockglue.c
	net/ipv4/raw.c
	net/ipv4/tcp.c
	net/ipv4/tcp_cubic.c
	net/ipv4/tcp_input.c
	net/ipv4/tcp_ipv4.c
	net/ipv4/tcp_output.c
	net/ipv4/udp.c
	net/ipv6/addrconf.c
	net/ipv6/datagram.c
	net/ipv6/ip6_input.c
	net/ipv6/ip6_output.c
	net/ipv6/mcast.c
	net/ipv6/ping.c
	net/ipv6/raw.c
	net/ipv6/reassembly.c
	net/ipv6/udp.c
	net/netfilter/nf_conntrack_core.c
	net/netfilter/nf_conntrack_expect.c
	net/netfilter/nf_conntrack_proto_tcp.c
	net/netfilter/xt_hashlimit.c
	net/netfilter/xt_limit.c
	net/netlink/af_netlink.c
	net/packet/af_packet.c
	net/sched/sch_htb.c
	net/socket.c
	net/sunrpc/xprt.c
	net/unix/af_unix.c
	net/wireless/core.c
	net/wireless/radiotap.c
	net/wireless/reg.c
	net/wireless/util.c
	net/xfrm/xfrm_user.c
	security/selinux/hooks.c
	sound/core/init.c
	sound/core/pcm_native.c
	sound/core/sound.c
	sound/pci/hda/patch_realtek.c
	sound/soc/soc-dapm.c
	sound/usb/card.h
	sound/usb/clock.c
	sound/usb/midi.c
	sound/usb/mixer.c
	sound/usb/pcm.c
	sound/usb/quirks-table.h
	tools/hv/hv_kvp_daemon.c
Linux 3.4.75 - 3.4.82

Signed-off-by: Lens-F <tnoah12@gmail.com>

Backend drivers shouldn't transistion to CLOSED unless the frontend is
CLOSED.  If a backend does transition to CLOSED too soon then the
frontend may not see the CLOSING state and will not properly shutdown.

So, treat an unexpected backend CLOSED state the same as CLOSING.

fs/file.c:fdtable: avoid triggering OOMs from alloc_fdmem

Recently due to a spike in connections per second memcached on 3
separate boxes triggered the OOM killer from accept.  At the time the
OOM killer was triggered there was 4GB out of 36GB free in zone 1.  The
problem was that alloc_fdtable was allocating an order 3 page (32KiB) to
hold a bitmap, and there was sufficient fragmentation that the largest
page available was 8KiB.

I find the logic that PAGE_ALLOC_COSTLY_ORDER can't fail pretty dubious
but I do agree that order 3 allocations are very likely to succeed.

There are always pathologies where order > 0 allocations can fail when
there are copious amounts of free memory available.  Using the pigeon
hole principle it is easy to show that it requires 1 page more than 50%
of the pages being free to guarantee an order 1 (8KiB) allocation will
succeed, 1 page more than 75% of the pages being free to guarantee an
order 2 (16KiB) allocation will succeed and 1 page more than 87.5% of
the pages being free to guarantee an order 3 allocate will succeed.

A server churning memory with a lot of small requests and replies like
memcached is a common case that if anything can will skew the odds
against large pages being available.

Therefore let's not give external applications a practical way to kill
linux server applications, and specify __GFP_NORETRY to the kmalloc in
alloc_fdmem.  Unless I am misreading the code and by the time the code
reaches should_alloc_retry in __alloc_pages_slowpath (where
__GFP_NORETRY becomes signification).  We have already tried everything
reasonable to allocate a page and the only thing left to do is wait.  So
not waiting and falling back to vmalloc immediately seems like the
reasonable thing to do even if there wasn't a chance of triggering the
OOM killer.

mac80211: fix fragmentation code, particularly for encryption

The "new" fragmentation code (since my rewrite almost 5 years ago)
erroneously sets skb->len rather than using skb_trim() to adjust
the length of the first fragment after copying out all the others.
This leaves the skb tail pointer pointing to after where the data
originally ended, and thus causes the encryption MIC to be written
at that point, rather than where it belongs: immediately after the
data.

The impact of this is that if software encryption is done, then
 a) encryption doesn't work for the first fragment, the connection
    becomes unusable as the first fragment will never be properly
    verified at the receiver, the MIC is practically guaranteed to
    be wrong
 b) we leak up to 8 bytes of plaintext (!) of the packet out into
    the air

This is only mitigated by the fact that many devices are capable
of doing encryption in hardware, in which case this can't happen
as the tail pointer is irrelevant in that case. Additionally,
fragmentation is not used very frequently and would normally have
to be configured manually.

Fix this by using skb_trim() properly.

s390/dump: Fix dump memory detection

Dumps created by kdump or zfcpdump can contain invalid memory holes when
dumping z/VM systems that have memory pressure.

For example:

   # zgetdump -i /proc/vmcore.
   Memory map:
   0000000000000000 - 0000000000bfffff (12 MB)
   0000000000e00000 - 00000000014fffff (7 MB)
   000000000bd00000 - 00000000f3bfffff (3711 MB)

The memory detection function find_memory_chunks() issues tprot to
find valid memory chunks. In case of CMM it can happen that pages are
marked as unstable via set_page_unstable() in arch_free_page().
If z/VM has released that pages, tprot returns -EFAULT and indicates
a memory hole.

So fix this and switch off CMM in case of kdump or zfcpdump.

s390: fix kernel crash due to linkage stack instructions

The kernel currently crashes with a low-address-protection exception
if a user space process executes an instruction that tries to use the
linkage stack. Set the base-ASTE origin and the subspace-ASTE origin
of the dispatchable-unit-control-table to point to a dummy ASTE.
Set up control register 15 to point to an empty linkage stack with no
room left.

A user space process with a linkage stack instruction will still crash
but with a different exception which is correctly translated to a
segmentation fault instead of a kernel oops.

spi: Fix crash with double message finalisation on error handling

It causes a NULL pointer dereference with drivers using the generic
spi_transfer_one_message(), which always calls
spi_finalize_current_message(), which zeroes master->cur_msg.

Drivers implementing transfer_one_message() theirselves must always call
spi_finalize_current_message(), even if the transfer failed:

 * @transfer_one_message: the subsystem calls the driver to transfer a single
 *      message while queuing transfers that arrive in the meantime. When the
 *      driver is finished with this message, it must call
 *      spi_finalize_current_message() so the subsystem can issue the next
 *      transfer

bind_get() checks the device number it is called with. It uses
MAX_RAW_MINORS for the upper bound. But MAX_RAW_MINORS is set at compile
time while the actual number of raw devices can be set at runtime. This
means the test can either be too strict or too lenient. And if the test
ends up being too lenient bind_get() might try to access memory beyond
what was allocated for "raw_devices".

If an NFS client attempts to get a lock (using NLM) and the lock is
not available, the server will remember the request and when the lock
becomes available it will send a GRANT request to the client to
provide the lock.

If the client already held an adjacent lock, the GRANT callback will
report the union of the existing and new locks, which can confuse the
client.

This happens because __posix_lock_file (called by vfs_lock_file)
updates the passed-in file_lock structure when adjacent or
over-lapping locks are found.

To avoid this problem we take a copy of the two fields that can
be changed (fl_start and fl_end) before the call and restore them
afterwards.
An alternate would be to allocate a 'struct file_lock', initialise it,
use locks_copy_lock() to take a copy, then locks_release_private()
after the vfs_lock_file() call.  But that is a lot more work.

The code for deconding the modem status to the internal linux
presentation in gsm_process_modem has already a big comment about
this 2 or 3 byte length thing and it is already able to decode the
brk, but the code calling the gsm_process_modem function in
gsm_control_modem does not encode it and hand it over the right way.
This patch fixes this.
Without this fix if the modem sends the brk byte in it's modem status
control message the driver will hang when opening a muxed channel.

The Cypress ATACB unusual-devs entry for the Super Top SATA bridge
causes problems.  Although it was originally reported only for
bcdDevice = 0x160, its range was much larger.  This resulted in a bug
report for bcdDevice 0x220, so the range was capped at 0x219.  Now
Milan reports errors with bcdDevice 0x150.

Modpost: fixed USB alias generation for ranges including 0x9 and 0xA

Unfortunately, the commit didn't fix the case when the range includes both
0x9 and 0xA, meaning that the final range must look like [x-9A-y] where
x <= 0x9 and y >= 0xA -- instead the [x-9A-x] range was produced.

Modprobe doesn't complain as it sees no difference between no-match and
bad-pattern results of fnmatch().

Fixing this simple bug to fix the aliases.
Also changing the hardcoded beginning of the range to uppercase as all the
other letters are also uppercase in the device version numbers.

When mkfs issues a full device discard and the device only
supports discards of a smallish size, we can loop in
blkdev_issue_discard() for a long time. If preempt isn't enabled,
this can turn into a softlock situation and the kernel will
start complaining.

Add an explicit cond_resched() at the end of the loop to avoid
that.

Research has shown that commit a77fcf895046 ("IB/qib: Use a single
txselect module parameter for serdes tuning") missed a key serdes init
sequence.
Subsystems that want to register CPU hotplug callbacks, as well as perform
initialization for the CPUs that are already online, often do it as shown
below:

	get_online_cpus();

	for_each_online_cpu(cpu)
		init_cpu(cpu);

	register_cpu_notifier(&foobar_cpu_notifier);

	put_online_cpus();

This is wrong, since it is prone to ABBA deadlocks involving the
cpu_add_remove_lock and the cpu_hotplug.lock (when running concurrently
with CPU hotplug operations).

Interestingly, the raid5 code can actually prevent double initialization and
hence can use the following simplified form of callback registration:

	register_cpu_notifier(&foobar_cpu_notifier);

	get_online_cpus();

	for_each_online_cpu(cpu)
		init_cpu(cpu);

	put_online_cpus();

A hotplug operation that occurs between registering the notifier and calling
get_online_cpus(), won't disrupt anything, because the code takes care to
perform the memory allocations only once.

So reorganize the code in raid5 this way to fix the deadlock with callback
registration.

When compiling for the IA-64 ski emulator, HZ is set to 32 because the
emulation is slow and we don't want to waste too many cycles processing
timers. Alpha also has an option to set HZ to 32.

This causes integer underflow in
kernel/time/jiffies.c:
kernel/time/jiffies.c:66:2: warning: large integer implicitly truncated to unsigned type [-Woverflow]
  .mult  = NSEC_PER_JIFFY << JIFFIES_SHIFT, /* details above */
  ^

Fix NULL pointer dereference of "chip->pdata" if platform_data was not
supplied to the driver.

The driver during probe stored the pointer to the platform_data:
	chip->pdata = client->dev.platform_data;
Later it was dereferenced in max17040_get_online() and
max17040_get_status().

If platform_data was not supplied, the NULL pointer exception would
happen:

[    6.626094] Unable to handle kernel  of a at virtual address 00000000
[    6.628557] pgd = c0004000
[    6.632868] [00000000] *pgd=66262564
[    6.634636] Unable to handle kernel paging request at virtual address e6262000
[    6.642014] pgd = de468000
[    6.644700] [e6262000] *pgd=00000000
[    6.648265] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
[    6.653552] Modules linked in:
[    6.656598] CPU: 0 PID: 31 Comm: kworker/0:1 Not tainted 3.10.14-02717-gc58b4b4 #505
[    6.664334] Workqueue: events max17040_work
[    6.668488] task: dfa11b80 ti: df9f6000 task.ti: df9f6000
[    6.673873] PC is at show_pte+0x80/0xb8
[    6.677687] LR is at show_pte+0x3c/0xb8
[    6.681503] pc : [<c001b7b8>]    lr : [<c001b774>]    psr: 600f0113
[    6.681503] sp : df9f7d58  ip : 600f0113  fp : 00000009
[    6.692965] r10: 00000000  r9 : 00000000  r8 : dfa11b80
[    6.698171] r7 : df9f7ea0  r6 : e6262000  r5 : 00000000  r4 : 00000000
[    6.704680] r3 : 00000000  r2 : e6262000  r1 : 600f0193  r0 : c05b3750
[    6.711194] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
[    6.718485] Control: 10c53c7d  Table: 5e46806a  DAC: 00000015
[    6.724218] Process kworker/0:1 (pid: 31, stack limit = 0xdf9f6238)
[    6.730465] Stack: (0xdf9f7d58 to 0xdf9f8000)
[    6.914325] [<c001b7b8>] (show_pte+0x80/0xb8) from [<c047107c>] (__do_kernel_fault.part.9+0x44/0x74)
[    6.923425] [<c047107c>] (__do_kernel_fault.part.9+0x44/0x74) from [<c001bb7c>] (do_page_fault+0x2c4/0x360)
[    6.933144] [<c001bb7c>] (do_page_fault+0x2c4/0x360) from [<c0008400>] (do_DataAbort+0x34/0x9c)
[    6.941825] [<c0008400>] (do_DataAbort+0x34/0x9c) from [<c000e5d8>] (__dabt_svc+0x38/0x60)
[    6.950058] Exception stack(0xdf9f7ea0 to 0xdf9f7ee8)
[    6.955099] 7ea0: df0c1790 00000000 00000002 00000000 df0c1794 df0c1790 df0c1790 00000042
[    6.963271] 7ec0: df0c1794 00000001 00000000 00000009 00000000 df9f7ee8 c0306268 c0306270
[    6.971419] 7ee0: a00f0113 ffffffff
[    6.974902] [<c000e5d8>] (__dabt_svc+0x38/0x60) from [<c0306270>] (max17040_work+0x8c/0x144)
[    6.983317] [<c0306270>] (max17040_work+0x8c/0x144) from [<c003f364>] (process_one_work+0x138/0x440)
[    6.992429] [<c003f364>] (process_one_work+0x138/0x440) from [<c003fa64>] (worker_thread+0x134/0x3b8)
[    7.001628] [<c003fa64>] (worker_thread+0x134/0x3b8) from [<c00454bc>] (kthread+0xa4/0xb0)
[    7.009875] [<c00454bc>] (kthread+0xa4/0xb0) from [<c000eb28>] (ret_from_fork+0x14/0x2c)
[    7.017943] Code: e1a03005 e2422480 e0826104 e59f002c (e7922104)
[    7.024017] ---[ end trace 73bc7006b9cc5c79 ]---

Each sub-buffer (buffer page) has a full 64 bit timestamp. The events on
that page use a 27 bit delta against that timestamp in order to save on
bits written to the ring buffer. If the time between events is larger than
what the 27 bits can hold, a "time extend" event is added to hold the
entire 64 bit timestamp again and the events after that hold a delta from
that timestamp.

As a "time extend" is always paired with an event, it is logical to just
allocate the event with the time extend, to make things a bit more efficient.

Unfortunately, when the pairing code was written, it removed the "delta = 0"
from the first commit on a page, causing the events on the page to be
slightly skewed.

In allmodconfig builds for sparc and any other arch which does
not set CONFIG_SPARSE_IRQ, the following will be seen at modpost:

  CC [M]  lib/cpu-notifier-error-inject.o
  CC [M]  lib/pm-notifier-error-inject.o
ERROR: "irq_to_desc" [drivers/gpio/gpio-mcp23s08.ko] undefined!
make[2]: *** [__modpost] Error 1

This happens because commit 3911ff30f5 ("genirq: export
handle_edge_irq() and irq_to_desc()") added one export for it, but
there were actually two instances of it, in an if/else clause for
CONFIG_SPARSE_IRQ.  Add the second one.

Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Jiri Kosina <jkosina@suse.cz>
Link: http://lkml.kernel.org/r/1392057610-11514-1-git-send-email-paul.gortmaker@windriver.com
msm: kgsl: Add an input handler to power up the GPU on a touch event

On a device where the primary input is a touchscreen nobody is
surprised that touch events are often the catalyst for drawing
frames. If the GPU is in slumber we can get a jump on the action
by watching for touch events and turning the GPU on in anticipation
of a draw call. Register for events from all input drivers
returning EV_ABS events and queue a work task to power up the GPU
if it is currently in slumber.

Signed-off-by: Lens-F <tnoah12@gmail.com>

Conflicts:
	drivers/gpu/msm/adreno.c
	drivers/gpu/msm/adreno.h
	drivers/gpu/msm/adreno_ringbuffer.c
	drivers/gpu/msm/kgsl_device.h
sched: max cost

Signed-off-by: Lens-F <tnoah12@gmail.com>
AIO,SCHED,CHROMIUM,SELINUX,WRITEBACK, and SOFTIRQ adjustments

Signed-off-by: Lens-F <tnoah12@gmail.com>
mm: frontswap: cleanup, fixes, and adjustments

Signed-off-by: Lens-F <tnoah12@gmail.com>