Add slatecom_interface header file in gen_headers to make it
accessible from userspace modules who uses Android.bp files
for compilation.
Change-Id: Ie298ec28983c16999d941ee8667e2dd7b5c3db22
Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>
Ignore -106 error when channel opened
again without closing.
CRs-Fixed: 2836671
Change-Id: Ib27179031e6bbdc20511132efd6c4578d1d0a911
Signed-off-by: Satish Kodishala <skodisha@codeaurora.org>
It is possible that byte-cntr release happens after byte-cntr is disabled.
Don't write csr register when byte-cntr is disabled to avoid the register
access issue.
Change-Id: Ic818107e1bcbe31e1a55cdc8c0f6ff89ff70564f
Signed-off-by: Mao Jinlong <jinlmao@codeaurora.org>
Signed-off-by: Yuanfang Zhang <zhangyuanfang@codeaurora.org>
Set the wakeup timeout for qrtr to 500 ms for lito. This change
will help ensure the TUI client thread gets a chance to run before
the system is suspended again.
Change-Id: I8c8831995bf58fc39a3e8c107d0fd761745bbfed
Signed-off-by: Sarannya S <sarannya@codeaurora.org>
The qrtr driver can guarantee that the packet gets queued to the socket
but cannot guarantee the client process will get time to run if auto
sleep is enabled. This config will help mitigate missed packets on
systems where auto sleep is too aggressive.
Use the pm_wakeup_ws_event() api so a hard wakeup can be specified.
This will ensure a resume occurs if the data coming in happens while
the device is going into suspend.
Change-Id: Ic596e06e585b3479a6faa1d0210c016fc9138c6e
Signed-off-by: Chris Lew <clew@codeaurora.org>
Signed-off-by: Arun Prakash <app@codeaurora.org>
There is one race condition where mhi_prepare_channel is called
in which read pointer and write pointer is set to base address
and in parallel there could be an MHI M0 transaction which
checks any pending event rings on all channels (tre_ring)
with RP != WP and rings channel DB which causes Null pointer
access. Check for MHI channel is enabled before ringing channel
doorbell. Reset mhi channel chan_ctxt, tre_ring and buf_ring
wp and rp to NULL in mhi_deinit_chan_ctxt.
Change-Id: If30908fc7fcc26f6987bd0da886bb75468a29b9e
Signed-off-by: Vivek Pernamitta <vpernami@codeaurora.org>
Due to zero length skb packet IPA HW going to stall state.
Adding changes to avoid sending these zero length SKB frag
packets to HW.
Change-Id: I4dae51bf767588095bc1fcd9e10196e913299227
Signed-off-by: Ashok Vuyyuru <avuyyuru@codeaurora.org>
Update the copyright years of file to 2017, 2019-2021.
Change-Id: Ic5c6ad17f546b981c131fc6bd0eb573859a104b5
Signed-off-by: Mohammed Siddiq <msiddiq@codeaurora.org>
This reverts commit c6bc8ac9c5.
But there are revert conflicts in:
net/ipv4/tcp_input.c
net/ipv4/tcp_output.c
which effectively mean those files are not reverted (the relevant portions
of code area already missing).
Test: see follow up commit
Bug: 180068784
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: I70bc587e7bae4090dfd101f2427d7cc4fb4435af
Git-Commit: b72347bdd09c65269646ce5eaefd0bb579552a44
Git-repo: http://source.codeaurora.org/quic/la/kernel/common
Signed-off-by: Kaustubh Pandey <kapandey@codeaurora.org>
Make sure to hold the sock_tag_list_lock while accessing the tag to
avoid a race between getting the tag and free'ing the tag.
Bug: 184018316
Fixes: c7ca0ac69702 ("ANDROID: netfilter: xt_qtaguid: add qtaguid matching module")
Signed-off-by: Will McVicker <willmcvicker@google.com>
Change-Id: Ia44dfcc1693bc3de1d767e024d09c11f4a8b02f9
Git-commit: 2398e650c58a6f4877dafce649188290f6e3b4f5
Git-repo: https://android.googlesource.com/kernel/msm
Signed-off-by: PavanKumar S.R. <pavasr@codeaurora.org>
Add ETR status check while receiving USB_QDSS_CONNECT event.
Otherwise, there will cause crash due to NULL pointer issue.
Since ETR buffer will be released if ETR is disabled.
Change-Id: I358d25477c938844df5bff5c29ddbee307b770e3
Signed-off-by: Tao Zhang <taozha@codeaurora.org>
Remove the gcc_camss_camnoc clocks from debugcc
which are not registered in GCC to avoid the crash
because of parent index in KHAJE.
Change-Id: Ia8db40e55c3f7d96abb47bb810eb4f13c20e65f2
Signed-off-by: Madhuri Medasani <mmedasan@codeaurora.org>
Consider a case where ffs_data_new is getting called from
ffs_fs_get_tree and ffs_data_new returns error pointer since
the function (e.g. adb) is already mounted. The driver is only
checking for the NULL return value for ffs but in this case it
will not be NULL, which will fail the check and driver will go
ahead accessing invalid pointer which can lead to inconsistencies.
Fix this by having NULL as well as error pointer check for ffs.
Change-Id: Idad5a0b91148325258ea3f545d4da71644c7fc53
Signed-off-by: Pratham Pratap <prathampratap@codeaurora.org>
Stop_rx is bailing out in the runtime suspend path because of
parallel data from SOC and there is no SW FLOW ON from UART,
causing SOC unable to send RX data to host.
Enabled SW flow on if the stop_rx is bailing out during
runtime suspend.
Change-Id: I0dd52fafe99466e6177a60a108132f25a5be570b
Signed-off-by: Yatish Kumar Singh <yatishku@codeaurora.org>
Enable RPM SMD cooling device driver for KHAJE. It monitors
device temperature and request different temperature band levels
to RPM hardware.
Change-Id: Ia0c4deed12ee94f8fa0a6e98950e0654576740e1
Signed-off-by: Gopala Krishna Nuthaki <gnuthaki@codeaurora.org>
when usb_bypass_notify is called by ush_qdss_close(), no need to
response to USB_QDSS_DISCONNECT event. so add etr status check to
avoid exception.
Change-Id: I4ab5d7f4ba054b0d1ecc7026b5662ddc1c8b5ca1
Signed-off-by: Yuanfang Zhang <zhangyuanfang@codeaurora.org>
Currently both Bengal and Khaje use the same MPM pins mapping
configuration as they use the same compatible string. USB PHY
has a different GIC IRQ on Khaje, so different MPM configuration
is required.
Change-Id: I680bb0529145dfe2166f5b26d934da34e5c52f98
Signed-off-by: Raghavendra Kakarla <rkakarla@codeaurora.org>
Use rwsem to ensure serialization of the callers and to avoid
starvation of high priority tasks, when the system is under
heavy IO workload.
Change-Id: Ifac519c3de127f79d8613ee742a68f7fc0377e36
Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
Add code to assert if FW requested memory allocation fails.
This helps us to collect logs at the time of failure.
Change-Id: I8d3ff82eee545510318e0a9a2a128a71dc8a9fb3
Signed-off-by: Naman Padhiar <npadhiar@codeaurora.org>
Signed-off-by: Mohammed Siddiq <msiddiq@codeaurora.org>
The context is currently kept alive until all its fences are
released. This means that we do not destroy a context until all
the fence fds associated with it are closed by userspace, which may
be a long time. Instead, remove the timeline's refcount on its
context when it is detached. This permits the context to be freed
once all its fences signal.
Change-Id: Ifc5dd55980358ddbb4d3f6220d8b5d9f725aed1b
Signed-off-by: Lynus Vaz <lvaz@codeaurora.org>
Signed-off-by: Hareesh Gundu <hareeshg@codeaurora.org>
Signed-off-by: Pankaj Gupta <gpankaj@codeaurora.org>
2G+5G+6G, total channel num is 157 until now, increase unsafe channel max
num to avoid out of buffer.
Change-Id: I1e433c0bd88290bb5493b2c4b0bda86e17b04a01
CRs-Fixed: 2752689
Signed-off-by: Jianmin Zhu <jianminz@codeaurora.org>
Signed-off-by: Mohammed Siddiq <msiddiq@codeaurora.org>
The following frequencies (320, 785 and 1025MHz) require
fmax table update for not crossing voltage bound.
Change-Id: I4c26c39ce1e7c655358a7ef14ab2aeaad0c57af5
Signed-off-by: Madhuri Medasani <mmedasan@codeaurora.org>
