usb: ehci-msm2: Fix controller autosuspend

When the EHCI controller is removed using platform_device_del(),
the PM disable_depth counter is decremented once by the driver
core. Thus the driver's remove callback additionally calling
pm_runtime_disable() is leading to an unbalanced counter since
pm_runtime_enable() call happens only once when platform_device_add()
calls the probe callback. Fix this by removing the extraneous
pm_runtime_disable().

Change-Id: Ie76256ac50ba65022814285bf57feca109f79d6b
Signed-off-by: Jack Pham <jackp@codeaurora.org>
usb: ehci-msm2: Fix unbalanced clock warning

The EHCI controller may be in suspend state in which its clocks
are already disabled. Fix warning given by clock subsystem when
disabling the clocks a second time when the controller's platform
device is removed by first checking if the device is suspended.

Change-Id: I3c491d0db11cc172d0e6779042c04fc726936b36
Signed-off-by: Jack Pham <jackp@codeaurora.org>
ASoC: wcd9xxx: Fix mclk bit setting in codec probe

WCD9320 supports different master clock rates. Modify the
bits required for master clock alone. This is required to
avoid overwriting other bits in chip control register set
in default register settings.

Change-Id: Id14cce2a404ca2d03121dad8c3eac2ebec433e47
Signed-off-by: Venkat Sudhir <vsudhir@codeaurora.org>
EHCI: HSIC: Fix a race between root hub resume and controller removal

The pm_qos request is removed before unregistering the HCD in remove
function. If root hub resume runs in parallel, there is a possibility
of adding the pm_qos request back to the active list. The pm_qos request
memory is freed after unregistering the HCD and this would lead to
pm_qos list corruption. A crash is observed when another driver is
submitting a pm_qos request after HSIC controller is removed during
shutdown.  Remove HCD prior to releasing controller resources.

CRs-Fixed: 444928
Change-Id: Iaed6964e7d4245b8ae6c295ed6c76f5a9d32e20f
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
ata: ahci: Fix re-entrancy in suspend routines

If the AHCI controller is already runtime suspended,
do not try to suspend again during platform suspend.
During resume activate the device and update the
runtime PM status to reflect the actual post-system
sleep status.

CRs-Fixed: 449549
Change-Id: I006e7427317df48e368762e4f56010541f4010e5
Signed-off-by: Sujit Reddy Thumma <sthumma@codeaurora.org>
power: pm8921-charger: fix a potential array out of bound access

There is a potential out of bound array access to find the
max adjustment value for battery current. Fix it.

Change-Id: I73856b7cdc85204e501b33b3412490148867576e
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
include: mmc: Export sanitized mmc headers

Export sanitized mmc.h and core.h for userspace.

Change-Id: I3a6eadde2023d974b0ce260a77082b01d8ba0b5d
Signed-off-by: Venkat Gopalakrishnan <venkatg@codeaurora.org>
scripts: gcc-wrapper: Add extents.c to allowed warning list

With gcc-4.5.3 compiler, we get the error:
In function 'ext4_ext_map_blocks':
kernel/fs/ext4/extents.c:2091:24:
warning: 'cex.ec_start' may be used uninitialized in this function

Change-Id: I460abf305a725deb3c3b06582518f8cd35314385
Signed-off-by: Rohit Vaswani <rvaswani@codeaurora.org>
include: linux: Export santized ioprio header

Export sanitized ioprio.h for userspace.

Change-Id: Ifec6bc6b539c84fcba27751d4ac0de03458cd131
Signed-off-by: Venkat Gopalakrishnan <venkatg@codeaurora.org>
Merge "ASoC: wcd9xxx: Fix mclk bit setting in codec probe"
Merge "power: pm8921-charger: fix a potential array out of bound access"
Merge "include: mmc: Export sanitized mmc headers"
Merge "include: linux: Export santized ioprio header"
Merge "scripts: gcc-wrapper: Add extents.c to allowed warning list"
ARM: dma-mapping: add support for CMA regions placed in highmem zone

This patch adds missing pieces to correctly support memory pages served
from CMA regions placed in high memory zones. Please note that the default
global CMA area is still put into lowmem and is limited by optional
architecture specific DMA zone. One can however put device specific CMA
regions in high memory zone to reduce lowmem usage.

Change-Id: I92ae4a772f24e0ca90c5560a826207850618b506
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
[lauraa@codeaurora.org: Context fixups]
Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
ARM: dma-mapping: Allow highmem pages to not have a mapping

The DMA_ATTR_NO_KERNEL_MAPPING is used to make sure that CMA
pages have no kernel mapping. Add support to make sure that
highmem pages have no mapping.

Change-Id: Ife76df126ecfedf0dba81a35e0de8a1787355b3d
Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
power: pm8921-bms: correct even after faking 100%

The current driver restores the OCV to the max voltage when the
BMS is in a mode where it fakes 100%.

This erases any corrections done to the OCV. Fix it by
forcing the OCV to max voltage just once right after charging
is done with a full battery.

Change-Id: Ibcbc20386e7932fe25d8152943be409397353988
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
msm: smd_pkt: Add new devices for femtocell

Add SMD PKT ports required for testing, logging, and data communication
on femtocell targets.

Change-Id: Ie5b0e2dc3055c9f253f358c08e2fed33cec06c5a
Signed-off-by: Eric Holmberg <eholmber@codeaurora.org>
Merge "msm: smd_pkt: Add new devices for femtocell"
media: dvb: mpq: Limit number of TS packets on secure demux input

Limit number of TS packets available to secure demux for processing
in any single processing session. This is done in order to prevent
large input buffer that require a long processing time and may cause
latency and overflow situations.
The limit can be fine-tuned as it is a module parameter.

Change-Id: I36f007da1b8152be27885ba4674bf42e6eb86ffa
Signed-off-by: Gilad Broner <gbroner@codeaurora.org>