As BT reset only is needed for qca6174 chip, so check chip
type first to avoid triggering get_bt_reset_gpio_value()
for other chip.
CRs-Fixed: 2514357
Change-Id: Icaaf7046aa02d3ae3ecb5bf565cc94c89f11fb71
Signed-off-by: Junlin Zhang <junlzhan@codeaurora.org>
Change BLK_DEV_LOOP_MIN_COUNT's value from 8 to 16 to meet
Android requirement.
Change-Id: Id1078cc1d3d1a4f05111cafad8007c983512b711
Signed-off-by: Tingwei Zhang <tingwei@codeaurora.org>
glink receive acknowledge function was called from IRQ context
This function can sleep and since function that can sleep cannot
be called from Interrupt context, moved this.
Change-Id: I838dffae2011e016ff3a7ac90e3556eeb4689220
Signed-off-by: Mohammed Nayeem Ur Rahman <mohara@codeaurora.org>
Remove "qcom,mhi-ethernet-interface" property such that mhi swip
will support default rawip network interface instead of ethernet
network interface on sdxpoorwills.
Change-Id: Ic0a4c0e5177a0258b26c66802ed14278eeec258f
Signed-off-by: Rama Krishna Phani A <rphani@codeaurora.org>
The bcl_sensor has a dependency on the FG gen3 driver. Disable
the same as FG is already disabled on this platform,disable
bcl_sensor can address the issue.
Change-Id: I23577171366cc89a211ad8b350ff6a5590989f0f
Signed-off-by: Junwen Wu <wudaemon@codeaurora.org>
Both flags and preempt_count variables of thread_info are falling
into the same cache line. When one of the cores is incrementing/
decrementing the preempt_count continuously in a tight loop with
spin_lock_irqsave() and spin_unlock_irqrestore() APIs, this causes the
flags update to be delayed. When the thread_info flags updates are
delayed, it leads to increased tasks scheduling latencies. So move the
thread_info's preempt_count into different cache line by adding padding.
Change-Id: I950d15a02b4df0c31862c3a11eb1a3d8fc17dff8
Signed-off-by: Prasad Sodagudi <psodagud@codeaurora.org>
Tight loops of spin_lock_irqsave() and spin_unlock_irqrestore()
in timer and hrtimer are causing scheduling delays. Add delay of
few nano seconds after cpu_relax in the timer/hrtimer tight loops.
Change-Id: Iaa0ab92da93f7b245b1d922b6edca2bebdc0fbce
Signed-off-by: Prasad Sodagudi <psodagud@codeaurora.org>
Signed-off-by: Chetan C R <cravin@codeaurora.org>
Presently chance of using uninitialized variables if a dci
command is not found is avoided by initializing command
structure variables.
Change-Id: I190299917ea6c7fadfc7686d43a7da098e0bc05e
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
Only one pair of MHI ep's are supported till now.
With respect to auto-pcie use case requirement
we need to support one more MHI ep pair for cv2x.
Modify ipa-mhi driver to support additional mhi ep pair.
Change-Id: I301dc7c46c6bfcc995db5a6a56c677481588d20b
Signed-off-by: Mohammed Javid <mjavid@codeaurora.org>
Update ipa driver's ep_mapping for modem end points
accordingly to support CV2X use case.
Change-Id: I9274d48c469a21d37f7e982b1b9f2418ad39ad1f
Signed-off-by: Mohammed Javid <mjavid@codeaurora.org>
In sdxpoorwills, only 12 ER indices are supported for
AP EE from IPA-GSI. So, modify the ER index from
9/13 to 7/11.
Change-Id: I3e975dabb4fc8c528ffe662dff8005618d9e4796
Signed-off-by: Mohammed Javid <mjavid@codeaurora.org>
Camera ID 1 supports eeprom and ID 2 doesn't support on Spyro WDP.
Change-Id: I654ba7ce4e4fabd172729956d90031f00fd946b5
Signed-off-by: Neng Chen <nengchen@codeaurora.org>
Add config to enable USB SERIAL CP210X and FTDI for apq8009.
Change-Id: Id681a3f2fc93d7415c654a8cc99056a9e157600f
Signed-off-by: wumeif <wumeif@codeaurora.org>
This commit disables scanning for mmc card presence
again and again on SA415M TTP devices as the presence
is handled through GPIO. This scanning otherwise
causes unnecessary CPU consumption.
Change-Id: Ic08482064c49a9c24780c86a8c719636e1528cbd
Signed-off-by: Rishi Gupta <rishgupt@codeaurora.org>
Disabled irq of sensor after 40 second of buffering if there is
no active client to read the data.
Change-Id: Ide5090fcb592628a6cf5e42fd41f4c305a3b899d
Signed-off-by: Puneet Yatnal <puneet@codeaurora.org>
cci_write is being executed meanwhile cci_init is called,
which will maybe cause cci timeout since cci_init will do
reset operation. So add the mutex_q lock which is used by
cci_write into cci_init.
Change-Id: I81c67f27205f4250f08ca7ab38799f6454578dbd
Signed-off-by: Ziyu Jian <ziyujiang@codeaurora.org>
load calculation check should be for a
non realtime session else it will result
in hardware overload error.
Change-Id: I86675d4e4f37a4c3c0e6080393255ad11c6ee6f9
Signed-off-by: Paras Nagda <pnagda@codeaurora.org>
There is potential rollover condition for CNTVCT and
CNTPCT counters.enable the config to control the counter read
to avoid rollover.
Change-Id: I6e3430e6ffe631d175d560fbcf0e4cee46ff7715
Signed-off-by: Tengfei Fan <tengfeif@codeaurora.org>
There is potential rollover condition for CNTVCT and
CNTPCT counters. So on any architecture timer counter
read, if the least significant 32 bits are set,
reread counter.
Change-Id: Iacc482ad956d5589d59a2a111576ec0463f5a1bb
Signed-off-by: Tengfei Fan <tengfeif@codeaurora.org>