diag: dci: Do not update status if DCI support is not present

If same command is registered on multiple peripherals then
diag driver is returning wrong error status to client while
traversing the registration table. This patch does not update
the error status if DCI support is not present on that
peripheral.

CRs-Fixed: 683796
Change-Id: Ib0f7eb6e910998f616fd4105df0428ec59c334e5
Signed-off-by: Mohit Aggarwal <maggarwa@codeaurora.org>
Merge "diag: dci: Do not update status if DCI support is not present"
Merge "Merge "diag: dci: Do not update status if DCI support is not present""
Merge e421bd44ae37d6a0386485ba266cd9dd6a6e00aa on remote branch

Change-Id: I1e26ca306bfe47bb5b7085c58e9473a7302e972d
Merge "Merge e421bd44ae37d6a0386485ba266cd9dd6a6e00aa on remote branch"
power: qpnp-bms: Improve logic for storing FCC learnt data

BMS module supports 16 (8-bit) battery backed-up registers.
Make sure that while backing-up the new data, always replace
the oldest stored data.

CRs-Fixed: 730047
Change-Id: I5fc406ec24ce242b722926cc1096f7dcaf561656
Signed-off-by: Zhenhua Huang <zhenhuah@codeaurora.org>
Merge "power: qpnp-bms: Improve logic for storing FCC learnt data"
Merge "Merge "power: qpnp-bms: Improve logic for storing FCC learnt data""
msm: mdss: Allow smp change during composition switch

The composition fallback mechanism might not ensure unsetting of
the pipe whose prepare call failed due to smp configuration change,
typically in the cases where change in composition requests same
pipe. This scenario is a deadlock where composition switch does
not happen, due to these pipe failures.

To handle such cases, for changed SMP request for a pipe doing
non backend composition, allow smp configuration to happen, so
that the composition could be successfully switched, thereby
preventing the deadlock.

Change-Id: I2d29ac6591671494abc7c4caf7c6c53f058d12f6
Signed-off-by: Justin Philip <jphili@codeaurora.org>
msm: mdss: ensure retire fences are signaled during panel off

When turning off command mode panel, if retire fences are still active
and suspend sequence goes through some fences may remain active.
If fences remain active command panel off sequence would stop signaling
vsyncs and would throw off the timeline. To fix this clear the retire
timeline when turning panel off.

Change-Id: I32a5fe0f81b16fa2ef959c7f05e484fb9f9f8598
Signed-off-by: Adrian Salido-Moreno <adrianm@codeaurora.org>
Merge "msm: mdss: ensure retire fences are signaled during panel off"
Merge "Merge "msm: mdss: ensure retire fences are signaled during panel off""
Merge fb7dd7112d4b6429d86303f302738b6a640023c7 on remote branch

Change-Id: I505fd371843b15e15e4c8a29ef2c4c039467dd48
Merge "Merge fb7dd7112d4b6429d86303f302738b6a640023c7 on remote branch"
Merge "msm: mdss: Allow smp change during composition switch"
Merge "Merge "msm: mdss: Allow smp change during composition switch""
Merge 6ec071fa06b92f32d454b3b13fd0a007a38fa92d on remote branch

Change-Id: Idf95e267fe73fffaf8556e100e8dabad1657b460
Merge "Merge 6ec071fa06b92f32d454b3b13fd0a007a38fa92d on remote branch"
crypto: msm: check potential integer overflow

According to the specification of AEAD, AEAD request crypt length is
not a fixed maximum and associated length is also same. This could
lead to potential integer overflow, thus allocating less memory. So
we need to check potential integer overflow on AEAD request length.

CRs-Fixed: 726872
Change-Id: Ie7708000bfd8c57e2fba8e02230a7ce9cdc9634c
Signed-off-by: William Clark <wclark@codeaurora.org>
Merge "crypto: msm: check potential integer overflow"