Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp685716iog; Thu, 30 Jun 2022 08:18:46 -0700 (PDT) X-Google-Smtp-Source: AGRyM1v7OhOMXzpG5VAAMckbU7IuUlzLeRdQuJm5qtlGfdZmmchXjAVl+gPJZ5mnxDqQkix68zsy X-Received: by 2002:a63:b00e:0:b0:40c:c685:d45 with SMTP id h14-20020a63b00e000000b0040cc6850d45mr8107154pgf.494.1656602325840; Thu, 30 Jun 2022 08:18:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656602325; cv=none; d=google.com; s=arc-20160816; b=YxIp8+tUf7RmlTTr7zk4qcA2mIK0VsGINDpQ1h7N8I8LbjbNf1EYODxbJiAVITQa+a +fwMtHkX2QwObB2bRRhDktvshRt4P1TGu0IwQm+tusY1e8/8CIO80CwdK96tMId/Lks6 V/zrOSnn3RvDbUbUEc95SaK0xJNetRLaZezuVowY2q5PKNvWS0zaTRoqwbJTtLRvCS2j 1e4hCpVFfmkQRkkz/YDhDoEgKefWSkYd4Rfmu0Cl5d2XT0nK1xXwfRerp+EZyf+69v8A LS1FfOoZIYHNnqe9mFoFlJixAxNbOkMNkt7BhpoF6nor8a14x+8vhLvnkHCeWzWgi8h5 Ym6A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=QQUZdryIvAGUEfbuSZ9RcgUBinauPA6CKY/nGGnI/Tc=; b=aVQwsuJOuLRB0cOrhIUULcfRpNFVcQdd6x5exrWGFOXnZZTTcNoH7ZWFO0FwGM9Cgz 3dHhGBV7oqmAeH5ohQ8cTDVvw4dq4jfE6rEVUbDeRZLhEe3EYaprLrW8mA2KenIuyh8X wHRHF+9uMBfbulM/7P3hpkZRi8TtqsK0SVKl7sPMeAqMdUb3goR1xJ7x7dclHCvqYrsP GZs9VRyIh0PZX4RSbAKU84AJxdCnvuS36yawZ4AafaMVokee5sKvtw05uWUa2etyH67j mSQAEqF+ECJ9nmxmhv5UdIF+JwXxgY0xZASu+pUBzcf8eWTCKI3wF6pIFNIH34JzOHkr 01AA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=OmSMy9DL; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d16-20020a63f250000000b003daf6356570si26093214pgk.3.2022.06.30.08.18.34; Thu, 30 Jun 2022 08:18:45 -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=OmSMy9DL; 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 S232479AbiF3PDB (ORCPT + 99 others); Thu, 30 Jun 2022 11:03:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39846 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235328AbiF3PC5 (ORCPT ); Thu, 30 Jun 2022 11:02:57 -0400 Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D386021E29 for ; Thu, 30 Jun 2022 08:02:55 -0700 (PDT) Received: by mail-lj1-x234.google.com with SMTP id o23so23454028ljg.13 for ; Thu, 30 Jun 2022 08:02:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QQUZdryIvAGUEfbuSZ9RcgUBinauPA6CKY/nGGnI/Tc=; b=OmSMy9DLYsZsfeGNqiOj5eUckzrgJF30/OyZbA1hLicM+qU7p41yr52k6Cw8V2f3W0 oADmaa7TM7Z4rDS8rxo8R5jo4BS/zJy63r0lOdjmA1iDTKBTPwf9Dk0FLwlku+O8aTtL xdPPQm59KITc4ru8+CbDuqOqySuM4uoXkdIbM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QQUZdryIvAGUEfbuSZ9RcgUBinauPA6CKY/nGGnI/Tc=; b=sV2nSYNdd05pInX40iHmST1E7VD/DUd7PZXQjRHIbt43TOz3PLi8NR16EHGyOCFK7K Wp/VeB2FSeDSsl8VlgdKcGTPhlg4KseAdnJmcACqWgfgx5UIAmTpL8o6MbSGGBqPl/2K tyTGH1bV7FE5zTEIrOZ7fHdtT/gbOFXQ0MBaPLA/Rr0OexMe4DrOLdF8bu3oIcYV/kL9 KZpGCl4KcvVnr507j5MIgtO3AnUuHqgeLS+ruUGegLzSIV8T2fkgYJnhaeORz/JQxDRc dqJ4r/VWcrsXjA7MBdv3nvx3SzNunM9bRRGJERJVF1xY8bXeHj16dY5wazkTWdTlKnUf Q1tw== X-Gm-Message-State: AJIora+cM/6cBhKX9pAHI7JuOfl9om8XZn3gCRSzwoqDMgmGRjoEChVi g3N/43l0cJbO+VkI+7BWEKCDqsMtwL1TJzyIofU= X-Received: by 2002:a17:907:75c8:b0:72a:4b50:b029 with SMTP id jl8-20020a17090775c800b0072a4b50b029mr6545547ejc.394.1656601362966; Thu, 30 Jun 2022 08:02:42 -0700 (PDT) Received: from mail-wr1-f49.google.com (mail-wr1-f49.google.com. [209.85.221.49]) by smtp.gmail.com with ESMTPSA id bd25-20020a056402207900b004357738e04esm13135411edb.21.2022.06.30.08.02.42 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 30 Jun 2022 08:02:42 -0700 (PDT) Received: by mail-wr1-f49.google.com with SMTP id o4so23801010wrh.3 for ; Thu, 30 Jun 2022 08:02:42 -0700 (PDT) X-Received: by 2002:a5d:4046:0:b0:21a:3a12:239e with SMTP id w6-20020a5d4046000000b0021a3a12239emr9029135wrp.138.1656601361824; Thu, 30 Jun 2022 08:02:41 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Doug Anderson Date: Thu, 30 Jun 2022 08:02:29 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] FROMLIST: arm64: dts: qcom: Add LTE SKUs for sc7280-villager family To: Jimmy Chen Cc: LKML , Stephen Boyd , Jimmy Chen , Andy Gross , Bjorn Andersson , Krzysztof Kozlowski , Rob Herring , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , linux-arm-msm Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.5 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: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Wed, Jun 29, 2022 at 11:27 PM Jimmy Chen wrote: > > From: Jimmy Chen > > This adds LTE skus for villager device tree files. > > Signed-off-by: Jimmy Chen > Signed-off-by: Jimmy Chen Pick one email address and use it. Having two Signed-off-by from the same person with different email addresses is odd. > arch/arm64/boot/dts/qcom/Makefile | 3 +++ > .../arm64/boot/dts/qcom/sc7280-chrome-common.dtsi | 7 ------- > arch/arm64/boot/dts/qcom/sc7280-herobrine-crd.dts | 1 + > .../qcom/sc7280-herobrine-herobrine-r1-lte.dts | 14 ++++++++++++++ > .../boot/dts/qcom/sc7280-herobrine-lte-sku.dtsi | 15 +++++++++++++++ > .../dts/qcom/sc7280-herobrine-villager-r0-lte.dts | 14 ++++++++++++++ > .../dts/qcom/sc7280-herobrine-villager-r1-lte.dts | 14 ++++++++++++++ > arch/arm64/boot/dts/qcom/sc7280-idp.dtsi | 1 + > 8 files changed, 62 insertions(+), 7 deletions(-) > create mode 100644 arch/arm64/boot/dts/qcom/sc7280-herobrine-herobrine-r1-lte.dts > create mode 100644 arch/arm64/boot/dts/qcom/sc7280-herobrine-lte-sku.dtsi > create mode 100644 arch/arm64/boot/dts/qcom/sc7280-herobrine-villager-r0-lte.dts > create mode 100644 arch/arm64/boot/dts/qcom/sc7280-herobrine-villager-r1-lte.dts NOTE: ${SUBJECT} for this patch has "FROMLIST". Please remove that. That's a prefix that's added when patches are picked from an upstream mailing list into a downstream Chrome OS tree. Also note that we've started updating the "bindings" file for boards. Please update "Documentation/devicetree/bindings/arm/qcom.yaml" as part of your series. Ideally that will make it a two-part series. Patch #1 updates the bindings and patch #2 does the device tree changes. > diff --git a/arch/arm64/boot/dts/qcom/Makefile b/arch/arm64/boot/dts/qcom/Makefile > index 2f8aec2cc6db6..ab1066883c468 100644 > --- a/arch/arm64/boot/dts/qcom/Makefile > +++ b/arch/arm64/boot/dts/qcom/Makefile > @@ -85,7 +85,10 @@ dtb-$(CONFIG_ARCH_QCOM) += sc7180-trogdor-r1.dtb > dtb-$(CONFIG_ARCH_QCOM) += sc7180-trogdor-r1-lte.dtb > dtb-$(CONFIG_ARCH_QCOM) += sc7280-herobrine-crd.dtb > dtb-$(CONFIG_ARCH_QCOM) += sc7280-herobrine-herobrine-r1.dtb > +dtb-$(CONFIG_ARCH_QCOM) += sc7280-herobrine-herobrine-r1-lte.dtb > dtb-$(CONFIG_ARCH_QCOM) += sc7280-herobrine-villager-r0.dtb > +dtb-$(CONFIG_ARCH_QCOM) += sc7280-herobrine-villager-r0-lte.dtb > +dtb-$(CONFIG_ARCH_QCOM) += sc7280-herobrine-villager-r1-lte.dtb > dtb-$(CONFIG_ARCH_QCOM) += sc7280-idp.dtb > dtb-$(CONFIG_ARCH_QCOM) += sc7280-idp2.dtb > dtb-$(CONFIG_ARCH_QCOM) += sc7280-crd-r3.dtb > diff --git a/arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi b/arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi > index 9f4a9c263c351..b1f83ddb4e23a 100644 > --- a/arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi > +++ b/arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi > @@ -83,13 +83,6 @@ spi_flash: flash@0 { > }; > }; > > -/* Modem setup is different on Chrome setups than typical Qualcomm setup */ > -&remoteproc_mpss { > - status = "okay"; > - compatible = "qcom,sc7280-mss-pil"; > - iommus = <&apps_smmu 0x124 0x0>, <&apps_smmu 0x488 0x7>; > - memory-region = <&mba_mem>, <&mpss_mem>; > -}; Please rebase your patch the Qualcomm tree, AKA the "for-next" branch of git://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git ...when I applied your patch I got a merge conflict here because upstream has commit 2a77ada5168a ("arm64: dts: qcom: sc7280: Enable wifi for Chrome OS boards") and commit 1c20d3dbaa67 ("arm64: dts: qcom: sc7280: Set modem FW path for Chrome OS boards") > /* Increase the size from 2.5MB to 8MB */ > &rmtfs_mem { > diff --git a/arch/arm64/boot/dts/qcom/sc7280-herobrine-crd.dts b/arch/arm64/boot/dts/qcom/sc7280-herobrine-crd.dts > index a4ac33c4fd59a..7aaba5e51af01 100644 > --- a/arch/arm64/boot/dts/qcom/sc7280-herobrine-crd.dts > +++ b/arch/arm64/boot/dts/qcom/sc7280-herobrine-crd.dts > @@ -8,6 +8,7 @@ > /dts-v1/; > > #include "sc7280-herobrine.dtsi" > +#include "sc7280-herobrine-lte-sku.dtsi" > > / { > model = "Qualcomm Technologies, Inc. sc7280 CRD platform (rev5+)"; > diff --git a/arch/arm64/boot/dts/qcom/sc7280-herobrine-herobrine-r1-lte.dts b/arch/arm64/boot/dts/qcom/sc7280-herobrine-herobrine-r1-lte.dts > new file mode 100644 > index 0000000000000..e37773fd63b3b > --- /dev/null > +++ b/arch/arm64/boot/dts/qcom/sc7280-herobrine-herobrine-r1-lte.dts Thinking about this more, I think we _shouldn't_ do this for herobrine-r1 right now. No herobrine-r1 boards were actually strapped to tell LTE vs. non-LTE and people just shoved LTE vs. non-LTE qcards on randomly. There is still some plan to have the bootloader identify LTE vs. WiFi qcards and use a different SKU ID bit, so maybe we'll solve this eventually. ...but for now leave herobrine alone. Personally for now I'd suggest adding #include "sc7280-herobrine-lte-sku.dtsi" to the existing "sc7280-herobrine-herobrine-r1.dts" file. > @@ -0,0 +1,14 @@ > +// SPDX-License-Identifier: (GPL-2.0+ OR MIT) > +/* > + * Google Herobrine board device tree source > + * > + * Copyright 2022 Google LLC. > + */ > + > +#include "sc7280-herobrine-villager-r0.dts" > +#include "sc7280-herobrine-lte-sku.dtsi" > + > +/{ > + model = "Google Herobrine (rev1+) with LTE"; > + compatible = "google,herobrine-sku0", "qcom,sc7280"; > +}; > diff --git a/arch/arm64/boot/dts/qcom/sc7280-herobrine-lte-sku.dtsi b/arch/arm64/boot/dts/qcom/sc7280-herobrine-lte-sku.dtsi > new file mode 100644 > index 0000000000000..c628910b310d3 > --- /dev/null > +++ b/arch/arm64/boot/dts/qcom/sc7280-herobrine-lte-sku.dtsi > @@ -0,0 +1,15 @@ > +// SPDX-License-Identifier: (GPL-2.0+ OR MIT) > + /* > + * Google Herobrine dts fragment for LTE SKUs > + * > + * Copyright 2022 Google LLC. > + */ Why is the copyright header comment indented by two spaces? Please fix. ...also please add a blank line here after the header.