In soc compress open fail, handle cleanup of backend
to avoid backend related issues after it during
stability SSR(Subsystem restart) tests.
Change-Id: Ib4417668e308f191b832d06601ef64bfa3bcd318
Signed-off-by: Laxminath Kasam <lkasam@codeaurora.org>
The Zero C sensor reports TSENS controller min temperature as its
sensor value to the thermal framework. It requires a low trip
monitor governor in thermal framework to monitor cold
temperature condition.
Instead of min temp value, use TSENS Zero C interrupt status as
sensor value. It removes the need for cold trip monitoring
governor and uses the existing governors to monitor the cold trip
condition and trigger mitigation.
Change-Id: I8bc3a76c5868d679d5f057f8722306a5b8d3fc98
Signed-off-by: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>
Add GPIO pins that are routed to PDC interrupt controller and can be
used as wakeup capable GPIOs.
Change-Id: If2044dfe89f7593ee3a6fd843866d4f86f3f42a6
Signed-off-by: Lina Iyer <ilina@codeaurora.org>
Signed-off-by: Tushar Nimkar <tnimkar@codeaurora.org>
With active-mode memory offlining, it would be helpful to track the
total Online and Offline times of each blocks and determine percentage
of time they have been in that state.
This patch adds the below additional stats:
- current state of each blocks.
- total Online and Offline time of each blocks.
- percentage of total system runtime that blocks were in Online
and Offline state.
- total overall percentage of time all blocks were in Online
and Offline state.
Also, change the sysfs node from 'perf_stats' to 'stats'.
Change-Id: Ie18ad68194df8c7702dc496821c4f680d15486ce
Signed-off-by: Sudarshan Rajagopalan <sudaraja@codeaurora.org>
With charger mode enabled in android, device boots into charger
mode when it is powered on with USB insertion. In this mode,
health HAL and charger service handles the power supply uevents
sent from power supply framework to take certain actions. For
example, when the USB or travel adapter (TA) is removed, device
would shut down in 10 seconds.
With a TA connected, device can enter suspend whenever possible
during charging. When the TA is removed after the device has
entered suspend, device comes out of suspend upon the notification
received from charger firmware (CHGFW) over PMIC Glink. Battery
charger driver handles this and calls power_supply_changed on one
of the power supply devices. However, before this uevent is
received and handled by charger service in the userspace, device
can enter suspend immediately.
In a low power discharging state, device stays in this state for
minutes until it gets another notification from CHGFW for battery
power supply, a periodic event which makes charger service to
initiate a shutdown. This conflicts with the user expectation
where the device has to shutdown in 10 seconds upon TA removal.
Workaround this problem by keeping the device awake for at least
50 ms when a notification is received from CHGFW. This way,
userspace process like charger could get a chance to receive and
handle the power supply uevents.
Change-Id: I9ea78eb6565988ffac0e6c5eee1ccae8dc7e3e3a
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
If minidump is configured to be ELF32, avoid using complete
ramdump property, so that only the required segments area is
dumped.
Change-Id: I34fe359204309fda47d0a665ca641cb042d87054
Signed-off-by: Neeraj Upadhyay <neeraju@codeaurora.org>
Signed-off-by: Mukesh Ojha <mojha@codeaurora.org>
Update the ABI snapshot version with the release of the new feature in
libabigail which also does CRC checks.
Change-Id: I0112a733015f608d53351c96a56f86e9086aee76
Signed-off-by: Siddharth Gupta <sidgup@codeaurora.org>
Add a new property, to dump minidump ELF in ELF32 format,
as some subsystems do not support the default format,
which is ELF64.
Change-Id: I87bc46097b4dfc0be44f0904823c5e88c476c86b
Signed-off-by: Neeraj Upadhyay <neeraju@codeaurora.org>
Signed-off-by: Mukesh Ojha <mojha@codeaurora.org>
Hook into preemptirq trace points and print the call stacks of
scenarios where preemption/irqs is disabled for more than
a use configured threshold. The threshold tunables are available
under /proc/sys/preemptirq directory. All the units are in nano seconds.
The following commands can be used to enable the trace. The stacktrace
trigger prints the stacktrace when the trace event is printed.
echo 1 > /d/tracing/events/preemptirq_long/enable
echo stacktrace > /d/tracing/events/preemptirq_long/preempt_disable_long/trigger
echo stacktrace > /d/tracing/events/preemptirq_long/irq_disable_long/trigger
Sample output is copied below. Note that this format works with both systrace
and commandline ftrace utilities.
init-1 [005] d..2 187.905211: irq_disable_long: delta=15244480(ns)
init-1 [005] d..3 187.905216: <stack trace>
=> test_irq_disable_long
=> trace_irq_enable_rcuidle
=> trace_hardirqs_on
=> console_unlock
=> vprintk_emit
=> devkmsg_emit
=> devkmsg_write
=> do_iter_readv_writev
=> do_iter_write
=> do_writev
=> __arm64_sys_writev
=> el0_svc_common
=> el0_svc_handler
=> el0_svc
kworker/u16:4-419 [000] .N.2 187.905221: preempt_disable_long: delta=4923646(ns)
kworker/u16:4-419 [000] .N.3 187.905226: <stack trace>
=> test_preempt_disable_long
=> trace_preempt_enable_rcuidle
=> trace_preempt_on
=> preempt_count_sub
=> perf_event_read
=> __perf_event_read_value
=> perf_event_read_value
=> memlat_monitor_work
=> process_one_work
=> worker_thread
=> kthread
=> ret_from_fork
Change-Id: If87a8d65359632b93da10b691e9b83e37000aeb3
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>