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 8C934C43217 for ; Thu, 12 May 2022 14:35:55 +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:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=ZlglwxJVqapX9bi9GfzqExmebKN+6FvoOpAqq0hxTpY=; b=SFXuhCdXUxWugN XY28rgMZa1i2Q7mnU18XkOlvCwOSaFKo6JUsYllNgViiyLGcOLjlJ22wd/TcSSiqD/IpLVOVgz6b7 C5WQylsahlID3F40LAjyF+Qi37McoDKEdtQBrDgyqR6vEcK5Wd3jl+m2tb+9K97x1x0ZSjbpzHJmp zJ1F+QbkeAE7aFX0QjPYYgEiaVgJLZBRXm/mXSsLkSfHWp0UR2Y4zjG69n3kb1NURmwBt5Cko/SU9 dINUxxQTiFLSICgTg1HmN9M680ybJgnKH/mf5DFFJmwxf7HKAeK4sbmNcQt70arOp7Po0ty3jBX4d P3TJI7jeE5rIjmIIGoCA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1np9tv-00CQOQ-JJ; Thu, 12 May 2022 14:34:47 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1np9ts-00CQLn-12; Thu, 12 May 2022 14:34:45 +0000 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 AC4C9106F; Thu, 12 May 2022 07:34:34 -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 36B4B3F73D; Thu, 12 May 2022 07:34:33 -0700 (PDT) Date: Thu, 12 May 2022 15:34:30 +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: References: <1698297.NAKyZzlH2u@archbook> <6587375.6lpfYT6tjA@archbook> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <6587375.6lpfYT6tjA@archbook> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220512_073444_150418_B0883170 X-CRM114-Status: GOOD ( 20.63 ) 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 On Thu, May 12, 2022 at 01:11:22PM +0200, Nicolas Frattaroli wrote: > Hello, > > sorry for the late reply, completely missed that there was a question > for me in this mail. > > On Donnerstag, 5. Mai 2022 11:40:09 CEST Etienne Carriere wrote: > > Hello Nicolas, Cristian, > > [...] > > > > Indeed the firmware implementation is wrong in TF-A. > > And also in OP-TEE by the way: > > https://github.com/OP-TEE/optee_os/blob/3.17.0/core/drivers/scmi-msg/base.c#L163-L166 > > > > @Nicoals, do you want to send a patch to TF-A, or do you want me to do it? > > I have no experience with TF-A, so I'd prefer if you could do it. > > In good news, Rockchip has confirmed they're preparing to release RK356x > TF-A sources, so I'll be able to port the patch over to their sources once > they are released, if they don't already apply it themselves. > So, there is no way to get a blob release with the patch applied ? We know it is a bug in TF-A and if Rockchip is using that codebase, it will be the same bug there too causing this issue. Waiting until the code is released and the proper TF-A port is done may not be acceptable for many developers. So someone from the rockchip doing these tf-a blob release must get involved here, understand the situation and get the fixed. We can workaround, but I want to hear that it will be fixed instead of getting ignored until proper port is available. Etienne, are you not the author for the related TF-A code ? How can we get that fixed in the TF-A code base. If you are not, then I will try to get my repo login credentials sorted so that I can only push TF-A change. -- Regards, Sudeep _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel