During multiple partial update, each pipe is checked against
the two ROIs and the pipe's src and dst rect are cropped and
adjusted with respect to first_roi or second_roi, based on its
position. If the pipe is used with the same configs in the next
kickoff, restore the pipe's actual src/dst before continuing with
the kickoff.
Change-Id: I1db579626d96302e07fef1a755fb39944d3eaca8
Signed-off-by: Veera Sundaram Sankaran <veeras@codeaurora.org>
Add TX app type support in compress driver to support different
post processing modules per COPP in the TX path
CRs-fixed: 1072067
Change-Id: I8e84577b5aff5e932632c4612a88808615d764ae
Signed-off-by: Satish Babu Patakokila <sbpata@codeaurora.org>
Add timestamp support for compress driver.
Modify ASM driver to read the buffer from predefined offset.
CRs-fixed: 1072067
Change-Id: I1c46befc223285495b3c0650e6c3eaae81f58771
Signed-off-by: Satish Babu Patakokila <sbpata@codeaurora.org>
Add cpu cache nodes to represent the cache hierarchy and
to specify the dump size of each cache.
While at it also add the cache dump nodes which will enable
reserving the memory for cache dumps.
Change-Id: I06eead417b77c74a6e12e6f6b5251c0c7e62c96b
Signed-off-by: Srinivas Ramana <sramana@codeaurora.org>
During composition switch, android driver stops data transfers first
and removes configuration before disabling the pullup. With this sequence
there is a possibility for a race where usb_remove_config is in progress
during which pullup is active and sending the setup request for strings
with zero configuration value. Hence fix the issue by adding spinlock
protection for get_sring descriptor.
Change-Id: I13c601f0e48d847b322a2761cd52268963cacf01
Signed-off-by: Chandana Kishori Chiluveru <cchiluve@codeaurora.org>
Currently we are using the argument passed to
the function to fill the array values as is
without checking for the sanity. This commit
will add a sanity check on function argument
to avoid array index out of bound access.
Change-Id: I5f23f036441a67a3f3828cc432ea57c1c06bc8ae
CRs-Fixed: 1096134
Signed-off-by: Deepak Kushwah <dkushwah@codeaurora.org>
Add APIs to allocate and instanciate f_rmnet function
driver using configFS.
Change-Id: Iad76a7e317dd9caf846dbe870baee63a8c5ce6c1
Signed-off-by: Ajay Agarwal <ajaya@codeaurora.org>
size_t is an unsigned integer. Change format specifier
to resolve compilation issues for 32 bit.
Change-Id: I4309335c7ad0c695081d446a3f90e84edbcf1e32
CRs-Fixed: 1096066
Signed-off-by: Deepak Kushwah <dkushwah@codeaurora.org>
Upon any CQ error, the driver tries to halt the CQE first and
if it fails to halt, then CQE is disabled. The error handling
work function mmc_blk_cmdq_err() also tries to HALT the CQE
at couple of places and takes some action based on the HALT
success/error status. But since CQE is disabled, we should not
treat any errors of CQE halt/unhalt as critical and in fact,
we should not even attempt to halt/unhalt.
Change-Id: I6bef9f2c033f78ad0959954acc5d7627e8a92139
Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
Signed-off-by: Sayali Lokhande <sayalil@codeaurora.org>
The legacy interrupts are enabled as part of CQE halt. But there could
be few cases, where halt fails. In those cases, CQE is disabled without
enabling legacy interrupts. Without this we cannot send any commands
like status CMD13 in legacy mode as part of error handling work.
Change-Id: I944ab4060e779c7f41a945532e6a65c30797d40f
Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
Signed-off-by: Sayali Lokhande <sayalil@codeaurora.org>
There could be cases where CQE halt might fail and in which
case, CQE gets disabled as part of error handling.
In this case, !mmc_host_halt() will be true and the commands
sent in legacy mode are getting software request timeout errors
as they are getting handled as cmdq irq.
Hence, add !mmc_host_cq_disable() check as well in addition to
!mmc_host_halt() in sdhci_irq() before considering it as a
cmdq irq.
Change-Id: Ic529aae53fdecd6b9ecbb17ba13147964dce55dc
Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
Signed-off-by: Sayali Lokhande <sayalil@codeaurora.org>
As per hdcp 2.2 specifications, send the stream type message
to sink at a specified address in case sink is a receiver.
Update the messages to be sent to sink with the message received
from TZ and tear down the session in case it time's out.
Also, enable encryption after stream management message
exchange for hdcp repeaters to avoid unnecessary link failures.
Change-Id: Ib77756c942abfbdd6e1522a3238d5d8499496fc9
Signed-off-by: Ajay Singh Parmar <aparmar@codeaurora.org>
concurrent sysfs calls on the fw updater can cause
ugly race conditions. Return EBUSY on concurrent sysfs calls.
For sysfs calls which generate deferred work, prevent
the deferred work from running concurrently with other
sysfs calls.
Also check that ext_data_source is appropriately sized
and allocated, based on a patch by
Gengjia Chen (chengjia4574@gmail.com).
Signed-off-by: Andrew Chant <achant@google.com>
Change-Id:I5bbe4992f3fd2d23db288296eaeb61f5831098e9
Bug: 30799828
Bug: 31252388
Git-repo: https://android.googlesource.com/kernel/msm.git
Git-commit: 287ce2ccfefe68067c1f9f5175b6664bf7397fe6
Signed-off-by: Srinivasa Rao Kuppala <srkupp@codeaurora.org>
Video hardware on msm8998 chipset limits the max non secure region
address to 0xE0000000. So reduce non secure region size to 0x6f800000
from 0x8f800000 to limit the max address to 0xE0000000.
CRs-Fixed: 1092881
Change-Id: Ib9602aa2298caf01ab01b4e0225c112c71bb81f4
Signed-off-by: Maheshwar Ajja <majja@codeaurora.org>
Glink clients are not notified of tx transactions that are waiting
for remote rx done commands during SSR. This change adds a
notify_tx_abort call for any pending packets during intent purge.
Change-Id: I6a6ba17e2dffddc5cdc2de00da737fedf03c9476
Signed-off-by: Chris Lew <clew@codeaurora.org>
Crypto clock is needed for HDCP 1.x/2.x encryption. If not set,
it may result in link integrity failure as source and sink may
go out of synchronization. Set the crypto clock rate as per
hardware recommendations.
Change-Id: I768b3390fbe4728be285424d0ce27981e1a5d6cb
Signed-off-by: Ajay Singh Parmar <aparmar@codeaurora.org>
Introduce api service_notif_pd_restart() using which clients can request
to restart user PD.
CRs-Fixed: 1092791
Change-Id: Ic21de510cde4bfa9f2e4f7f3d4518b464be88db2
Signed-off-by: Puja Gupta <pujag@codeaurora.org>
Reverse the order in which the clocks needed
for QoS programming are being disabled. This is done
to resolve certain clocks being stuck on due to SlaveReady
FSM enabled.
Change-Id: I2d414689ad7ec2167b3974ae0f40338075609046
Signed-off-by: David Dai <daidavid1@codeaurora.org>
Forward thread acquired v4l2_ctrl->handler->lock in
v4l2_s_ctrl() and waiting for response from response thread.
Response thread was blocked on core->lock which was acquired
by second forward thread. The second forward thread acquired
core->lock and called v4l2_g_ctrl() in msm_comm_get_mbs_per_sec()
where it was blocked on same v4l2_ctrl->handler->lock and hence
response thread was not unblocked. Resolve the deadlock issue
by avoiding v4l2_g_ctrl() call in msm_comm_get_mbs_per_sec().
CRs-Fixed: 1095539
Change-Id: I73c2a74f1bb86f2b0359be54ed4f7675051db7b0
Signed-off-by: Maheshwar Ajja <majja@codeaurora.org>
Enable the interrupts required by hdcp 2.2 to update the hdcp 2.2
state machine as per hardware status.
Change-Id: Ib551b1fe8641203b66a31e745d5091641b4d0ae2
Signed-off-by: Ajay Singh Parmar <aparmar@codeaurora.org>
This change prevents blocking IOCTLs with wrong command
number or wrong magic Number. IOCTL handler should first
check that the command is valid and only then wait for
IPA driver initializations to finish.
CRs-Fixed: 1094653
Signed-off-by: Amir Levy <alevy@codeaurora.org>
Change-Id: I578dc96da96f7c10be51eac1f8b3c190e45dcfcf
This change adds RMNET support using IPA over BAM2BAM.
Removes all different supported control and data
transports and assumes BAM2BAM_IPA as default mode.
Cleans up QTI Control driver to support only RMNET
and DPL.
Change-Id: I5b763acfb28c2f1832874af786704835314fa9c7
Signed-off-by: Ajay Agarwal <ajaya@codeaurora.org>
In error scenarios, tx_buf is accessed even after tx_buf
memory is freed up. This change is to avoid access to freed
up memory.
Change-Id: I93a2c5875474094da1de07ddaaad8a709193632f
Signed-off-by: Vidyakumar Athota <vathota@codeaurora.org>
Some UFS devices violate T-HIBERN8_ENTER_TX time when moving Device
TX (Host RX) lane-1 from SLEEP to HIBERN8 at the end of burst.
M-PHY specification defines max value of 1000 ns for
T-HIBERN8_ENTER_TX but these devices drive DIF-N for 3432 ns. This can
cause the broken link situation after link starup.
This change fixes above issue by increasing host PHY's RX_MIN_HIBERN8_TIME
to 8us (we are giving some additional margin though device needs 3.432us).
Change-Id: I55cb0b718e2e429c0378d842d85a02ace44bf2ce
Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org>
Validate the power setting size before copying.
If userspace sends a value which is greater than
MAX_POWER_CONFIG, then the driver accesses unintended memory.
This change will fix the issue.
Crs-Fixed: 1089433
Signed-off-by: Rajesh Bondugula <rajeshb@codeaurora.org>
Change-Id: Iaaa6f5b3c1c2ac5b5b38b3ac407d6ae394bba780
In case of link integrity failures reported by sink, tear down
the hdcp session. Complete any thread waiting for a response
from sink as part of hdcp protocol to avoid unnecessary delays
in starting new hdcp session.
Change-Id: I0afc56e0177ceccf76b717a483584f7ad5055fe1
Signed-off-by: Ajay Singh Parmar <aparmar@codeaurora.org>
Glink channel state LOCAL_DISCONNECT occurs only when remote
side channel is closed or device node closed from userspace.
In this case, glink LINK itself is not available to open channel.
So avoid opening glink channels during LOCAL_DISCONNECT state.
Change-Id: I637622d7bfd0cd1d0aa5b905173a7674093674c4
Signed-off-by: Vidyakumar Athota <vathota@codeaurora.org>
