Add the symbols qcom_scm_dcvs_reset, qcom_scm_io_reset,
qcom_scm_dcvs_init_ca_v2, qcom_scm_dcvs_ca_available, and
qcom_scm_dcvs_init_v2 to the whitelist and update the
ABI snapshot.
Change-Id: I3049cecbc4256c47050a91125f359993ee1af96b
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Add the symbol, drm_dp_check_act_status, to the qcom whitelist
and update the ABI snapshot accordingly.
Change-Id: I239fafdd2d57b0600a130b7610777da8a5874afe
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Wrapped keys can have key sizes of variable length.
Pass in the wrapped key size sent from userspace instead
of using a fixed value from the cipher when calling into
blk-crypto.
Bug: 156230001
Test: Validated metadata encryption with wrappedkey_v0 when /data
is mounted on a dm device.
fstab: metadata_encryption=aes-256-xts:wrappedkey_v0
Git-repo: https://android.googlesource.com/kernel/common/
Change-Id: I9c8bfff71eaf783427270766c419feceefb6be2d
Signed-off-by: Gaurav Kashyap <gaurkash@codeaurora.org>
Update the logic to handle multiple boost frequencies and also add the
frequencies to the OPP irrespective of normal or boost frequency.
Change-Id: I5b6dc8b157128392fd79e910c88911d6f4bd7b4d
Signed-off-by: Taniya Das <tdas@codeaurora.org>
- If probe_defer from secure_buffer received, we are raising the below
warning from arm_smmu_assign_table.
arm_smmu_assign_table+0x124/0x130arm_smmu_attach_dev+0x9c8/0x1098
iommu_group_add_device+0x1ac/0x460
iommu_group_get_for_dev+0xc4/0x2b4
arm_smmu_add_device+0x330/0x4f8
iommu_probe_device+0x98/0x110
of_iommu_configure+0xac/0x1b4
of_dma_configure+0x198/0x320
platform_dma_configure+0x1c/0x30
really_probe+0x234/0x8a8
driver_probe_device+0x70/0x144
__device_attach_driver+0x138/0x1fc
bus_for_each_drv+0xa4/0x120
- with this change we will be clearing the smmu domain, if probe_defer
from secure_buffer driver received.
Change-Id: Iad8a262e7d0ec8f49d94f521c4d43d3ec6931c8d
Signed-off-by: Faiyaz Mohammed <faiyazm@codeaurora.org>
Add register_oom_notifer and unregister_oom_notifier to
the QCOM whitelist and update the ABI snapshot accordingly.
Change-Id: I6b3888f909348dfbad4f0ede565ba616336b2388
Signed-off-by: Raghavendra Rao Ananta <rananta@codeaurora.org>
Some chipsets require PCIe root complex driver to manually
control PCIe PHY PLL block. Add support to power on PCIe PHY PLL
block if it has been manually powered down.
Change-Id: Iee2b7e9fd80e537a0b2983827261297c8642a3b7
Signed-off-by: Tony Truong <truong@codeaurora.org>
If the DRV subsystem goes through SSR (subsystem reset), then
PCIe root complex driver needs to handle recovering PCIe
controller and PHY accordingly.
Change-Id: I230e196725901acac29843b372aae5805a0763e7
Signed-off-by: Tony Truong <truong@codeaurora.org>
add operation to deal with smcinvoke callback request
Change-Id: Ia79b380691dbda4298cdf088fe1a09280767ef17
Signed-off-by: Zhen Kong <zkong@codeaurora.org>
Some simple ioctls like timsetamp query, capabities query can be
done anytime and should not be under the stream lock. Move these to
snd_compress_simple_iotcls() which is invoked without lock held.
While at it, improve readblity a bit by sprinkling some empty lines.
Change-Id: Icc8ffdadd565c635f6a95e7e5bdda76257f24ea3
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Signed-off-by: Eric Laurent <elaurent@google.com>
Git-commit: 6a44374b8b92e9946dc1e5c15c2a11003aa859b1
Git-repo: https://android.googlesource.com/kernel/msm
[dhakumar@codeaurora.org: resolved merge conflicts]
Signed-off-by: Dhananjay Kumar <dhakumar@codeaurora.org>
[bgoswami@codeaurora.org: resolved merge conflicts]
Signed-off-by: Banajit Goswami <bgoswami@codeaurora.org>
Signed-off-by: Meng Wang <mwang@codeaurora.org>
The sm_work needs to be queued on an ordered workqueue.
The create_freezable() does not ensure the ordered attribute
needed.
Hence, use the alloc_ordered_workqueue() instead of it
with the flags WQ_FREEZABLE and WQ_MEM_RECLAIM.
Change-Id: I535cb826f117b0162efb87639c85d7b1634a441a
Signed-off-by: Sriharsha Allenki <sallenki@codeaurora.org>
The mem-buf driver follows a supplier and consumer model
to enforce what the instance of the driver on a particular
Virtual Machine (VM) can and cannot do. These roles are
conveyed through the qcom,mem-buf-capabilities property.
A driver on a VM that has the supplier capability is able
to lend and share memory to other VMs, but cannot request
memory from another VM.
In the other direction, a VM with consumer capability is
only capable of requesting memory from other VMs, but cannot
satisfy memory requests from other VMs.
Change-Id: I1d258bdaafbbdb020831afc85c47f44a5ec93940
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
