From: Sudeep Holla <sudeep.holla@arm.com>
To: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
Etienne Carriere <etienne.carriere@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Heiko Stuebner <heiko@sntech.de>, Liang Chen <cl@rock-chips.com>,
linux-kernel@vger.kernel.org,
Kever Yang <kever.yang@rock-chips.com>,
Jeffy Chen <jeffy.chen@rock-chips.com>,
Peter Geis <pgwipeout@gmail.com>
Subject: Re: [BUG] New arm scmi check in linux-next causing rk3568 not to boot due to firmware bug
Date: Thu, 5 May 2022 11:10:32 +0100 [thread overview]
Message-ID: <20220505101032.icqb2hau4dhj3afr@bogus> (raw)
In-Reply-To: <CAN5uoS_MgBiTVZCRSZyYCH4cnUZD_bHj2+mZu661bFV8TKWScw@mail.gmail.com>
> > > > On Wed, May 04, 2022 at 02:49:07PM +0200, Nicolas Frattaroli wrote:
> > > > > Good day,
> > > > >
> > > > > a user on the #linux-rockchip channel on the Libera.chat IRC network
> > > > > reported that their RK3568 was no longer getting a CPU and GPU clock
> > > > > from scmi and consequently not booting when using linux-next. This
> > > > > was bisected down to the following commit:
OK I missed to read the above properly earlier. If scmi probe failure is
resulting in Linux boot failure, then that is another bug that needs fixing.
Why does not getting CPU clock block the boot. I would like to see the boot
logs. I considered this issue to be non-fatal and must be just ending up
disabling all SCMI communication. But the reported issue is boot failure
which sounds like another/different bug and I would like that to be fixed
first before we push the workaround for the reported issue so that it is
not ignored.
Has anyone analysed why the absence of CPU clock results in boot failure ?
Are you running the upstream kernel itself ?
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-05 10:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 12:49 [BUG] New arm scmi check in linux-next causing rk3568 not to boot due to firmware bug Nicolas Frattaroli
2022-05-04 13:21 ` Sudeep Holla
2022-05-04 17:51 ` Nicolas Frattaroli
2022-05-05 8:03 ` Cristian Marussi
2022-05-05 9:40 ` Etienne Carriere
2022-05-05 10:10 ` Sudeep Holla [this message]
2022-05-05 13:42 ` Nicolas Frattaroli
2022-05-05 10:47 ` Cristian Marussi
2022-05-05 14:21 ` Cristian Marussi
2022-05-12 11:11 ` Nicolas Frattaroli
2022-05-12 14:34 ` Sudeep Holla
2022-05-13 8:44 ` Kever Yang
2022-05-13 8:58 ` Etienne Carriere
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=20220505101032.icqb2hau4dhj3afr@bogus \
--to=sudeep.holla@arm.com \
--cc=cl@rock-chips.com \
--cc=cristian.marussi@arm.com \
--cc=etienne.carriere@linaro.org \
--cc=frattaroli.nicolas@gmail.com \
--cc=heiko@sntech.de \
--cc=jeffy.chen@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.com \
/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