From: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-rockchip@lists.infradead.org,
Heiko Stuebner <heiko@sntech.de>, Liang Chen <cl@rock-chips.com>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-kernel@vger.kernel.org,
Kever Yang <kever.yang@rock-chips.com>
Subject: [BUG] New arm scmi check in linux-next causing rk3568 not to boot due to firmware bug
Date: Wed, 04 May 2022 14:49:07 +0200 [thread overview]
Message-ID: <1698297.NAKyZzlH2u@archbook> (raw)
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:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/firmware/arm_scmi/base.c?h=next-20220503&id=3b0041f6e10e5bdbb646d98172be43e88734ed62
The error message in the log is as follows:
arm-scmi firmware:scmi: Malformed reply - real_sz:8 calc_sz:4, t->rx.len is 12, sizeof(u32) is 4, loop_num_ret is 3
The rockchip firmware (bl31) being used was v1.32, from here:
https://github.com/JeffyCN/rockchip_mirrors/blob/rkbin/bin/rk35/rk3568_bl31_v1.32.elf
This seems like a non-fatal firmware bug, for which a kernel workaround is
certainly possible, but it would be good if rockchip could fix this in their
firmware.
The user going by "amazingfate" reported that commenting out the
ret = -EPROTO; break;
fixes the issue for them.
I'm writing here to get the discussion started on how we can resolve this
before the Linux 5.19 release.
Sudeep Holla has already told me they'll gladly add a workaround before
the 5.19 release, but would rather see this fixed in the vendor firmware
first. Would rockchip be able and willing to fix it and publish a new
bl31 for rk3568?
Regards,
Nicolas Frattaroli
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-05-04 12:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 12:49 Nicolas Frattaroli [this message]
2022-05-04 13:21 ` [BUG] New arm scmi check in linux-next causing rk3568 not to boot due to firmware bug 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
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=1698297.NAKyZzlH2u@archbook \
--to=frattaroli.nicolas@gmail.com \
--cc=cl@rock-chips.com \
--cc=heiko@sntech.de \
--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=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).