From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id AAD3DC433FE for ; Wed, 4 May 2022 12:50:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-ID:Date:Subject:Cc :To:From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=dF1BENj3oP9MZ+ROsRFzYb/9V0L9Jxl1uev9Pk/LOeA=; b=1owqeB2MXEH31R UB4POSPOlwPVNStAUtPpe8Rdc1uguW07j209OppAoJIYnPHEYBxd1FOEZcOtsZ9aSPqwpAjOCzKyH BErZBFBZuyFrJODXvx5LfAQbA3jKUt/pkND0TxBBJf5HDn1Pe3SuG2MxFqd1SrKr9tkODOyWdw34s Ue5SRsCeFu2Q4OTyXWNfRj0vBjz9/gHQh8kHVLJRRUqpDTZkSJNEIkHQuYM2HXsH5EN8sJUL0GmMh RHF2+oDYDEML6piG4dTILQP0/7qXIn5HmfCeNL4HNZNhr9a22TGVaZlBTN90173QhQYdo1hVQOSMx paCjEnwMZ7iFEeBuTPRA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nmERT-00Aqqh-0y; Wed, 04 May 2022 12:49:19 +0000 Received: from mail-ej1-x632.google.com ([2a00:1450:4864:20::632]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nmERP-00Aqn5-JQ; Wed, 04 May 2022 12:49:17 +0000 Received: by mail-ej1-x632.google.com with SMTP id bv19so2671480ejb.6; Wed, 04 May 2022 05:49:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=bZOr4HtGpaWrCWq6twhnfSIMm+TDbavFaWLE4oY5Z9c=; b=nDXrvhpETmVWGr629uSMqiX19ijYfRXKXMhGz8o5tIvCP8S9zxByN1mXXSY4xpoyTF jIY9vEofi63VivguJwzrnZNRqBW7uDuHVGNtAWDnzg4vNj4H2/zyrb0QptxtKV8gLC1F dv0FOA9BnfulRLlZab66QXb6HOMz27lWvJIcOv3yF31liu7NCeh+j9BrInw3No6No0Uz d9qp5fioReOska3ktJXacTPQ6LTbdnbYSe4vg2Fe96CAXuIjRPmUXLKUB9znlaVBAAot UW6WNL/GzCT1Ezrs0i+ltz9xZUWqgynEtu3Y55k7MXOS1CqpSn6V6FWrEpjaVq8skmIW 9LlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=bZOr4HtGpaWrCWq6twhnfSIMm+TDbavFaWLE4oY5Z9c=; b=ShTvdepLo8NiAMClg8DkkfeQx/dH+/UrDgck4tUpM2R7qDTvBfx6Gn3mbUU4x1I0ID zXMlUzqolq71IN351xE30cNKnOtdsVs3WwVhWWTVLnjMJu677z5/FqFUWPGAwkwZ/p+u BZQbjPvPgZs5jK3g5jwh1+Kk0bQ+P5507DcAkQtPUPDT4kk2cD7PxhXfHNWrJxhv9Yzw thavtgtcLqjsjpV9AG/9OWI7ZJKdFMKKE6S79YSpERutttOFh7q9aQw3PRb6LCD94lJb SqkQy3BVCNjqfLln4HS1zcTTvvzUIsDTu/7kQok/5pmM6c+pqaQ253kIJ2Y3rOXJywAK /+TA== X-Gm-Message-State: AOAM53234Lj4osNB76wI6faQKCjRVxNo0NZFA5eccTgf+dWwALmP1/kW RxMwHAsar9RCH3Dz9grhyZKlpmHID4Ta9w== X-Google-Smtp-Source: ABdhPJx71yCTi6az8xLbfEKhVrgKgdLuPPk5NgAYoOUVtjv92KGGf6NaeuVDVDWbkMzcbOmU89I5iQ== X-Received: by 2002:a17:907:2d24:b0:6f4:3152:3d1a with SMTP id gs36-20020a1709072d2400b006f431523d1amr15972250ejc.324.1651668549151; Wed, 04 May 2022 05:49:09 -0700 (PDT) Received: from archbook.localnet (84-72-105-84.dclient.hispeed.ch. [84.72.105.84]) by smtp.gmail.com with ESMTPSA id qr48-20020a1709068cb000b006f3ef214e0bsm5768686ejc.113.2022.05.04.05.49.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 04 May 2022 05:49:08 -0700 (PDT) From: Nicolas Frattaroli To: linux-arm-kernel@lists.infradead.org Cc: linux-rockchip@lists.infradead.org, Heiko Stuebner , Liang Chen , Sudeep Holla , linux-kernel@vger.kernel.org, Kever Yang 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 Message-ID: <1698297.NAKyZzlH2u@archbook> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220504_054915_667791_F51B3FEE X-CRM114-Status: GOOD ( 13.13 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org 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