ASoC: wcd9xxx: Fix RX Ear register gain values

Rx Ear Gain register on WCD9306 supports different gain
values from 6DB to -12DB. It was wrongly configured with
2DB. This change fixes the issue and adds support for
correct gain values for Ear PA Gain.

CRs-Fixed: 520688
Change-Id: I6493cf63a1d36d9c9c0a3086b645b92f8c3de588
Signed-off-by: Venkat Sudhir <vsudhir@codeaurora.org>
Merge "netfilter: x_tables: fix ordering of jumpstack allocation and table update"
Merge "ASoC: wcd9xxx: Fix RX Ear register gain values"
radio: iris: Bound check user space values

There is no bound check for arguments passed
from user space to kernel space. This may cause
fatal exceptions.

Change-Id: I944e8e5d6e3b12b75df4e6cee7887075237b4411
CRs-Fixed: 546081
Signed-off-by: Ayaz Ahmad <aahmad@codeaurora.org>
Merge "kernel: alarm: Do not call rtc_alarm_irq_enable in IRQ Disabled context"
msm: rpm-smd: use data type correctly for a variable

Change variable data type from signed int to unsigned int.

CRs-fixed: 556055
Change-Id: I6bb363b31d4fab26d84f89e775101c6051fe9e10
Signed-off-by: Anil kumar mamidala <amami@codeaurora.org>
Bluetooth: HID: Add support for building hid drivers

This patch adds support for enabling uhid driver in kernel which
provides interface for user space hid module to interact with
hid drivers of kernel. Without support for uhid driver, Bluetooth
HID functionality is broken completely. Also support for Microsoft
and Elecom hid drivers is enabled so that HID profile can be
connected with these HID devices.

Change-Id: If56742a9c6b6c4ef774da6e83d57aee56bf28842
CRs-Fixed: 553571
Signed-off-by: Hemant Gupta <hemantg@codeaurora.org>
Merge "Merge "kernel: alarm: Do not call rtc_alarm_irq_enable in IRQ Disabled context""
Merge "mmc: sdhci: do not use maximum timeout for all cards"
Merge "msm:qdsp6v2: Check null pointer on userspace data argument in kernel"
Merge "mmc: card: fix arbitrary write via read handler in mmc_block_test"
msm: wfd:Wait for one more vsync cycle, if VSG running out of input frames

If VSG running out of input frames, it will re-encode previous frames.
With this change, instead of encoding pervious frame VSG will push timer to
half of capturing frame rate. If it find new frame, it will be encoded
Otherwise will re-encode previous frame.

CRs-Fixed: 571771
Change-Id: Ie1c970b4e251c2165e77134b746c4ee0e3a90fba
Signed-off-by: Srinu Gorle <sgorle@codeaurora.org>
ARM: dts: msm: Update 8974Pro PVS table to config v1

Update 2.5GHz and 2.3GHz RC1 tables to latest voltage plan.
Added PVS config version property.

Change-Id: I7344e81485246191c518f7d644c401ca1934e800
Signed-off-by: Junjie Wu <junjiew@codeaurora.org>
ARM: dts: msm: update ldo-delta to 12.5mV for 8084 and 8974pro devices

Recent characterization data has indicated that the ldo-delta
value should be 12.5mV for apq8084 and msm8974pro.

Set the ldo-delta to 12.5mV for them.

Change-Id: Ic300940fd253e7b1a5e9effe222a94a26b1675ca
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
Merge "ARM: dts: msm: Update 8974Pro PVS table to config v1"
Merge "ARM: dts: msm: update ldo-delta to 12.5mV for 8084 and 8974pro devices"
ext4: make sure the journal sb is written in ext4_clear_journal_err()

After we transfer set the EXT4_ERROR_FS bit in the file system
superblock, it's not enough to call jbd2_journal_clear_err() to clear
the error indication from journal superblock --- we need to call
jbd2_journal_update_sb_errno() as well.  Otherwise, when the root file
system is mounted read-only, the journal is replayed, and the error
indicator is transferred to the superblock --- but the s_errno field
in the jbd2 superblock is left set (since although we cleared it in
memory, we never flushed it out to disk).

This can end up confusing e2fsck.  We should make e2fsck more robust
in this case, but the kernel shouldn't be leaving things in this
confused state, either.

Change-Id: I7a7cd58880209fbd54f4ded5f2b62de492cae9e0
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: stable@kernel.org
Git-commit: d796c52ef0b71a988364f6109aeb63d79c5b116b
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: Osvaldo Banuelos <osvaldob@codeaurora.org>
ext4: fix memory leak in xattr

If we take the 2nd retry path in ext4_expand_extra_isize_ea, we
potentionally return from the function without having freed these
allocations.  If we don't do the return, we over-write the previous
allocation pointers, so we leak either way.

Spotted with Coverity.

[ Fixed by tytso to set is and bs to NULL after freeing these
  pointers, in case in the retry loop we later end up triggering an
  error causing a jump to cleanup, at which point we could have a double
  free bug. -- Ted ]

Change-Id: I49b8ca41a6c6d44b563eb23306870258a3affd3b
Signed-off-by: Dave Jones <davej@fedoraproject.org>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
Cc: stable@vger.kernel.org
Git-commit: 6e4ea8e33b2057b85d75175dd89b93f5e26de3bc
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: Osvaldo Banuelos <osvaldob@codeaurora.org>
ASoC: dapm: Fix race condition in dapm

Dirty widget list can be accessed by multiple
paths in dapm framework. Dirty list is protected by
dapm mutex. Since stream_event function accesses the dirty list,
it should acquire dapm mutex instead of codec mutex.

CRs-fixed: 593141, 596103
Change-Id: I9f41bf436b41ba9b4fa3bb447035fd1fe262e76b
Signed-off-by: Gopikrishnaiah Anandan <agopik@codeaurora.org>
Merge "Merge "Merge "kernel: alarm: Do not call rtc_alarm_irq_enable in IRQ Disabled context"""