[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9dfe47bc-9f37-e494-271b-b343205c8073@free.fr>
Date: Tue, 21 May 2019 18:10:17 +0200
From: Marc Gonzalez <marc.w.gonzalez@...e.fr>
To: Amit Kucheria <amit.kucheria@...aro.org>
Cc: MSM <linux-arm-msm@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Andy Gross <agross@...nel.org>,
Jeffrey Hugo <jhugo@...eaurora.org>
Subject: Re: [PATCH v2 7/9] arm64: dts: qcom: msm8998: Add PSCI cpuidle low
power states
On 21/05/2019 14:03, Marc Gonzalez wrote:
> the system starts to boot, hangs a few seconds, then silently reboots
Using extremely high-tech debugging tools (i.e. spraying printk left and right)
I traced this one down to:
psci_cpu_suspend_enter: 435
psci_cpu_suspend: 171
psci_cpu_suspend: __invoke_psci_fn_smc c4000001
__invoke_psci_fn_smc: id=c4000001 3 0 0
/*** we never return from arm_smccc_smc() ***/
The following dmesg log caught my eye, and might be relevant:
ARM_SMCCC_ARCH_WORKAROUND_1 missing from firmware
If I revert your patch, psci_cpu_suspend_enter() is never called,
so we don't tickle the arm_smccc_smc() monster.
Could it be that my FW doesn't support PSCI?
Regards.
Powered by blists - more mailing lists