From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Amit Kucheria <amit.kucheria@linaro.org>
Cc: MSM <linux-arm-msm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Andy Gross <agross@kernel.org>,
Jeffrey Hugo <jhugo@codeaurora.org>
Subject: Re: [PATCH v2 7/9] arm64: dts: qcom: msm8998: Add PSCI cpuidle low power states
Date: Tue, 21 May 2019 18:10:17 +0200 [thread overview]
Message-ID: <9dfe47bc-9f37-e494-271b-b343205c8073@free.fr> (raw)
In-Reply-To: <a7514c68-d2d3-ce9e-bc4b-f484bb5bf3cf@free.fr>
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.
next prev parent reply other threads:[~2019-05-21 16:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 9:35 [PATCH v2 0/9] qcom: Add cpuidle to some platforms Amit Kucheria
2019-05-21 9:35 ` [PATCH v2 1/9] arm64: dts: fsl: ls1028a: Fix entry-method property to reflect documentation Amit Kucheria
2019-05-21 9:35 ` [PATCH v2 2/9] Documentation: arm: Link idle-states binding to "enable-method" property Amit Kucheria
2019-06-13 23:13 ` Rob Herring
2019-05-21 9:35 ` [PATCH v2 3/9] arm64: dts: qcom: msm8916: Add entry-method property for the idle-states node Amit Kucheria
2019-05-22 3:30 ` Bjorn Andersson
2019-05-21 9:35 ` [PATCH v2 4/9] arm64: dts: qcom: msm8916: Use more generic idle state names Amit Kucheria
2019-05-22 3:30 ` Bjorn Andersson
2019-05-21 9:35 ` [PATCH v2 5/9] arm64: dts: qcom: qcs404: Add PSCI cpuidle low power states Amit Kucheria
2019-05-22 3:31 ` Bjorn Andersson
2019-05-21 9:35 ` [PATCH v2 6/9] arm64: dts: qcom: msm8996: " Amit Kucheria
2019-05-21 10:13 ` Daniel Lezcano
2019-05-22 3:49 ` Bjorn Andersson
2019-05-23 21:24 ` Niklas Cassel
2019-05-21 9:35 ` [PATCH v2 7/9] arm64: dts: qcom: msm8998: " Amit Kucheria
2019-05-21 12:03 ` Marc Gonzalez
2019-05-21 16:10 ` Marc Gonzalez [this message]
2019-09-30 22:20 ` Jeffrey Hugo
2019-09-30 22:44 ` Amit Kucheria
2019-10-01 14:21 ` Jeffrey Hugo
2019-10-02 9:19 ` Niklas Cassel
2019-10-02 9:27 ` Niklas Cassel
2019-10-02 18:18 ` Jeffrey Hugo
2019-10-04 1:36 ` Amit Kucheria
2019-10-04 3:14 ` Jeffrey Hugo
2019-05-21 9:35 ` [PATCH v2 8/9] arm64: dts: qcom: sdm845: " Amit Kucheria
2019-05-22 3:59 ` Bjorn Andersson
2019-05-21 9:35 ` [PATCH v2 9/9] arm64: dts: msm8996: Add proper capacity scaling for the cpus Amit Kucheria
2019-05-21 10:14 ` Daniel Lezcano
2019-05-22 3:50 ` Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9dfe47bc-9f37-e494-271b-b343205c8073@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=agross@kernel.org \
--cc=amit.kucheria@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®