Non-atomic scm call which could be interrupted, trustzone will store
the session id in a register(r6) which will be used when trustzone resumes
the call.
To avoid r6 being used by compiler, HLOS now uses it to send a zero before
making scm call.
Change-Id: I2927efe04fd019d551aae5e6548da3fb5c18b655
Signed-off-by: Taniya Das <tdas@codeaurora.org>
During modem WDOG bite scenarios, error handlers are not executed
in modem. So Adrastea may not be in reset when SSR notifications
are received in HLOS. Remapping MSA0 during SSR could cause SMMU
fault at Adrastea, as it may be still accessing it. Skip collecting
MSA0 dump in WDOG bite scenarios.
CRs-Fixed: 1102057
Change-Id: I9082d4d40b70d0ca8cc8fbc6aadf14b2f0aedd0c
Signed-off-by: Sameer Thalappil <sameert@codeaurora.org>
In some specific cases, clients may want to know why subsystem
crashed, for example, in case of watch dog bite, subsystem may not
be able to execute error handling. Which would need different code
paths to be exercised on the apps processor.
Change-Id: I073733b8a56b57f14906b25cba08012c2f0b414a
Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@codeaurora.org>
As it turns out, the KASLR code breaks CONFIG_MODVERSIONS, since the
kcrctab has an absolute address field that is relocated at runtime
when the kernel offset is randomized.
This has been fixed already for PowerPC in the past, so simply wire up
the existing code dealing with this issue.
Change-Id: Ib01e32f2c5cd3d6feff6321a897ed8d276bc3be3
Cc: <stable@vger.kernel.org>
Fixes: f80fb3a3d508 ("arm64: add support for kernel ASLR")
Tested-by: Timur Tabi <timur@codeaurora.org>
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Git-commit: 9c0e83c371cf4696926c95f9c8c77cd6ea803426
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: Runmin Wang <runminw@codeaurora.org>
Right now the vmpressure window is of constant size 2MB, which
works well with the following exceptions.
1) False vmpressure triggers are seen when the RAM size is greater
than 3GB. This results in lowmemorykiller, which uses vmpressure
events, killing tasks unnecessarily.
2) Vmpressure events are received late under memory pressure. This
behaviour is seen prominently in <=2GB RAM targets. This results in
lowmemorykiller kicking in late to kill tasks resulting in avoidable
page cache reclaim.
The problem analysis shows that the issue is with the constant size
of the vmpressure window which does not adapt to the varying memory
conditions. This patch recalculates the vmpressure window size at
the end of each window. The chosen window size is proportional to
the total of free and cached memory at that point.
Change-Id: I7e9ef4ddd82e2c2dd04ce09ec8d58a8829cfb64d
Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org>
Remove rpm-standalone flag under rpm_bus to allow communication
between APPS and RPM processors for msmfalcon.
Change-Id: I1736dc8a2a34ece02aaec70c867c7a0993fa82c7
Signed-off-by: Raju P.L.S.S.S.N <rplsssn@codeaurora.org>
Model and configure MDSS DSI PLL using upstream clock framework
APIs. Add changes to define and register vco, divider, mux clcoks
as per common clock infrastructure.
Change-Id: Idc51070e2bb36d1a757d2714d2875a99901321a7
Signed-off-by: Sandeep Panda <spanda@codeaurora.org>
In smblib_get_prop_usb_online() and smblib_get_prop_dc_online(),
used incorrect VALID_INPUT_POWER_SOURCE_BIT check. Now change
to VALID_INPUT_POWER_SOURCE_STS_BIT check.
Change-Id: I70489775b2a99afff8b26366758834a98b1ffb30
Signed-off-by: Vic Wei <vwei@codeaurora.org>
CRs-Fixed: 1102132
It is needed to enable remote file system on modem processor, which
needs access to store data onto eMMC/UFS device.
The shared memory size used by modem and apps for this purpose is 2MB
on msmfalcon.
Change-Id: Id0cdd7f27b42c261966bb5e92d8229fa234445c4
Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
For a full battery, the driver currently reports battery full
only when the charger is online and switches back to reporting
discharging when charger is removed.
This is incorrect because a user might reinsert the charger
seeing discharging status right after he removes it only to
realize that the battery is full after he plugs it back.
So allow the full status to be reported even when no charger is
online.
Change-Id: I0c31e2fbe984420a6754e923cfc3abe77bc54991
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
A boost current threshold will be referenced in deciding
optimal boost switching frequency for efficiency.
CRs-Fixed: 1095917
Change-Id: I1e738e66cdfb72305dd4256dc0a6e05b03de585e
Signed-off-by: Harry Yang <harryy@codeaurora.org>
Currently, the default boost switching frequency is fixed at 800KHz,
which shows low efficiency in low USB load.
To improve it, only use the default 800KHz when boost current goes
above 100mA; otherwise, switch to 2MHz.
CRs-Fixed: 1095917
Change-Id: Iebb62303febfb78738ada4553fdb9b9eb4810ed5
Signed-off-by: Harry Yang <harryy@codeaurora.org>
This reverts commit 2a8225ef46
("sched/cputime: Fix steal time accounting vs. CPU hotplug").
The commit introduces a bug in scheduler book-keeping whereby if a CPU
is hotplugged out for a small duration of time, subsequent time spent
executing tasks gets mis-attributed to interrupts. This in turn results
in unfair scheduling whereby a task can keep executing for a very long
time without any update to it's vruntime. This revert has no side
effects for msm based systems.
Change-Id: Ibb506824c4223551bceb449594ac99f9dfd8064b
Signed-off-by: Syed Rameez Mustafa <rameezmustafa@codeaurora.org>
Disable the aio interface as we do not use this for performance
benefits.
Change-Id: Ibbe1845c673f3a422b013d17492790c79c78d076
Signed-off-by: Runmin Wang <runminw@codeaurora.org>
The original change to set 200mV boost PFM threshold at request
of a HW workaround is no longer needed, set as default now in
SBL. Remove it.
CRs-Fixed: 1095917
Change-Id: I4e041dafa83d935a5c16c96bea7a3ea488e80d87
Signed-off-by: Harry Yang <harryy@codeaurora.org>
Remove the write of acc strap register by default value during Q6 reset
as per Hardware Programming Guide.
Change-Id: Id5b8aaae0783893290e95626b394841a7d3808a3
Signed-off-by: Gaurav Kohli <gkohli@codeaurora.org>
Update the reset sequence to read each write while enabling QDSP6 memory
bank one at a time. This will make sure whether write is complete or not.
Also add logs during Mss shutdown, It will help to debug Mss restart
and shutdown case.
Change-Id: I9f2cb058a7e59b573fc64662ee7b5bff49b18ea7
Signed-off-by: Gaurav Kohli <gkohli@codeaurora.org>
Add asm loopback FE DAI to support the audio asm loopback
use case for msm8998 platform.
CRs-Fixed: 1099656
Change-Id: Ia1c6d8dfd75eb21cde8de7b9bfcab4e4277e339f
Signed-off-by: Kuirong Wang <kuirongw@codeaurora.org>
Update speaker left and right GPIOs for APQ8998 platform since it
uses different GPIOs from MSM8998 platform.
CRs-Fixed: 1099656
Change-Id: Idecd865b7a11e4cd30737f5d800673c87807592c
Signed-off-by: Kuirong Wang <kuirongw@codeaurora.org>