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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id CA923C433F5 for ; Thu, 5 May 2022 10:10:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229514AbiEEKOU (ORCPT ); Thu, 5 May 2022 06:14:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52256 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1354904AbiEEKOQ (ORCPT ); Thu, 5 May 2022 06:14:16 -0400 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id EECC24A3EE for ; Thu, 5 May 2022 03:10:36 -0700 (PDT) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id B8FDF106F; Thu, 5 May 2022 03:10:36 -0700 (PDT) Received: from bogus (e103737-lin.cambridge.arm.com [10.1.197.49]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 3F5F73FA27; Thu, 5 May 2022 03:10:35 -0700 (PDT) Date: Thu, 5 May 2022 11:10:32 +0100 From: Sudeep Holla To: Nicolas Frattaroli Cc: Cristian Marussi , Etienne Carriere , linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, Heiko Stuebner , Liang Chen , linux-kernel@vger.kernel.org, Kever Yang , Jeffy Chen , Peter Geis Subject: Re: [BUG] New arm scmi check in linux-next causing rk3568 not to boot due to firmware bug Message-ID: <20220505101032.icqb2hau4dhj3afr@bogus> References: <1698297.NAKyZzlH2u@archbook> <20220504132130.wmmmge6qjc675jw6@bogus> <3764923.NsmnsBrXv5@archbook> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > > > 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