Message ID | 20230511150539.3.I525a2ed4260046d43c885ee1275e91707743df1c@changeid |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:b0ea:0:b0:3b6:4342:cba0 with SMTP id b10csp4708570vqo; Thu, 11 May 2023 15:32:35 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4M9NiVGwwhIJKOdFSabl/Of6oCkgZdAFC8SAw7Ff5xHMuc3UZUb0+M9h4a9b1z3wnkNVSO X-Received: by 2002:a17:903:183:b0:1ac:7260:80a7 with SMTP id z3-20020a170903018300b001ac726080a7mr21526418plg.43.1683844354937; Thu, 11 May 2023 15:32:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683844354; cv=none; d=google.com; s=arc-20160816; b=sv4lLmFmDRaYtTJF2uT+PHlenwPjE/1rD8Ul+PLG5HEW3ebGhKOZ0Q4fZF+OBkqHXz 1TSa24bi5tTr7lWD6O/3bjDazmvgkvgcLgDWYvJ39gauYuJ8Kj9tl7sCaF/caEVMZZ9i Jp4Q6b6SBcs5C3czmkxTPJWXAuvmsM8SQ6L2lzTutOg21Et2UPBnW1bvDK2hCK6/Jixl Qz6avVT9fGZqzhPv51glIL5+QOM9SO5VQiBRDblNWnQnxg1N3B4AvfG6C0PPl7iQ5p2W Mif4u4Vr2Z2lxcptn55mQCPzmxMddXTnHmO1SU2Jad/WhtbcckPOnfAtr8oZcMkxBhXg 6YIg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=jGmB8F2e98GdWrgyT4B5IleiARSuWWe2Ulwy2r0MhKE=; b=0Hh4Wgxda3Lr4amVBBmjeXjkXzBvCUe8zk8kC4zWSX/JWn6wCJwb/X7UQKZVagycPP E10kMpcfAdVTah5UdGs/1G99mMr9iNGObroCoNBG+xgo1Q32aIYcbXpnFZPx8lJrcrUz OwVTkgiQG1UirDs0Zh+vwdpHn87Wp7DIKIYLMzJA5Ul/m3XhoER62LsR3cGvBNo2puj8 7Ow3xeC45qcLkA7qGOXnd7W2M1bRoq357z1p0WzgmlrEXO7XR2vWUtF72v3Yf2QiqSXz OQGrGLIoawmH4k2CYsntxu8gYy4nbOKOLPJx2NnFqEkLIoMGa0dCJWIq+mpgZh4Lg+Km dWIw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=a8ROuWQy; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id 3-20020a170902c10300b001ab1b0c5b21si7292901pli.5.2023.05.11.15.32.19; Thu, 11 May 2023 15:32:34 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=a8ROuWQy; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239433AbjEKWHf (ORCPT <rfc822;peekingduck44@gmail.com> + 99 others); Thu, 11 May 2023 18:07:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56694 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238953AbjEKWH2 (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Thu, 11 May 2023 18:07:28 -0400 Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A5C786E94 for <linux-kernel@vger.kernel.org>; Thu, 11 May 2023 15:07:24 -0700 (PDT) Received: by mail-pj1-x102c.google.com with SMTP id 98e67ed59e1d1-2502346bea0so5722932a91.2 for <linux-kernel@vger.kernel.org>; Thu, 11 May 2023 15:07:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1683842844; x=1686434844; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=jGmB8F2e98GdWrgyT4B5IleiARSuWWe2Ulwy2r0MhKE=; b=a8ROuWQy9au/LGDatW3Yczkvz1oDRSIPWobGizLtzk0TsyfsXDteYsoxk4LFs2lq9I zmg18AmauzAwY5tL3x5orosIDGNmfVPcTnQE8EGCRj40rRYHapv4Zj4uHo4PiAkpJjE9 p+5iV3Raay93vAOnpWhbkitqUW6+lsDByEF10= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683842844; x=1686434844; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=jGmB8F2e98GdWrgyT4B5IleiARSuWWe2Ulwy2r0MhKE=; b=S8U8P4z8MZ4GEJOSCSRPhT0Dnc5J9tBjoIUX8SM5JRIZzX8BX0lrSHC7ZKHxrsSzBz ygzTQeQE5SyA8gMwBL2uaac4nGtUffAJk/7KLsFxZ9jgYpsxPSumJN9ZhOrTMpEHUwVa DDpe2evNGUOamxFR95a8gowckqlS0i+N2mK6AC7YhK/cDayAEjvk3GLdVwCUGDjqfbah dq45zmbD8xwRaegfj1ptRUAk5F5+UizTtZ8B8yCeMFsU9hpVByy50wAcvpqY6Kbfb4mu iYAOZGe5/yk7BzCMMal4wJBw638j5u2zKVeOWmTjras7TCIQQX1VSIFh5/tRXtQSnpLB w6oA== X-Gm-Message-State: AC+VfDy+pNC5EJNpkwL7jXHUuhv+/52gEhMi8Izhj58Br5rzkKyMqBzS bsP7fUeFLmoSyRsZXk0/XSVsjA== X-Received: by 2002:a17:90a:2d6:b0:252:a2e5:4c3f with SMTP id d22-20020a17090a02d600b00252a2e54c3fmr1747848pjd.25.1683842844119; Thu, 11 May 2023 15:07:24 -0700 (PDT) Received: from tictac2.mtv.corp.google.com ([2620:15c:9d:2:b96a:d776:ee3:e572]) by smtp.gmail.com with ESMTPSA id h24-20020a17090a9c1800b00247735d1463sm17589457pjp.39.2023.05.11.15.07.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 11 May 2023 15:07:23 -0700 (PDT) From: Douglas Anderson <dianders@chromium.org> To: Marc Zyngier <maz@kernel.org>, Thomas Gleixner <tglx@linutronix.de>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Matthias Brugger <matthias.bgg@gmail.com> Cc: devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org, wenst@chromium.org, Eddie Huang <eddie.huang@mediatek.com>, Allen-KH Cheng <allen-kh.cheng@mediatek.com>, Ben Ho <Ben.Ho@mediatek.com>, Weiyi Lu <weiyi.lu@mediatek.com>, AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>, linux-arm-kernel@lists.infradead.org, Tinghan Shen <tinghan.shen@mediatek.com>, jwerner@chromium.org, Hsin-Hsiung Wang <hsin-hsiung.wang@mediatek.com>, yidilin@chromium.org, Seiya Wang <seiya.wang@mediatek.com>, Douglas Anderson <dianders@chromium.org>, Conor Dooley <conor+dt@kernel.org>, linux-kernel@vger.kernel.org Subject: [PATCH 3/6] arm64: dts: mediatek: mt8183: Add mediatek,gicr-save-quirk Date: Thu, 11 May 2023 15:05:37 -0700 Message-ID: <20230511150539.3.I525a2ed4260046d43c885ee1275e91707743df1c@changeid> X-Mailer: git-send-email 2.40.1.606.ga4b1b128d6-goog In-Reply-To: <20230511150539.6.Ia0b6ebbaa351e3cd67e201355b9ae67783c7d718@changeid> References: <20230511150539.6.Ia0b6ebbaa351e3cd67e201355b9ae67783c7d718@changeid> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1765638778097846720?= X-GMAIL-MSGID: =?utf-8?q?1765638778097846720?= |
Series |
irqchip/gic-v3: Disable pseudo NMIs on Mediatek Chromebooks w/ bad FW
|
|
Commit Message
Doug Anderson
May 11, 2023, 10:05 p.m. UTC
Firmware shipped on mt8183 Chromebooks is affected by the GICR
save/restore issue as described by the patch ("dt-bindings:
interrupt-controller: arm,gic-v3: Add quirk for Mediatek SoCs w/
broken FW"). Add the quirk property.
Fixes: e526c9bc11f8 ("arm64: dts: Add Mediatek SoC MT8183 and evaluation board dts and Makefile")
Signed-off-by: Douglas Anderson <dianders@chromium.org>
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 1 +
1 file changed, 1 insertion(+)
Comments
Reviewed-by: Julius Werner <jwerner@chromium.org>
On Thu, 11 May 2023 23:05:37 +0100, Douglas Anderson <dianders@chromium.org> wrote: > > Firmware shipped on mt8183 Chromebooks is affected by the GICR > save/restore issue as described by the patch ("dt-bindings: > interrupt-controller: arm,gic-v3: Add quirk for Mediatek SoCs w/ > broken FW"). Add the quirk property. > > Fixes: e526c9bc11f8 ("arm64: dts: Add Mediatek SoC MT8183 and evaluation board dts and Makefile") > Signed-off-by: Douglas Anderson <dianders@chromium.org> > --- > > arch/arm64/boot/dts/mediatek/mt8183.dtsi | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi > index 5169779d01df..39545172fce5 100644 > --- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi > +++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi > @@ -709,6 +709,7 @@ gic: interrupt-controller@c000000 { > <0 0x0c400000 0 0x2000>, /* GICC */ > <0 0x0c410000 0 0x1000>, /* GICH */ > <0 0x0c420000 0 0x2000>; /* GICV */ > + mediatek,gicr-save-quirk; Is that something you can safely generalise at the SoC level? Are these SoC solely used on Chromebooks, and/or without any hope of seeing any alternative FW being already in use? M.
Hi, On Fri, May 12, 2023 at 1:13 AM Marc Zyngier <maz@kernel.org> wrote: > > On Thu, 11 May 2023 23:05:37 +0100, > Douglas Anderson <dianders@chromium.org> wrote: > > > > Firmware shipped on mt8183 Chromebooks is affected by the GICR > > save/restore issue as described by the patch ("dt-bindings: > > interrupt-controller: arm,gic-v3: Add quirk for Mediatek SoCs w/ > > broken FW"). Add the quirk property. > > > > Fixes: e526c9bc11f8 ("arm64: dts: Add Mediatek SoC MT8183 and evaluation board dts and Makefile") > > Signed-off-by: Douglas Anderson <dianders@chromium.org> > > --- > > > > arch/arm64/boot/dts/mediatek/mt8183.dtsi | 1 + > > 1 file changed, 1 insertion(+) > > > > diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi > > index 5169779d01df..39545172fce5 100644 > > --- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi > > +++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi > > @@ -709,6 +709,7 @@ gic: interrupt-controller@c000000 { > > <0 0x0c400000 0 0x2000>, /* GICC */ > > <0 0x0c410000 0 0x1000>, /* GICH */ > > <0 0x0c420000 0 0x2000>; /* GICV */ > > + mediatek,gicr-save-quirk; > > Is that something you can safely generalise at the SoC level? Are > these SoC solely used on Chromebooks, and/or Hmmm, I thought I checked to make sure that the only users of these upstream were Chromebooks, but I just double-checked and I obviously was blind yesterday. You're right that I need to fix this. I will move these to: mt8195-cherry.dtsi mt8192-asurada.dtsi mt8183-kukui.dtsi ...it looks as if the common "baseboard" dtsi for mt8186 Chromebooks hasn't been upstreamed yet, so we'll have to keep an eye on that and make sure it gets the property. When I spin this series early next week I'll make that change. > without any hope of > seeing any alternative FW being already in use? I haven't seen anyone try to fully replace the firmware of a Chromebook in the past. It would be a lot of work, certainly. More common, I'd think, would be someone chaining an extra level of loader between the existing firmware and the OS. I _think_ I've seen people use a stripped down U-Boot for this. However, the "resident" firmware would still be the one that the Chromebook ships with. Certainly someone could prove me wrong and re-implement the firmware on one of these Chromebooks. That person would need to follow the same convention or accept that their kernel won't be enabling pseudoNMIs. -Doug
Il 12/05/23 00:05, Douglas Anderson ha scritto: > Firmware shipped on mt8183 Chromebooks is affected by the GICR > save/restore issue as described by the patch ("dt-bindings: > interrupt-controller: arm,gic-v3: Add quirk for Mediatek SoCs w/ > broken FW"). Add the quirk property. > > Fixes: e526c9bc11f8 ("arm64: dts: Add Mediatek SoC MT8183 and evaluation board dts and Makefile") > Signed-off-by: Douglas Anderson <dianders@chromium.org> > --- > > arch/arm64/boot/dts/mediatek/mt8183.dtsi | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi > index 5169779d01df..39545172fce5 100644 > --- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi > +++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi > @@ -709,6 +709,7 @@ gic: interrupt-controller@c000000 { > <0 0x0c400000 0 0x2000>, /* GICC */ > <0 0x0c410000 0 0x1000>, /* GICH */ > <0 0x0c420000 0 0x2000>; /* GICV */ > + mediatek,gicr-save-quirk; Nit: Can you please move this after interrupts? Thanks, Angelo > > interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH 0>; > ppi-partitions {
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi index 5169779d01df..39545172fce5 100644 --- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi +++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi @@ -709,6 +709,7 @@ gic: interrupt-controller@c000000 { <0 0x0c400000 0 0x2000>, /* GICC */ <0 0x0c410000 0 0x1000>, /* GICH */ <0 0x0c420000 0 0x2000>; /* GICV */ + mediatek,gicr-save-quirk; interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_HIGH 0>; ppi-partitions {