Refactor the soc watchdog driver to use the
qcom watchdog framework.
Change-Id: I12a6afff4299bb39cacca27bcf483e08a503add0
Signed-off-by: Branden Bonaby <[email protected]>
Separate core watchdog functionality from the qcom watchdog
driver to create a framework for other qcom watchdogs. This
will reduce the duplication of code for future watchdog
drivers and allow them to take advantage of this framework.
Change-Id: I1234af9d92de6841bd09157042a4fbba1745f11b
Signed-off-by: Branden Bonaby <[email protected]>
Refactor watchdog core to remove the bark percpu
interrupt as it is deprecated and no longer used
by the watchdog.
Change-Id: Idbd959a7b42895d72f4f812057304687f7aca948
Signed-off-by: Branden Bonaby <[email protected]>
Refactor watchdog core to remove unused member
variables in the watchdog data structure.
Change-Id: I3a83fdb291064f25721549a3fe70f97629c148b4
Signed-off-by: Branden Bonaby <[email protected]>
Refactor watchdog core to remove dead code. Specifically,
the slack variables from the watchdog data structure and
the pet function that uses them. Currently these variables
are not used and can be refactored to simply reset the
watchdog counter directly.
Change-Id: Ie184e2826ed790288a94dfebf578ec99b53831e8
Signed-off-by: Branden Bonaby <[email protected]>
In preparation to change the qcom watchdog to a new core
framework that future watchdog drivers will utilize, the name
of the file needs to be changed. Due to the number of changes
needed in the file we need to rename it to reflect its new purpose.
Change-Id: Iac6ad57fbc02866f6716a44d7bb4a62d97e4a810
Signed-off-by: Branden Bonaby <[email protected]>
Remove qcom watchdog config in preparation for the
creation of the watchdog core.
Change-Id: I964285a5ad06dc5753756d821bd0f4fc1d664739
Signed-off-by: Branden Bonaby <[email protected]>
Change adds kernel_restart to qcom KMI symbol list and updates
the ABI snapshot, as it is used by spss_utils driver.
Change-Id: Iedb73f0aeb092989461078cc403695e24fbe8146
Signed-off-by: Konstantin Dorfman <[email protected]>
Bail out if device returns invalid bhi/bhie offsets.
Change-Id: Ifc92c53a4c1f7c951721cbec0b1d7285cf19cd72
Signed-off-by: Manu Gautam <[email protected]>
It can be used by MHI core to have a sanity check for
bhi and bhie offsets reported by device.
Change-Id: Ibcdef53a4c1f7c951721cbec0b1d7285cf19cd72
Signed-off-by: Manu Gautam <[email protected]>
If mhi_get_exec_env API returns MHI_EE_MAX skip RDDM download.
API returns this value if BHI offset read failed or BHI_EXECENV
register read fails. This indicates the underlying transport is
unresponsive so there is no need to trigger RDDM using SYSERR
or request SOC reset.
Change-Id: I0cc85af84f19b425c94fe8aea987ab03af6de032
Signed-off-by: Hemant Kumar <[email protected]>
In case power up failed due to incorrect bhi offset
bhi pointer in mhi controller remains NULL. Later if
MHI controller forces RDDM it checks the execution
environment by accessing the BHI offset. This results
into NULL pointer dereference. Fix this by adding NULL
check for both mhi controller and bhi pointer before
reading the BHI offset.
Change-Id: I93f8918d7d595a77a5c8bcb6fd610f1a2b484fc4
Signed-off-by: Hemant Kumar <[email protected]>
A memory request may not be satisfied in time because of delays
in allocation times. When the allocation response is given to the
consumer, but the consumer's request has already timed out, the
memory will be leaked, as it won't be claimed by the consumer, and
it won't be relinquished to the supplier. Thus, to prevent the memory
from being leaked, relinquish unclaimed memory back to the supplier.
Change-Id: I91f52113c26f4536789fe6807175c845cc9c9e26
Signed-off-by: Isaac J. Manjarres <[email protected]>
Use an unbound high priority workqueue to ensure that mem-buf
transactions can be handled on any CPU, as well as with high
priority. Also, increase the timeout for allocation responses
from 2 seconds to 3.5 seconds.
Change-Id: I2ec4d85bf7307d64d2f8a7dae6dfb2b29cfc45bb
Signed-off-by: Isaac J. Manjarres <[email protected]>
Dump stack is observed when mutex (typec_lock) is locked without
initializing it in case of PD supported typec designs. Fix it by
initializing the mutex for PD supported typec designs also.
Change-Id: I7ee29715651dc001a450d80c49c6cce10f10e837
Signed-off-by: Shyam Kumar Thella <[email protected]>
This change is for general scheduler improvement.
Change-Id: I5e27121c3625d21d0a5abedcda9bcbfc947f5359
Signed-off-by: Pavankumar Kondeti <[email protected]>
Set the bhi and bhie pointers to NULL as part of clean
up. This makes sure that stale pointers are not accessed
in case the bhi or bhie is failed to initialize during
power up.
Change-Id: Iddbd3a8234ff4d384ab03081479d55faf10d9443
Signed-off-by: Hemant Kumar <[email protected]>
Collects data from SMEM region when modem crashes
and stores it under /dev to expose to user space.
Change-Id: I6b79a2ea7f7d9d7507e8c44dd1d385a185759ac1
Signed-off-by: Shawn Shin <[email protected]>
When RC_CLK_CAL_EN is set in auto mode while haptics boost is working
in open loop, the first cycle of the vibration would be played
incorrectly because the haptics module couldn't get enough clock count
before the play gets triggered. Fix this by toggling the RC clock
calibration mode from disabled to auto mode.
Change-Id: I80b3c48b9bb508b12841a679eafa2c618771edf2
Signed-off-by: Fenglin Wu <[email protected]>
During LRA frequency calibration, reading CAL_TLRA_CL_STS has to be
done before de-asserting play. In the boot up LRA frequency calibration
sequence, CAL_TLRA_CL_STS was read out and stored in SDAM module
registers by the bootloader. Later, HLOS haptics driver can read it from
there and use it for calculating LRA frequency. This boot up LRA
frequency calibration sequence is only available for PM8350B 2.0 chip.
Update the driver to support this.
Change-Id: I0b81e79bad57160f9c79e01151e2d4060b4bbd41
Signed-off-by: Fenglin Wu <[email protected]>
RC_CLK_CAL_COUNT is the calibration count used in manual RC_CLK_CAL
mode when playing FIFO patterns. For haptics module in PM8350B 2.0,
there are new equations recommended to calculate RC_CLK_CAL_COUNT
based on CAL_TLRA_CL_STS and LAST_GOOD_TLRA_CL_STS status to achieve
better accuracy. Update the driver to support this.
Change-Id: I983c1b1f284006847549d2b3d23a0c1039f8b4c1
Signed-off-by: Fenglin Wu <[email protected]>
Enable RCU NOCB_CPU and FAST_NO_HZ options for the lahaina. These configs
are needed to avoid frequent cpu wake up for processing rcu callbacks.
Whenever LPM governor driver has requested for sleep length
tick_nohz_get_sleep_length tries to find the next event from
tick_nohz_next_event function.
static ktime_t tick_nohz_next_event(struct tick_sched *ts, int cpu)
{
...
if (rcu_needs_cpu(basemono, &next_rcu) || arch_needs_cpu() ||
irq_work_needs_cpu() || local_timer_softirq_pending()) {
next_tick = basemono + TICK_NSEC;
} else {
tick_nohz_next_event calls rcu_needs_cpu to find whether future
non-offloaded RCU-related work need to be done by the current CPU
or not. If any non-offloaded future callbacks are present rcu
framework requests the cpu to wake up for every tick period to
process the callbacks.
When CONFIG_FAST_NO_HZ is defined rcu_needs_cpu function checks whether
any callbacks are ready to process or not. If there are no ready
call backs and no non-offloaded callbacks pending for this CPU, RCU
doesn't need the CPU and returns KTIME_MAX for sleep length. Another
important thing is that, if CPU has lazy callbacks or future non-offload
RCU callbacks, rcu framework try to advance those callbacks and allows
the CPU to enter dyntick-idle mode.
RCU_NOCB_CPU config option helps to offload callback invocation from
the set of CPUs to kthread ("rcuox/N") and reduce OS jitter for
aggressive high performance computing workloads.
Change-Id: I47cdd2a3528e3a447a6909bf3f840ee8a3dd4b1e
Signed-off-by: Prasad Sodagudi <[email protected]>
Signed-off-by: Raghavendra Rao Ananta <[email protected]>
Make the debug function target specific since
it was anyways used in only two places and it also
simplifies a bunch of indirect register reads
we had to do because of ADRENO_REG enum.
Change-Id: I20fcd91339639d999d475dae60f95a357721b71d
Signed-off-by: Urvashi Agrawal <[email protected]>
Some registers only exist on A660, add logic to capture
these into the snapshot.
Change-Id: I21bef72768cdb9597906ae9996c8988de1a00f7f
Signed-off-by: Urvashi Agrawal <[email protected]>
