Received: by 2002:ac0:da4c:0:0:0:0:0 with SMTP id a12csp853050imi; Fri, 22 Jul 2022 10:55:15 -0700 (PDT) X-Google-Smtp-Source: AGRyM1u+NjauXzziRBV8LV5cTONxt+gIAa3WRZFw0XnorYc5u7Qqsn40JHiO5BJ2ko4qcNgmmerr X-Received: by 2002:a05:6a00:1a92:b0:52b:ac3:7964 with SMTP id e18-20020a056a001a9200b0052b0ac37964mr1066116pfv.31.1658512515407; Fri, 22 Jul 2022 10:55:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658512515; cv=none; d=google.com; s=arc-20160816; b=N6IDbXNiL4Qb/212FyZdUfIOb9VXYtYH4cYTuE6IpiFiduI2u0ONDCRHX85ASkFbFS EgClQKJdZVT9oFo35eZAoVCRXLoEtnnlWjOJ91erCQV66BjJS8o9rsthmxNNi3j55wnc dgTWl2717fXx+AhB64jfuE4akK0QAT4CfukennIIXJTnx/iUCrl1wMNosQCnWEP062EF LuTvKWQFTdBuG7vfQzZSO57fAkat4yYN3SE5nH4wzIYiBaDpyEQ0WZozkWsB02jYnBnW bIdbtnkFiB12khhFNgpnOXTIJmmmE4NMxp+sItKWhFjRCD++WlQM2sfLOAdJhKlQ/TaE uC/w== 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=Ue0tc0adu1W83NSgyETf8DUiCKAIIriUdz0pGaeFGiM=; b=z9k8wyz1TBi91uoA2aEFBzS05M6i1VInev2dshxwExvQe7y3gH4DSh2rJ7nWwZ5gmC J/R0G/vaTAnUGU3PO20Z3AqTvX+YYos3S56aF4dKNTmsg0KSDpFaOKXG33VRhbDUnQRD Q2Ece7P4YOKiFG26dI8ap9MznOSH52HkN2bYqXhuNoiAAPEPMUlIXD0Nuk22WnJio83q d8QHl1Dt++KL3KLfUD7WhqpO5nsvApiKEZrjRS0MOfaG76ggu9vlTI1mnGQH5Sd5JarB pqtjOMYSH5Z+xHm3fAG5ihNWYECKdKdY+pM7aRT1a6z+Uxf+RtYoXIa6sIFvM2i4j2Ev G15A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=h7n2Ohg6; 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 t69-20020a638148000000b00412b10397b4si5410465pgd.664.2022.07.22.10.54.59; Fri, 22 Jul 2022 10:55:15 -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=h7n2Ohg6; 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 S235178AbiGVRyU (ORCPT + 99 others); Fri, 22 Jul 2022 13:54:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46050 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232383AbiGVRyT (ORCPT ); Fri, 22 Jul 2022 13:54:19 -0400 Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8128AE4 for ; Fri, 22 Jul 2022 10:54:18 -0700 (PDT) Received: by mail-io1-xd36.google.com with SMTP id r70so4174662iod.10 for ; Fri, 22 Jul 2022 10:54:18 -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=Ue0tc0adu1W83NSgyETf8DUiCKAIIriUdz0pGaeFGiM=; b=h7n2Ohg6jboD5Oevy+0g87C911HBazqSA8cA404DtpQJKvNaWodxAOKcF5pr4LZRwC HV1Qu5FqHBz4aiUjc+OzYlURLq6KwN0tLVuixL9qccP9jz46c3uJVI2z0DqcmWIFBuYN RA2dnwvZMKZe+2dWiMZVvidUgX9zZuPTVKoyE= 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=Ue0tc0adu1W83NSgyETf8DUiCKAIIriUdz0pGaeFGiM=; b=2YSgcwsHm8+Wja2O14BftkKuSvhTMY+xtHRzVh55nFhQU5IFt9385YWUJMbeWSeTim 842crBb1V/F51+iuxpnZSSp8kddO+CbrssqpUWcdWyFr5+yW57O/WjhLxfFTYs1M1dHc cwSEOTidF21jJmRdT4aG1Pt93Ax3gbAberJqC+pog8tJYalIjwl0p/STLeNS0+YJnh3h lLyhJgLLuBt84QiFKtymVuruT5Pd2tQYeKn72gvk6oLWzJpKspE9jOa2gQiOW0Xy9oU5 +uJUX5Mb95W2qDxIj3w7kHhnW+OgGkqUkWQUD+UxCPft4htckc05hYx7YsGI3BVZLt05 KJ/Q== X-Gm-Message-State: AJIora+zItcWiAw6huoYL8CWHdR09hNoL0ADspW+wZTt4PBWKUZnnc77 izkpn8P3G6Lcr+D457lPYknZ/C1caYQ7Na5Q X-Received: by 2002:a6b:3fd6:0:b0:67b:d97f:47d3 with SMTP id m205-20020a6b3fd6000000b0067bd97f47d3mr334147ioa.46.1658512457584; Fri, 22 Jul 2022 10:54:17 -0700 (PDT) Received: from mail-io1-f51.google.com (mail-io1-f51.google.com. [209.85.166.51]) by smtp.gmail.com with ESMTPSA id 2-20020a020a02000000b0033ea1d9858bsm2236712jaw.36.2022.07.22.10.54.15 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 22 Jul 2022 10:54:15 -0700 (PDT) Received: by mail-io1-f51.google.com with SMTP id 125so4178646iou.6 for ; Fri, 22 Jul 2022 10:54:15 -0700 (PDT) X-Received: by 2002:a05:6638:388e:b0:33c:b603:516 with SMTP id b14-20020a056638388e00b0033cb6030516mr534277jav.133.1658512454563; Fri, 22 Jul 2022 10:54:14 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Doug Anderson Date: Fri, 22 Jul 2022 10:54:01 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v7 0/3] Add new board revision and LTE SKUs for sc7280-villager family To: Jimmy Chen Cc: LKML , Andy Gross , Bjorn Andersson , Alan Huang , Rob Herring , Konrad Dybcio , Krzysztof Kozlowski , "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.8 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 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 Fri, Jul 22, 2022 at 1:11 AM Jimmy Chen wrote: > > These patches add a new board revision for device Villager, and add > new LTE sku for both board revisions. > > yaml issue has been clarified in [1] and [2], and 'status' has been > reordeded last since v4. > > [1] https://lore.kernel.org/all/CAD=FV=WtKRFQr5jSQvsr08x9dgHrvenUWWtX_SKuCLuSvSH7WQ@mail.gmail.com/ > [2] https://lore.kernel.org/all/d3d4d90b-85b5-5ad9-78e6-5a074c21af4f@linaro.org/ > > Changes in v7: > -Revise typo in Makefile in ptch 2/3 > > Changes in v6: > -remove v5 accidentally added sc7280-herobrine-herobrine-r1-lte.dts in patch3/3 > > Changes in v5: > -Update subject and revise Makefile > > Changes in v4: > - Add patch 1/3 and update patch 3/3 > > Changes in v3: > - Update patch format > > Changes in v2: > - Add patch 1/2 > > Jimmy Chen (3): > dt-bindings: arm: qcom: document sc7280 and villager board > arm64: dts: qcom: sc7280: Add herobrine-villager-r1 > arm64: dts: qcom: Add LTE SKUs for sc7280-villager family > > Documentation/devicetree/bindings/arm/qcom.yaml | 15 +++++++++++++++ > arch/arm64/boot/dts/qcom/Makefile | 3 +++ > .../boot/dts/qcom/sc7280-chrome-common.dtsi | 11 ----------- > .../boot/dts/qcom/sc7280-herobrine-crd.dts | 1 + > .../dts/qcom/sc7280-herobrine-herobrine-r1.dts | 1 + > .../boot/dts/qcom/sc7280-herobrine-lte-sku.dtsi | 17 +++++++++++++++++ > .../qcom/sc7280-herobrine-villager-r0-lte.dts | 14 ++++++++++++++ > .../dts/qcom/sc7280-herobrine-villager-r0.dts | 4 ++-- > .../qcom/sc7280-herobrine-villager-r1-lte.dts | 14 ++++++++++++++ > .../dts/qcom/sc7280-herobrine-villager-r1.dts | 14 ++++++++++++++ > arch/arm64/boot/dts/qcom/sc7280-idp.dts | 1 + > 11 files changed, 82 insertions(+), 13 deletions(-) > 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 > create mode 100644 arch/arm64/boot/dts/qcom/sc7280-herobrine-villager-r1.dts We're at a point now where this won't be able to land for at least 2.5 weeks. Given other changes happening (especially the audio changes), I suspect all the in-flight stuff will get confusing. As an experiment, I created a staging tree atop the current arm64 dts tree and put this there. I'll try to put only things that I believe are truly ready to land there, but git hashes won't be stable since it's just a staging tree: https://github.com/dianders/kernel-staging/commits/qcom/arm64-staging -Doug