Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp2717277pxb; Thu, 3 Feb 2022 12:38:18 -0800 (PST) X-Google-Smtp-Source: ABdhPJxJ+r9WMxhrmJptGCfvFoVaVhmmBeXl2hzaNxgl6bij8GhDRnbzg7Eop0MStGTvPEM74n+0 X-Received: by 2002:a17:90b:1009:: with SMTP id gm9mr15481626pjb.223.1643920698002; Thu, 03 Feb 2022 12:38:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643920697; cv=none; d=google.com; s=arc-20160816; b=ZCzSPzghCQTvK8h6jlLE1R6LvstXaUBPLw3T2YlvkxytFjOvBvYZypuJxoplAcmi5v uYxSuKvTG2rMxlfUrvGIEY3xc/khj/on2RQTjp+MgOkSb9qFU4JQxVO+025muWs0zFMs CSvBcjlrRwTO5ah6QpaHxiYn1Ntc5iv2mNklrdbuGF+6yKNIWzzfDk1ghry0/CVboxLP dWCcULPwQ+kwv3u0o5NXj7dO5HeM25AFjwvENllJJvuX2NekjqM7utUmiFNR07r3diK+ Woqc6rRuYJERmtogxn0OOmEM5N0OJiDyYBZ4MT2yRZGEZL6QY9Y31QQgJc2rznvxPInC CZyA== 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=kGTOdXpCfpyaz8M+/fYDUe/NgCW7SBGMlvp2i1b84zI=; b=eEmGTzNPx4m0RyTZcrMzJny3lPL8tRtKgdWGAcAMYAiKnelQXf6JtYVDaPp+/mATMp wHthgnP8cRJlJd1elInj28AH7Cmg7zk2DCYtewTVDoUCGwMwcAJyoRfh71Rhv0cIXWAr QLZL080731YXurfi0Wh9WwEsEC1Rx9Rv2kyPLNuAIc6v8WtNL5aYxSElISqvbAEnFxu6 NO60Gq8QpyoZPEa3ZJqCRJ+22rReRnU/VWGbuKr4FJ4aQhxuM7rCR8Sko/fDRXLgTo6y zmAVdhVn8UQCG9RQu18LlNQUnFaEd7kLEZylrGIlhn4bAKj8xVrtN9wMa8DTEUmEt3cu hy6Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=Tpp8U7y5; 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 i4si19591499plb.489.2022.02.03.12.38.06; Thu, 03 Feb 2022 12:38:17 -0800 (PST) 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=Tpp8U7y5; 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 S230487AbiBBVc5 (ORCPT + 99 others); Wed, 2 Feb 2022 16:32:57 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55368 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1347618AbiBBVcu (ORCPT ); Wed, 2 Feb 2022 16:32:50 -0500 Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4F9BBC061744 for ; Wed, 2 Feb 2022 13:32:50 -0800 (PST) Received: by mail-io1-xd2f.google.com with SMTP id h7so781899iof.3 for ; Wed, 02 Feb 2022 13:32:50 -0800 (PST) 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=kGTOdXpCfpyaz8M+/fYDUe/NgCW7SBGMlvp2i1b84zI=; b=Tpp8U7y5JxXRpmOYMr1x6CrNjgnKiBuTzJX3FpA7ZFqWHBbpr7Xt2eJEQhhf152wL9 1rhMAUwEr0J17TUBUT6E420HKMR5YbJ8Yd3vhp89mjsl6gsM/o41Me9RR5nd1ZTqDpae N7zok0/JgckZdLtIXwwUYYwbpc/zRtHuxP7Wc= 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=kGTOdXpCfpyaz8M+/fYDUe/NgCW7SBGMlvp2i1b84zI=; b=tH20HbhdOhBEsWO6trhPiuXJxFSL4Hso8jpAjbQYa74k8sjcv44gtPrTZrm3FZ2e8c uBSaziVCYi17wanUbdtmNvf0YEga0ka2eUyfOchpIEXYIwzBId1j0hnB0qIv+TJ2qicg kDa/YhubWjH6APCLEOCj4RPBJlDho69ghot3TD0GRh8b49CIqZ8LRSE4V2h0h2t96SE7 vFH8zm48cGEOuPUHum0M6lRFxwSRaWImULf82Zgjf/Kdx+qvuEBczlBEVzzL3EYhUj41 2EbuYBreNomcCjB/gi2V0HTF+3jwDo2R8IkiWVUohk/E+rHkMzQaVdJGys2/OBUlxd50 30mg== X-Gm-Message-State: AOAM532KznBop5K1nGklpwaWU0nSgxMXK0OQqjQm4DGxevZnu1qY4bCj Fal7SHRO4/SsbHK0awMe7RxTfx+wmMNjRw== X-Received: by 2002:a6b:d812:: with SMTP id y18mr17553123iob.161.1643837569570; Wed, 02 Feb 2022 13:32:49 -0800 (PST) Received: from mail-il1-f172.google.com (mail-il1-f172.google.com. [209.85.166.172]) by smtp.gmail.com with ESMTPSA id a10sm2117548ilv.44.2022.02.02.13.32.48 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 02 Feb 2022 13:32:48 -0800 (PST) Received: by mail-il1-f172.google.com with SMTP id i1so502730ils.5 for ; Wed, 02 Feb 2022 13:32:48 -0800 (PST) X-Received: by 2002:a05:6e02:1bed:: with SMTP id y13mr2711266ilv.27.1643837568176; Wed, 02 Feb 2022 13:32:48 -0800 (PST) MIME-Version: 1.0 References: <20220125224422.544381-1-dianders@chromium.org> <20220125144316.v2.5.I5604b7af908e8bbe709ac037a6a8a6ba8a2bfa94@changeid> In-Reply-To: From: Doug Anderson Date: Wed, 2 Feb 2022 13:32:36 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 5/5] arm64: dts: qcom: sc7280: Add herobrine-r1 To: Bjorn Andersson Cc: Stephen Boyd , Viresh Kumar , Konrad Dybcio , kgodara@codeaurora.org, Matthias Kaehlcke , Sibi Sankar , Prasad Malisetty , quic_rjendra@quicinc.com, Andy Gross , Rob Herring , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , linux-arm-msm , LKML Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Mon, Jan 31, 2022 at 5:01 PM Doug Anderson wrote: > > Hi, > > On Mon, Jan 31, 2022 at 8:50 AM Doug Anderson wrote: > > > > > Either we leave it as is - which follows my interpretation of what the DT > > > spec says - or we (and the DT maitainers) agree that it shouldn't be > > > there (because this dtb won't run on any random qcom,sc7180 anyways) at > > > all. > > > > I'm curious what part of the DT spec says that we should have the SoC > > in there? I know I've always done it, but it's always just been > > following the examples of what was done before. When talking about the > > root node, I see this in the `devicetree-specification-v0.4-rc1` spec: > > > > --- > > > > Specifies a list of platform architectures with which this platform is > > compatible. This property can be used by operating systems in > > selecting platform specific code. The recommended form of the property > > value is: "manufacturer,model" > > > > For example: > > compatible = "fsl,mpc8572ds" > > > > --- > > > > That doesn't say anything about putting the SoC there. > > > > > > I would also note that I'd be at least moderately inclined to land > > things as-is and deal with this in a follow-up patch, though I'm happy > > to spin if that's what people agree upon too. This is not a new > > problem and so it doesn't seem like it makes sense to glom dealing > > with it into this patch series... > > I noticed that you applied the first 4 patches in the series (thanks!) > but not this one. Are we waiting to get agreement on this before > landing? As per above, I think it'd be OK to land as-is and then I'm > happy to do a follow-up patch to clean this up since this isn't a new > issue. Having this patch outstanding makes it a little confusing with > the other cleanup patches that I'm posting... ;-) I didn't hear anything and I was sending a new version of the cleanup patch series, so I: * Added this last patch to the end of the cleanup series. * Addressed the "-regulator" suffix issue that Stephen pointed out. * Didn't remove the SoC compatible from the top-level node in this patch, but added follow-on patches in the series that do it. Hopefully that looks good to everyone. I removed both of Stephen's and Matthias's review tags from the v3 version. https://lore.kernel.org/r/20220202132301.v3.12.I5604b7af908e8bbe709ac037a6a8a6ba8a2bfa94@changeid -Doug