On APQ8096 Auto ADP Lite platform, it only has two displays,
native HDMI and one DSI-HDMI display through ADV7533 bridge
chip. The secondary ADV7533 instance needs to be disabled.
Change-Id: Ibae5c1561ec9f6890f818eeef185dfcf0bc1a62d
Signed-off-by: Jin Li <jinl@codeaurora.org>
Defines the non-removable property for UFS device node.
This basically lets the driver know that UFS is the boot
device.
Change-Id: I11df8441385910fdab7595a96a5deb24c7ca833e
Signed-off-by: Asutosh Das <asutoshd@codeaurora.org>
If host driver fails to send WMI_VDEV_DOWN_CMDID, firmware will drop
further packets as vdev TX PAUSE reset is done as part of VDEV_DOWN.
Send vdev down to firmware if STA fails to associate.
CRs-Fixed: 2061161
Change-Id: Ie26645389dcb839758ff6aa55812172beeccc171
Signed-off-by: Ashutosh Kumar <askuma@codeaurora.org>
There is still one ADV7535 instance on MSM8996Pro Auto CDP lite
platform, which connects DSI0 interface to HDMI.
Change-Id: I1efe7484d6f4eb1956c95689420b06b40278588e
Signed-off-by: Jin Li <jinl@codeaurora.org>
Add support to parse the HDMI TX version and
HDCP support from the HDMI and QFPROM registers.
This information is used to decide which HDCP driver
module is to be initialized at boot time.
Change-Id: Ib598f3867f1cd2ef9adb7503c5907cbb1e4ba758
Signed-off-by: Abhinav Kumar <abhinavk@codeaurora.org>
Update the minimum frequency restriction value and maximum frequency
limit value to the correct nominal frequency 1.056 GHz and 1.2096 GHz
respectively, as per the updated frequency plan of msm8996pro.
Change-Id: I725351c064f0211f95af4b4dd708b62360331282
Signed-off-by: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>
Without this fix the MMC may incorrectly set the CAPS for the SD card.
Change-Id: Ia4be2e78453663818cfd18deb9a590ec80423bca
Signed-off-by: Bao D. Nguyen <nguyenb@codeaurora.org>
For V4L2_CID_MPEG_VIDC_VIDEO_PICTYPE_DEC_MODE ioctl the valid
ctrl values are V4L2_MPEG_VIDC_VIDEO_PICTYPE_DECODE_ON and
V4L2_MPEG_VIDC_VIDEO_PICTYPE_DECODE_OFF. But for
V4L2_MPEG_VIDC_VIDEO_PICTYPE_DECODE_OFF case
we are sending wrong enable_picture.picture_type value. We are
also oring HAL_PICTURE_IDR, whereas only
HAL_PICTURE_I | HAL_PICTURE_P | HAL_PICTURE_B should be sent.
Change-Id: I96103d068b3e6e5f23da07d9a4c20e92ed55557c
Signed-off-by: Praveen Kumar Dwivedi <pkd@codeaurora.org>
Fix the access to ipacm_client array.
Change-Id: I0e6c026a4f6eb0bc21f4e07cb301e21f78103f33
CRs-Fixed: 2024177
Acked-by: Ady Abraham <adya@qti.qualcomm.com>
Signed-off-by: Skylar Chang <chiaweic@codeaurora.org>
Assert the device upon send command failure
after reaching maximum retries.
Change-Id: I154eda0697ec190662dc16edbe09e2213b4a0bae
Acked-by: Ashok Vuyyuru <avuyyuru@qti.qualcomm.com>
Acked-by: Mohammed Javid <mjavid@qti.qualcomm.com>
Signed-off-by: Utkarsh Saxena <usaxena@codeaurora.org>
Signed-off-by: Mohammed Javid <mjavid@codeaurora.org>
IPI's from the victim cpu are not handled in dev_cpu_callback.
So these pending IPI's would be sent to the remote cpu only when
NET_RX is scheduled on the victim cpu and since this trigger is
unpredictable it would result in packet latencies on the remote cpu.
This patch add support to send the pending ipi's of victim cpu.
Change-Id: I6e688bf0d09a952468eec18f80ce6b21bf370ef1
Signed-off-by: Ashwanth Goli <ashwanth@codeaurora.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Refine the code change for this changeID:
I335a046a886ac3ce35cf96eb71231bfe75d33c60
CRs-Fixed: 2058348
Change-Id: I9a734c8bed284870562ff2d096e7316328f37e02
Signed-off-by: Paul Zhang <paulz@codeaurora.org>
With certain senarios such as error FATAL, WBOG Bite in modem
WLAN hardware is still alive, while trying to collect the dump
platform driver is removing the MSA permissions from MSS
and WLAN Hardware to HLOS, at the same time if WLAN Hardware
is trying to access the MSA region which results into SNOC error
To avoid such senarios instead of removing MSS and WLAN permissions
MSA is assigned HLOS permissions as well and once the ramdump is collected
HLOS permissions will be removed.
Change-Id: Ic71e0fa8c064fd70dad9958187244909cbb80c0a
CRs-fixed: 2048531
Signed-off-by: Anurag Chouhan <achouhan@qti.qualcomm.com>
On qcom platforms, bootdevice is the primary storage
device. The regulators to this device are left ON by
the bootloaders. Detecting further in the init sequence
that UFS is not the bootdevice entails turning-off of
these regulators without sending PON. This is bad for
the underlying storage device.
Change-Id: I7e9231f0bcf90d8f329146ae2d831bbb5ef8190e
Signed-off-by: Asutosh Das <asutoshd@codeaurora.org>
When calling smmu mapping, if iova is specified directly by user, not
allocated dynamically in dma-mapping.c, smmu driver needs to provide
support for this. This is needed in early display case. In this scenario,
LK has set physical memory to display hardware for fetching, so if iova
is not explicitly specified in kernel, but instead dynamically produced
by "alloc_iova" in dma-mapping.c, display hardware has no chance to know
this new iova, then smmu fault will happen if enabling the iommu stage-1
translation.
To fix this smmu fault problem, add re-routing to the right path when
iova specified by user is not 0 in smmu map function.
Change-Id: I555fe7ae44464f25245d2d0a6740a2411a8624ba
Signed-off-by: Guchun Chen <guchunc@codeaurora.org>
