To get the 2MB aligned IOVA section mappings, set
ARM_DMA_IOMMU_ALIGNMENT to 9.
Change-Id: I3254c39e4864c32d6f25a4d416b1b7aec6756ecd
Signed-off-by: Charan Teja Reddy <charante@codeaurora.org>
CONFIG_CPU_BOOST config option is only enabled for
msmcortex-perf_defconfig. Enable it for msmcortex_defconfig too.
Change-Id: I31d42aa4ac3a78e6bc3c52aa0ba7cebd8c5a7893
Signed-off-by: Rohit Gupta <rohgup@codeaurora.org>
Currently both sde_crtc_atomic_begin() and
sde_crtc_atomic_flush() add the CRTC state event
to the cached sde_crtc->event.
This has a potential NULL ptr issue in the
case of vblank event firing in between sde_crtc_atomic_begin() and
sde_crtc_atomic_flush() because the upstream DRM vblank API
send_vblank_event() doesn't consider the case when the VBLANK
interrupt could have already freed any pending vblank events.
Remove the caching from sde_crtc_atomic_begin() to avoid this
condition.
Also make sure that a page_flip event was indeed submitted before
signaling the complete_flip() by setting a PENDING_FLIP flag right
after HW flush.
Change-Id: Ib201d2851e57bf22ec1f00814fc2e4dd2f35bfa1
Signed-off-by: Abhinav Kumar <abhinavk@codeaurora.org>
As debugfs interface is intended to test the respective framework, remove
from the driver to make sure it won't be available by default.
CRs-Fixed: 2025661
Change-Id: I6af9a8333c8028611f889cc2f9b0beb37ef12c9b
Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@codeaurora.org>
Variable current_image can be modified by multiple threads.
This change will protect current_image getting modified
by multiple threads.
Change-Id: I33df463311b24f73b1ba124d388731a72bd13263
CRs-Fixed: 2016485
Signed-off-by: Swetha Chikkaboraiah <schikk@codeaurora.org>
This patch checks the buffer for NULL
pointer to prevent undefined access.
CRs-Fixed: 2032374
Change-Id: I1a1c4ca24e5c3d538ea93685de304dd186968308
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
In some scenarios such as USBCV tests, multiple set_alt
could be issued with same interface and alternate
setting. In that case, EPs are disabled and enabled,
we get the usage count but do not put it. This causes
a mismatch and DWC3 LPM does not work anymore. Fix
this issue by moving put_usage_count to ffs_func_set_alt.
Change-Id: Ic85db09820d2c18b67bd463fe27e2c1ef41e8c74
Signed-off-by: Ajay Agarwal <ajaya@codeaurora.org>
Enable support for "Disable U1U2 low power modes" for SDM660 in
superspeed mode.
Change-Id: Ic49cf7ef48cb027cd82c0a3de7f98ae3da1fca61
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
Trigger preemption from the interrupt handler. This allows us
to aggressively change ringbuffers especially to lower priority
ones and finish working on pending commands.
Change-Id: Ic05213f3d02b1bb7400461edd0d19e38d5b01ec2
Signed-off-by: Sharat Masetty <smasetty@codeaurora.org>
This reverts commit 8777df6c6e
("ASoC: msm: decrement slim channel ref to set the property").
Slimbus channel deallocate and slimbus channel query should
happen in pair to ensure the ref count and state of the
channel are both in correct value.
CRs-Fixed: 1102349
Change-Id: Ie15f6e65448194ba781160856dd3f4e2ab081de1
Signed-off-by: Walter Yang <yandongy@codeaurora.org>
The txpower is being recalculated when adding interface to make sure
txpower won't overshoot the spec, and when removing the interface,
the txpower should again to be recalculated to restore the correct value
from the active interface list.
Following is one of the scenario
vdev0 is created as STA and connected: txpower:23
vdev1 is created as P2P_DEVICE for control interface: txpower:0
vdev2 is created as p2p go/gc interface: txpower is 21
So the vdev2@txpower:21 will be set to firmware when vdev2 is created.
When we tear down the vdev2, the txpower needs to be recalculated to
re-set it to vdev0@txpower:23 as vdev0/vdev1 are the active interface.
ath10k_pci mac vdev 0 peer create 8c:fd:f0:01:62:98
ath10k_pci mac vdev_id 0 txpower 23
... (adding interface)
ath10k_pci mac vdev create 2 (add interface) type 1 subtype 3
ath10k_pci mac vdev_id 2 txpower 21
ath10k_pci mac txpower 21
... (removing interface)
ath10k_pci mac vdev 2 delete (remove interface)
ath10k_pci vdev 1 txpower 0
ath10k_pci vdev 0 txpower 23
ath10k_pci mac txpower 23
Signed-off-by: Ryan Hsu <ryanhsu@qca.qualcomm.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git
Git-commit: d679fa1b3c8997e3a371da3cca08c44a38054c34
CRs-Fixed: 2027293
Change-Id: I56befd4c4fd80ab77ed65926663a1f2471701f68
Signed-off-by: Rajeev Kumar Sirasanagandla <rsirasan@codeaurora.org>
Update QP Control value and sanitise QP values for
Initial QP properly.
Change-Id: I870a4f33a0dfbfd3a95970bb9cf319855fba746f
CRs-Fixed: 2027340
Signed-off-by: Deepak Kushwah <dkushwah@codeaurora.org>
Ath10k reports the phy capability that supports P2P_DEVICE interface.
When we use the P2P supported wpa_supplicant to start connection, it'll
create two interfaces, one is wlan0 (vdev_id=0) and one is P2P_DEVICE
p2p-dev-wlan0 which is for p2p control channel (vdev_id=1).
ath10k_pci mac vdev create 0 (add interface) type 2 subtype 0
ath10k_add_interface: vdev_id: 0, txpower: 0, bss_power: 0
...
ath10k_pci mac vdev create 1 (add interface) type 2 subtype 1
ath10k_add_interface: vdev_id: 1, txpower: 0, bss_power: 0
And the txpower in per vif bss_conf will only be set to valid tx power when
the interface is assigned with channel_ctx.
But this P2P_DEVICE interface will never be used for any connection, so
that the uninitialized bss_conf.txpower=0 is assinged to the
arvif->txpower when interface created.
Since the txpower configuration is firmware per physical interface.
So the smallest txpower of all vifs will be the one limit the tx power
of the physical device, that causing the low txpower issue on other
active interfaces.
wlan0: Limiting TX power to 21 (24 - 3) dBm
ath10k_pci mac vdev_id 0 txpower 21
ath10k_mac_txpower_recalc: vdev_id: 1, txpower: 0
ath10k_mac_txpower_recalc: vdev_id: 0, txpower: 21
ath10k_pci mac txpower 0
This issue only happens when we use the wpa_supplicant that supports
P2P or if we use the iw tool to create the control P2P_DEVICE interface.
Signed-off-by: Ryan Hsu <ryanhsu@qca.qualcomm.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git
Git-commit: 88407beb1b1462f706a1950a355fd086e1c450b6
CRs-Fixed: 2027293
Change-Id: Ib56352e1601e7400b856cfafe67503bee98d5ced
Signed-off-by: Rajeev Kumar Sirasanagandla <rsirasan@codeaurora.org>
Userspace f_fs client e.g. ADB daemon can re-open ep0 file node
on adb_read/write error (or on bus reset). This results in device
disabling and enabling pull-up on bus reset. USBCV CH9 tests which
perform bus resets also fail due to this.
Fix this by not failing adb_read on bus reset so that adbd client
woudln't attempt ep0-file close. This behavior is not changed for
composition switch or cable disconnect by checking if adb_read
was attempting first transfer after online state or it was in middle
of a session when disconnect happened.
Change-Id: I2378f22995b7ddffb17d618df059d8aedb594d97
Signed-off-by: Ajay Agarwal <ajaya@codeaurora.org>
Add the RRADC die_temp channel details to the FG node for
the FG standby oscillator frequency drift WA.
Change-Id: I78d385afc82f9d8b7b6cdc64de59dfe964d2b50b
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
It is observed that on certain foundry devices, frequency of the
standby oscillator drifts with die temperature. Compensate
for this by correcting the FG time-base based on die temperature.
Change-Id: I0de19b9c342bf50568502b4de96897e159a8e143
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
It is possible to route analog microphone data to the MAD (Microphone
Activity Detection) block in the codec. Currently, VDDIO mode is used
for analog microphones, which can cause degradation of audio data,
causing no detection from the MAD block. Change the MAD programming
to use micbias instead of VDDIO mode for analog microphones to fix
this signal degradation problem.
CRs-fixed: 2021869
Change-Id: I77e089bd9858e5179405f87982b16ddaf7b4cd5b
Signed-off-by: Bhalchandra Gajare <gajare@codeaurora.org>
Update "apq8998" to "apq8098" as a proper name for all files
and strings used by apq8098 platform.
Change-Id: Id633d346946251751829fb597c860c8d41944265
Signed-off-by: Runmin Wang <runminw@codeaurora.org>
Use timestamp to detect when dual camera interfaces are out
of sync. Without using timestamps the interfaces can remain
out of sync for a long time since it takes a while to detect
the out of sync condition based on frame id increment.
CRs-Fixed: 2029680
Change-Id: I21cf2b0a76a7c9d8ad812ffbdbb1b1a36d9af1a5
Signed-off-by: Shubhraprakash Das <sadas@codeaurora.org>
