QTI needs an indication of cable connect for DPL.
Since host DPL driver does not send DTR indication
send zero length packet to QTI upon cable connect.
Change-Id: I545771f9a84ecc9c2f641c17e057673a32b1f305
Signed-off-by: Hemant Kumar <hemantk@codeaurora.org>
Correct spi8 pin function as defined by pinctrl definition.
Change-Id: Ibdf1c630525db84b384bd6d27269b0b74d77fee6
Signed-off-by: Shrey Vijay <shreyv@codeaurora.org>
Add charger/FG device nodes along with the necessary
configuration.
Keep all these nodes disabled for simulator/RUMI platform.
CRs-fixed: 1091731
Change-Id: I9c751d777d8402cdea3cdfb27da1a19a98a250e2
Signed-off-by: Ashay Jaiswal <ashayj@codeaurora.org>
It is found that "dc civac" from el0 on a non-COW RO VA results in a
segmentation fault, while as per ARM ARM, for el0 only read access
permission is needed on a VA to perform clean and invalidate. This bug
was introduced by commit 3fbe6bc28a6b ("arm64: Allow cache maintenance
operations to trigger write faults"), which enabled write faults on all
cache maintenance faults.
The original intention of the above commit was to trigger write faults
only for cache maintenance operations performed by EL1 on user VA. But
it introduced this side effect of generating a write fault on EL0 cache
maintenance ops also when a read permission is sufficient for operation
to succeed. This results in a segmentation fault when the VA is part of
region marked as PROT_READ.
So trigger write faults only when the cache maintenance fault is generated
in non-user mode. Still, there can be a case where kernel performs a cache
maintenance op on a PROT_READ mapped VA which will result in a kernel
fault. But that looks invalid since there is no need for a kernel driver
to perform a cache maintenance on a RO buffer and such cases if they exist
need to be fixed.
Change-Id: I001ca0473c37fcf713201386b5ed6a6244f6b37d
Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
arm64 sets non-dirty userspace PTEs as read only by default.
The expectation is that on the first write the fault handler will
properly unmark the PTE as read only. Currently, the fault handler
will not mark a fault coming from a cache maintenance operation as
a write. The result of this is that a write to a user space address
from a cache maintenance operation will not get unmarked as read only
and the access may be retried infinitely. Rather than going through
the hassel and side effects of adding the cache operations to the
exception table and changing arm code to match, just drop the CM
check from the fault handler and let cache maintenance faults be
handled like normal writes.
Change-Id: I4b295b47ebdd24abf94204ad634e91ca5f71ce8a
Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
Remove the pointless checking against interface combinations in
the initial basic beacon interval validation, that currently isn't
taking into account radar detection or channels properly. Instead,
just validate the basic range there, and then delay real checking
to the interface combination validation that drivers must do.
This means that drivers wanting to use the beacon_int_min_gcd will
now have to pass the new_beacon_int when validating the AP/mesh
start.
CRs-Fixed: 1087922
Change-Id: Iec536bcdf4ed95e3d796324fd8bf5df259b340b0
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git
Git-commit: 4c8dea638c16141adb046fd2e0cab51dfe43650c
[liord@codeaurora.org: Fix conflicts]
Signed-off-by: Lior David <liord@codeaurora.org>
We shouldn't abort the iteration with an error when one of the
potential combinations can't accomodate the beacon interval
request, we should just skip that particular combination. Fix
the code to do so.
CRs-Fixed: 1087922
Change-Id: Ib1ae7221291b8176d61d58e756a3814c80d98d27
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git
Git-commit: 0507a3ac6e98f50583912ec78d07c2e4daaf2b28
[liord@codeaurora.org: cherry-pick without changes]
Signed-off-by: Lior David <liord@codeaurora.org>
Beacon interval interface combinations validation was missing
for MESH/IBSS join, add those.
Johannes: also move the beacon interval check disallowing really
tiny and really big intervals into the common function, which
adds it for AP mode.
CRs-Fixed: 1087922
Change-Id: I282300533dcd80f65c9ba366246d028a6130ffff
Signed-off-by: Purushottam Kushwaha <pkushwah@qti.qualcomm.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git
Git-commit: 12d20fc9186a742d40e824f575df5aa62be31d69
[liord@codeaurora.org: fix conflicts and trivial compile errors]
Signed-off-by: Lior David <liord@codeaurora.org>
Change the power supply for msmcobalt QRD interposer platform
to use regulators from pmfalcon.
CRs-Fixed: 1090535
Change-Id: Ib1fdb0454c6e1d770ea6ec11a6032f8553d56c06
Signed-off-by: xiaonian <xiaonian@codeaurora.org>
Content Protection IRQ is a mechanism used by HDCP 1.3
protocol over DisplayPort to notify source device about
current hdcp status of receiver/repeater device. Handle
cp_irq to listen to sink receiver/repeater events and
update source hdcp state accordingly.
Change-Id: I63ecf6045f13e8b1d75bf6db2135671aa30c9e60
Signed-off-by: Ajay Singh Parmar <aparmar@codeaurora.org>
Add venus device nodes to support hardware accelerated
video codecs for starlord.
CRs-Fixed: 1088324
Change-Id: I2e8ffab214106c01557446e00dbebe2cc2a52bd1
Signed-off-by: Deepak Kushwah <dkushwah@codeaurora.org>
Specify the regulators for mdss on falcon track3.
Change-Id: Ie828c8568ef09c89cff157d16d3cb322647b6f6e
Signed-off-by: Ashish Garg <ashigarg@codeaurora.org>
Add the LDO and NCP display +ve and -ve bias for LCD
display.
Change-Id: Ia85688854f26fe871d5c1253c2d51d75d84deb8f
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
The variable used to hold the value for VFE clock does not need
64bits as 32bits will suffice.
CRs-Fixed: 1091727
Change-Id: Ib4d1328efe6e1df02e39502d38bb5662f9c4164c
Signed-off-by: Venu Yeshala <vyeshala@codeaurora.org>
Add common dtsi file for msmfalcon and msmtriton. Also Add
device tree entry for super speed USB3 controller, super speed
phy and high speed phy.
Change-Id: I326eceeddff8e77d346c3365fa46cd539324451f
Signed-off-by: Chandana Kishori Chiluveru <cchiluve@codeaurora.org>
To optimize charging during power negotiation and the voltage
is not changing, for example when transitioning from implicit
contract to the default 5V PDO, there is no requirement to
suspend the charging and hence setting the charger's
PROP_PD_CURRENT_MAX can be avoided. It is only needed when
changing voltages, in which case current limit should be
calculated based on pSnkStdby (2.5W), or when staying at the
same voltage and decreasing current.
Also fix the incorrect setting of PROP_CURRENT_MAX to
PROP_PD_CURRENT_MAX when doing a sink->source swap.
Change-Id: Ib53902459646e590df4dc7fcb00f833d5e8f41ed
Signed-off-by: Jack Pham <jackp@codeaurora.org>
There's no harm in having drivers read the list, since they can
use RCU protection or RTNL locking; allow this to not require
each and every driver to also implement its own bookkeeping.
CRs-Fixed: 1087922
Change-Id: I2f38b8ba1ddbe6041a4189f5d9b72c982f0fb367
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git
Git-commit: 53873f134d285191ef6435882d55837093a36c53
[liord@codeaurora.org: fix conflicts]
Signed-off-by: Lior David <liord@codeaurora.org>
Increase the refresh rate for the RRADC to support
reading refreshed USBIN voltage at a higher frequency.
To support the higher frequency at which the data
is refreshed enable continuous mode and force update
on reading every cycle on the USBIN_V trigger.
After reading the USBIN_V result set the RRADC to non
continuous mode with default trigger setting.
Change-Id: I7e9ada5de1f619c6a34a4b2e1764f5e908564ce5
Signed-off-by: Siddartha Mohanadoss <smohanad@codeaurora.org>
Clear mpm_wcssaon_config bits before top level reset.
If those bits are non-zero during WLAN is enabled,
there could be random failures.
CRs-Fixed: 1086372
Change-Id: Ia03380dfa4852c80fedb38f3c79f55d8d1a9a7f6
Signed-off-by: Yuanyuan Liu <yuanliu@codeaurora.org>
Currently we disable try.SINK right before pd becomes active and
re-enable it right after inactive. This breaks typec compliance.
To fix it, disable try.SINK mode in the probe and never enable it.
Change-Id: I61523188f45daca026b90943c845b43a8327f51e
Signed-off-by: Harry Yang <harryy@codeaurora.org>
Currently there is an issue introduced by forcing the results of
the icl_votable while pd is active. icl_votable is a min voter
and since the DEFAULT_VOTER votes 1.5Amps that becomes the max
one could draw when pd is active. This is incorrect and hence the
issue.
Note that DEFAULT_VOTER is only needed while DCP is present.
So, to fix it, rename DEFAULT_VOTER to DCP_VOTER and make DCP_VOTER
unvote and vote when pd_active is set and unset respectively.
CRs-Fixed: 1091477
Change-Id: I7435f05f20e12a7704ae5d9597b5cdc9b5a61d00
Signed-off-by: Harry Yang <harryy@codeaurora.org>
