In host mode upon XO shutdown high speed and full speed device
connection is not getting detected because mpm is not configured
to monitor for Dp line state change.
Change-Id: I34e3f586b99b6ff1af1d2323d4f272ee3cca7fa2
Signed-off-by: Hemant Kumar <hemantk@codeaurora.org>
This is an ancient bug that was actually attempted to be fixed once
(badly) by me eleven years ago in commit 4ceb5db975 ("Fix
get_user_pages() race for write access") but that was then undone due to
problems on s390 by commit f33ea7f404 ("fix get_user_pages bug").
In the meantime, the s390 situation has long been fixed, and we can now
fix it by checking the pte_dirty() bit properly (and do it better). The
s390 dirty bit was implemented in abf09bed3c ("s390/mm: implement
software dirty bits") which made it into v3.9. Earlier kernels will
have to look at the page state itself.
Also, the VM has become more scalable, and what used a purely
theoretical race back then has become easier to trigger.
To fix it, we introduce a new internal FOLL_COW flag to mark the "yes,
we already did a COW" rather than play racy games with FOLL_WRITE that
is very fundamental, and then use the pte dirty flag to validate that
the FOLL_COW flag is still valid.
Change-Id: I42e448ecacad4781b460c4c989026307169ba1b5
Reported-and-tested-by: Phil "not Paul" Oester <kernel@linuxace.com>
Acked-by: Hugh Dickins <hughd@google.com>
Reviewed-by: Michal Hocko <mhocko@suse.com>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Kees Cook <keescook@chromium.org>
Cc: Oleg Nesterov <oleg@redhat.com>
Cc: Willy Tarreau <w@1wt.eu>
Cc: Nick Piggin <npiggin@gmail.com>
Cc: Greg Thelen <gthelen@google.com>
Cc: stable@vger.kernel.org
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Git-repo: https://chromium.googlesource.com/chromiumos/third_party/kernel.git
Git-commit: 19be0eaffa3ac7d8eb6784ad9bdbc7d67ed8e619
Signed-off-by: Dennis Cagle <d-cagle@codeaurora.org>
Currently GEN3 FG driver reads "qcom,nom-batt-capacity-mah"
property from the battery profile device node to use that for
notifying fastcharge current to the charger driver. Change that
to use "qcom,fastchg-current-ma" property which seems to be more
appropriate. Update all the battery profiles that are used with
GEN3 FG to follow that.
Change-Id: I119e6af297b37a06a227475f712f938367fb65bc
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
To match with other battery profiles used for GEN3 fuel gauge,
rename the battery profile used for msm8998 QRD platform.
Change-Id: I9a12ac11b6bd303eb32b4e03e116281bca664d06
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
migrate_tasks() migrates all tasks of a CPU by using pick_next_task().
This works in the hotplug case as we force migrate every single task
allowing pick_next_task() to return a new task on every loop iteration.
In the case of isolation, however, task migration is not guaranteed
which causes pick_next_task() to keep returning the same task over and
over again until we terminate the loop without having migrated all the
tasks that were supposed to migrated.
Fix the above problem by temporarily dequeuing tasks that are pinned
and marking them with TASK_ON_RQ_MIGRATING. This not only allows
pick_next_task() to properly walk the runqueue but also prevents any
migrations or changes in affinity for the dequeued tasks. Once we are
done with migrating all possible tasks, we re-enqueue all the dequeued
tasks.
While at it, ensure consistent ordering between task de-activation and
setting the TASK_ON_RQ_MIGRATING flag across all scheduling classes.
Change-Id: Id06151a8e34edab49ac76b4bffd50c132f0b792f
Signed-off-by: Syed Rameez Mustafa <rameezmustafa@codeaurora.org>
There is a race condition between clearing an HMP request for active
migration and the actual active migration. Active migration can he
half-way through doing the migration when the HMP request can be cleared
by another core. Move clearing of HMP request to the stopper thread to
avoid this.
Change-Id: I6d73b8f246ae3754ab60984af198333fd284ae16
Signed-off-by: Olav Haugan <ohaugan@codeaurora.org>
We don't want user space tasks to run on isolated cpus. If the affinity
mask that the user space task is trying to set only includes online
cpus that are isolated return error.
Also ensure that tasks do not get stuck on isolated cores. We are not
properly updating the mask that we check against the current CPU so we
might end up thinking we can run on the current CPU. Fix this.
Change-Id: I078d01e63860d1fc60fc96eb0c739c0f680ae983
Signed-off-by: Olav Haugan <ohaugan@codeaurora.org>
For targets with LMH DCVSh hardware and OSM, BCL software frequency
mitigation is not required. Since hardware is doing the frequency
mitigation, there is no need for the HLOS BCL frequency mitigation.
So make the properties "qcom,mitigation-freq-khz" and
"qcom,thermal-handle" as optional properties.
Change-Id: I0062f3b39f00ff2f0e74affcffbcf1afd89d3b2f
Signed-off-by: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>
When the eSE is powered off, the “system” needs to give
8ms to the capacitor connected on the SVDD line to discharge.
We should inform the FW we just powered off the eSE.
Change-Id: I864fd8f75ded6ab8c42ea36bcdadcdbe924e927d
Signed-off-by: Gaurav Singhal <gsinghal@codeaurora.org>
Proxy vote for gcc_boot_rom_ahb_clk for modem pil on msm8998 instead
of keeping the vote until the modem was shutdown.
Change-Id: Ib32d40351179a687eca38228c4503e4a9a88c28d
Signed-off-by: Puja Gupta <pujag@codeaurora.org>
When an atomic iommu domain attaches, an additional vote for both
clk_prepare, bus_bw, and regulator_enable must be held. The prior logic
only did this if the atomic domain was the first to attach to the iommu.
Fix this.
As a side effect, add reference counting for bus_bandwidth voting such
that a call to arm_smmu_enable_clock() followed by
arm_smmu_disable_clocks() will not always result in a bus bandwidth
vote of zero.
Change-Id: I7f88ea845a281c8c1def4f642e61262b53b60e1a
Signed-off-by: Patrick Daly <pdaly@codeaurora.org>
L2a is required to lock the phy PLL upon bus resume when
exiting from XO shutdown. This LDO powers REFGEN block
which is required to be powered on so that phy PLL gets
locked as part of wakeup from XO shutdown.
Change-Id: Ia0e3d574de7c78534832e4f8749672eb6fcde1f0
Signed-off-by: Hemant Kumar <hemantk@codeaurora.org>
For the devices supporting implicit feedback over data endpoint
usb audio driver instantiates snd_usb_endpoint as sync_endpoint
even though there is no real usb sync endpoint exists. QMI driver
looks for usb endpoint if sync_endpoint is instantiated and bails
out if endpoint related context does not exist. This causes such
devices to not work. Hence do not bail out if sync ep context
does not exist and continue preparing the QMI response.
Change-Id: I7d96555573cfd6cca1ca56c877d78fde943f8100
Signed-off-by: Hemant Kumar <hemantk@codeaurora.org>
This fixes the issue where the dp pll resource was not correctly
keeping a refcount on the pll resource. This will fix the bootup
warning when both DSI and DP are enabled.
Crs-Fixed: 1088737
Change-Id: I19f8eef7f664a58cac1a082b8195e48c52613c5d
Signed-off-by: Siddhartha Agrawal <agrawals@codeaurora.org>
The hardware version register does not return the expected
version value. The register is located in register space that is
accessible to the secure world only. This results in WDOG status
register not being enabled. Use the chip version instead.
CRs-Fixed: 1099112
Change-Id: I014c823bcf2545f005205dde326a074eaa5d7a6a
Signed-off-by: Osvaldo Banuelos <osvaldob@codeaurora.org>
1. Update PMIC gpio configuration for
front and rear camera.
2. Correct VANA GPIO.
3. Correct the CSID VREG Voting.
Change-Id: I1e72bf8855ea1150eb2cedaee82d04610b09bdae
Signed-off-by: Shankar Ravi <rshankar@codeaurora.org>
Enable required audiosource driver that is required for audio
over accessory dock to work.
Change-Id: Ifeb779a3323c505d482eb53ad96a1b8aec0f3af5
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
As audio-ext-clk.h is finally included in device tree and
and using ifdef results in compilation failure. Delete
ifdef from audio-ext-clk.h.
CRs-Fixed: 1090500
Change-Id: Ib6f715c3f606770e7e0b1f0f84ab50e442398cd0
Signed-off-by: Meng Wang <mwang@codeaurora.org>
Add support of PMFALCON PMIC in FG driver. PMFALCON
FG core uses same SRAM map as PMI8998v2.0.
While at it, add workaround flag variable to keep track
of all hardware specific workarounds.
CRs-Fixed: 1096793
Change-Id: I8ba73276fd30f6eaf935ed77b75601f1322c0ba6
Signed-off-by: Ashay Jaiswal <ashayj@codeaurora.org>
The smb138x parallel charger device has a watchdog timer that will
disable parallel charging if it is not pet by software. Enable it.
Change-Id: Ie28323cdabccdc64196fae25deb2f56dfbb5a0e7
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
Specify the graphics coresight trace ID in the device tree
file.
Change-Id: I30a10a63b320cd3cb6d7cc4ef2fba423f697a66f
Signed-off-by: Harshdeep Dhatt <hdhatt@codeaurora.org>
Add properties in the GPU device tree for coresight. Define GPU
name and its funnel connections.
CR-fixed: 988516
Change-Id: Ibf2e369c2a4732ebc7471ee103bc8d5d934247ec
Signed-off-by: Lokesh Batra <lbatra@codeaurora.org>
In WDI2.0, seeing some issue about rdy_ring_rp_va
is not equal to rdy_comp_ring_wp_va because wlan-fw
still update the doorbell after ipa host-driver
issue the CH_DISABLE cmd to ipa-uc. The fix is
to compare rdy_comp_ring_wp_va and rx_door_bell
values instead.
Change-Id: Ibe57c7d5ba9e45260c12528910f173e347259d7c
Signed-off-by: Skylar Chang <chiaweic@codeaurora.org>
LMH DCVSh hardware doesn't generate a debug interrupt, when HLOS
CPU frequency cap is the only throttling value coming to the hardware
aggregator logic. The LMH DCVSh requires atleast one of the hardware
algorithm to throttle to generate a debug interrupt. So there will be
a case where, LMH DCVS driver won't notify scheduler about the
throttling frequency if HLOS is the only reason for throttling.
LMH DCVSh driver now exposes a new API, to trigger the frequency polling
loop. KTM is updated to use this API to trigger the LMH DCVSh polling,
whenever there is a new software frequency cap. This will ensure that
the LMH DCVSh will notify the scheduler even if software is the only
throttling reason.
Change-Id: I92b1bd9a5efc9810eea721b088dff1bd6eef3838
Signed-off-by: Ram Chandrasekar <rkumbako@codeaurora.org>
kgsl_ioctl_gpu_sparse_command() is added to for user to
specify list of binds/unbinds for a memory entry
and syncpoints they depend on. If user specifies both
create a sync object for syncpoints and bind object for
binds/unbinds and add them to dispatcher draw queue. Sync
object should be inserted before the bind object in the
draw queue. Once the bind object reaches the head of
draw queue the corresponding binds/unbinds are performed.
kgsl_ioctl_gpu_sparse_command() only accepts commands from
context created with flag KGSL_CONTEXT_SPARSE, commands
from all other context types will return an error.
Change-Id: Ib0a2361f854ae01d0d8090cdd48cfa96308daf93
Signed-off-by: Tarun Karra <tkarra@codeaurora.org>
This property will be used to indicate to the boost current
after the boost is turned on.
CRs-Fixed: 1095917
Change-Id: Ie667fa49c4a8e8c008e8866f655e3bbe3e69e156
Signed-off-by: Harry Yang <harryy@codeaurora.org>
HLOS can place a mitigation frequency via the LMH DCVSh hardware using
the software cap register and this request doesn't trigger a debug
interrupt. Thus, this frequency mitigation change will not result in
scheduler being notified by LMH DCVSh driver.
Introduce a new API in LMH DCVSh driver, that can be used by other
drivers to trigger the scheduler notification. This API and the
interrupt handler follows the same code path to poll and notify the
scheduler.
Change-Id: Iefcdb57ff598ecb1bafc535958684f75b1f6e645
Signed-off-by: Ram Chandrasekar <rkumbako@codeaurora.org>
Add the support for trace ID for coresight. This ID is
will be defined in the respective device tree file.
Change-Id: I78ba05ed05b54fdc0f4d4f55c468f90f39c821f1
Signed-off-by: Lokesh Batra <lbatra@codeaurora.org>
Signed-off-by: Harshdeep Dhatt <hdhatt@codeaurora.org>
In order to share the usb audio qmi device iova with lpass usb audio
driver, attach usb audio qmi device to lpass q6 iommu using sid 6.
Change-Id: I6b3c9b49ac973f2472391b3f702908212e3f6e7d
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
Update the SMMU device node configuration for correct operation of SMMU
on msmfalcon.
Change-Id: I29fa8f488df800d38f6403646e58a19e555ba1cd
Signed-off-by: Charan Teja Reddy <charante@codeaurora.org>
Enable USB video class support for msmfalcon for host video usecases.
Change-Id: I30f8294527275a267bd88115a8a8d44beb2adfb8
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
LCDB driver exposes regulators to control the positive and
negative voltage bias for the LCD display panel. It also
allows configurability for the various bias-voltage parameters.
CRs-Fixed: 1074468
Change-Id: I68958c5ecfb71a11f346c5c46884948e4b36eea0
Signed-off-by: Ashay Jaiswal <ashayj@codeaurora.org>
BT and WLAN vote for the regulator-mode via pinctrl. Add
support for this.
Change-Id: I95158cce1b20778547615141ffbbb7d81d5e10a1
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
In failure case pointer to resource for restart register may be used while
it is uninitialized. So use proper NULL check for the same.
Change-Id: I3fc77b72e825f4b11724808239eea16aa126de42
Signed-off-by: Gaurav Kohli <gkohli@codeaurora.org>
Enable SCSI_UFS_QCOM_ICE for msmfalcon_32 which is required
for hardware encryption.
Change-Id: I6f9afca5bebd5ad0745b064bb7d1a33f78fe6941
Signed-off-by: AnilKumar Chimata <anilc@codeaurora.org>
Enable EXT4_FS_ICE_ENCRYPTION feature for msmfalcon_32
to use ICE for FBE.
Change-Id: I991f3550720526b097c009dc852e9caaabf4860b
Signed-off-by: AnilKumar Chimata <anilc@codeaurora.org>
Add missing required properties for USB node for msmfalcon for
USB functionality to be working.
Change-Id: I602cac95616da34ffe6462c8cf3af85ce973085b
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
There are 2 issues with setting the vdd-phy voltage:
1. The min & max range that's defined is 1v, whereas
0.925 (+/- 5%) is the required voltage. A range of
0.8v to 0.925v would suffice.
2. This defined range is over-ridden with the current
rail-voltage. This assumes that some consumer has
set the regulator to the correct voltage.
This change corrects the defined min/max range to
0.8v-0.925v for vdd-phy.
It also removes the code that's causing [2].
CRs-fixed: 1095116
Change-Id: I943bc4f38385036b21c1f9a2e479d6e94ac12813
Signed-off-by: Asutosh Das <asutoshd@codeaurora.org>
PM2FALCON GPIO 7 is connected to VOL_UP key. Add the
PMIC and GPIO key configuration for GPIO 7.
Change-Id: Ie1dcc85f579e0b9817a104be86bbb9e91771b15c
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
Since we move to GEF implementation for Dolby post processing,
disabling DAP/DAX2 driver logic on msm8998 target except for
license validation.
CRs-Fixed: 1094027
Change-Id: I33c5625026611856f6cdd8c6e0b5d7ef229ba8c7
Signed-off-by: Weiyin Jiang <wjiang@codeaurora.org>
Add feed state check whether any filter is configured on dvbdemux
feed before feed stop is called. If any filter is started the feed
status should be set to DMX_STATE_GO.
CRs-Fixed: 1090466
Change-Id: If9e87065bb9fb82befb398f2a3a0d0da2f76efa5
Signed-off-by: Udaya Mallavarapu <udaym@codeaurora.org>
Add core hang detect node for msmfalcon which enables the
core hang detect feature. Enable the same for msmtriton
also.
Change-Id: I108451bae429c8e4c858f7f549c4202f3d59a6d2
Signed-off-by: Venkatesh Yadav Abbarapu <vabbar@codeaurora.org>
Currently userspace data is getting accessed directly
and leading to crash, So use get_user() API to copy
userspace data/settings to kernel space.
Change-Id: I3a75ec9503d8207829640bf88e1c3160bf72c9f0
Signed-off-by: Mohammed Khajapasha <mkhaja@codeaurora.org>
Update regulators for clocks and usb phy.
CRs-Fixed: 1096674
Change-Id: Ib205ccebaec612fd9d1d6bb1a02a4f14be8f21c1
Signed-off-by: Zhenhua Huang <zhenhuah@codeaurora.org>
