[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240315172632.6zxwj4enq4tddbb3@bogus>
Date: Fri, 15 Mar 2024 17:26:32 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Doug Anderson <dianders@...omium.org>
Cc: Maulik Shah <quic_mkshah@...cinc.com>, andersson@...nel.org,
Sudeep Holla <sudeep.holla@....com>, ulf.hansson@...aro.org,
swboyd@...omium.org, wingers@...gle.com, daniel.lezcano@...aro.org,
rafael@...nel.org, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
jwerner@...omium.org, quic_lsrao@...cinc.com,
quic_rjendra@...cinc.com, devicetree@...r.kernel.org,
Abhinav Kumar <quic_abhinavk@...cinc.com>,
Jessica Zhang <quic_jesszhan@...cinc.com>,
Rob Clark <robdclark@...omium.org>
Subject: Re: [RESEND v4 3/3] arm64: dts: qcom: sc7280: Add power-domains for
cpuidle states
On Fri, Mar 15, 2024 at 10:12:12AM -0700, Doug Anderson wrote:
> Hi,
>
> On Fri, Mar 15, 2024 at 8:24 AM Sudeep Holla <sudeep.holla@....com> wrote:
> >
> > On Thu, Mar 14, 2024 at 04:20:59PM -0700, Doug Anderson wrote:
> > > Hi,
> > >
> > > On Mon, Jul 3, 2023 at 1:56 AM Maulik Shah <quic_mkshah@...cinc.com> wrote:
> > > >
> > > > Add power-domains for cpuidle states to use psci os-initiated idle states.
> > > >
> > > > Cc: devicetree@...r.kernel.org
> > > > Reviewed-by: Ulf Hansson <ulf.hansson@...aro.org>
> > > > Signed-off-by: Maulik Shah <quic_mkshah@...cinc.com>
> > > > ---
> > > > arch/arm64/boot/dts/qcom/sc7280.dtsi | 98 +++++++++++++++++++++-------
> > > > 1 file changed, 73 insertions(+), 25 deletions(-)
> > >
> > > FWIW, I dug up an old sc7280-herobrine board to test some other change
> > > and found it no longer booted. :( I bisected it and this is the change
> > > that breaks it. Specifically, I can make mainline boot with:
> > >
> > > git revert --no-edit db5d137e81bc # arm64: dts: qcom: sc7280: Update
> > > domain-idle-states for cluster sleep
> > > git revert --no-edit 7925ca85e956 # arm64: dts: qcom: sc7280: Add
> > > power-domains for cpuidle states
> > >
> >
> > IIRC, this could be issue with psci firmware. There were some known
> > issues which were discussed few years back but I am not aware of the
> > details and if/how it is applicable here.
> >
> > Not sure if you are getting any logs during the boot, if you do have
> > worth look at logs related to PSCI/OSI/Idle/...
>
> Given that the new firmware fixes it I'm going to say it's not worth
> looking into any longer.
>
But it would be good to know if that is the exact reason, see if it can
be upgraded, or else we can disable them by default. The bootloader or
something else can detect the f/w version and enable them so that the
board with old f/w(if can't be upgraded) can still be used.
Otherwise it is a regression IMO.
--
Regards,
Sudeep
Powered by blists - more mailing lists