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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id A9479C433FE for ; Thu, 14 Apr 2022 07:10:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240287AbiDNHNA (ORCPT ); Thu, 14 Apr 2022 03:13:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39126 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240281AbiDNHM7 (ORCPT ); Thu, 14 Apr 2022 03:12:59 -0400 Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C8641DF2F for ; Thu, 14 Apr 2022 00:10:34 -0700 (PDT) Received: by mail-ej1-x62c.google.com with SMTP id p15so8275526ejc.7 for ; Thu, 14 Apr 2022 00:10:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=vXc9aotX8pItntv6nrbEQeQkIWFJAZuwrUVeDNb5KEY=; b=oGRYsPmA7r5aH6nEOkafv18jXIudJ4QSnqZ4Eqphri03GL0sKRs2CoFpW4rT7egeSV +/Ofo9+Rb6zqPRNeQxM3aCEw9NVH7O3FXWQ+WZsghvrrs/4pCAE3JAwDO28glperM7uf FtaM/HcV/JEAN2bQdGFQOwlLGULvPeKPD9qCFhng8QkPKf8wgEY6kZfzzfLFdaCi3PQ+ 42vNJfVWxiDtyGb86VIxXSUxHnpUT+TSt3yZUGIs7dGb97afnHrXeQogjoiwjAb0v6RL 6RjdmVFJjsm+Zl0LVX2h4w8WAuGsN++p5KFafpnqg55HV/NFHu/6BR6tYy+wWhS0zRf1 Cy3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=vXc9aotX8pItntv6nrbEQeQkIWFJAZuwrUVeDNb5KEY=; b=OVNbbLbeJOtBDXo+bP9O6iEY42Uu6wjpgH+JsS8WzVvCn8hOtcNRwcne75qMOzQ4Cs CozQR90BS/QocV/g6WmZ6Jto+TtqLPsYsK5UvABv2SJ0ZspFS55NlnqcVa8Y2NT7Jxtm GsygODiF8GWZ8jfQ07TIW1C/GZpWIYbrnqBW4Lbu0moehhUSUu0S0+pHe/jydJTmBc/4 ca8RSh9wp/ZE5mPvrOmTYr8j+QGg4CqmO1LWOImIeREb15zOI1E3V0ZwpHxNIVQZ77Fp /fAdUfkomylLEzTAgeldcEJwEYa2e2aGcwoBlcZwHTp+bjEy0UT1eZXVgrnjd5NdMKQq bbKg== X-Gm-Message-State: AOAM5319y8k/RN/vy+6j5UHDhAvcRo83+F6MSeV97NvfIlykJPmaCoja 8E0f2FldqJ0dfH2MG7MR33AhJA== X-Google-Smtp-Source: ABdhPJxbn1hFLOcOehZlEtYBz6/zRzSwJimnPFP6rtn1IUphaeXpCXp1/vqdvJmP6/y4ydceI58nmQ== X-Received: by 2002:a17:907:94d6:b0:6eb:6a12:df60 with SMTP id dn22-20020a17090794d600b006eb6a12df60mr1089630ejc.68.1649920233387; Thu, 14 Apr 2022 00:10:33 -0700 (PDT) Received: from [192.168.0.209] (xdsl-188-155-201-27.adslplus.ch. [188.155.201.27]) by smtp.gmail.com with ESMTPSA id u3-20020a17090657c300b006d01de78926sm356507ejr.22.2022.04.14.00.10.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 14 Apr 2022 00:10:32 -0700 (PDT) Message-ID: Date: Thu, 14 Apr 2022 09:10:32 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [PATCH] CHROMIUM: arm64: dts: qcom: Add sc7180-gelarshie Content-Language: en-US To: Doug Anderson Cc: Mars Chen , Andy Gross , Bjorn Andersson , Rob Herring , Krzysztof Kozlowski , linux-arm-msm , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , LKML References: <20220330090947.9100-1-chenxiangrui@huaqin.corp-partner.google.com> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 13/04/2022 23:48, Doug Anderson wrote: > I'm actually kinda curious: is there really a good reason for this? I > know I haven't been adding things to > `Documentation/devicetree/bindings/arm/qcom.yaml` for Qualcomm > Chromebooks. Ironically, it turns out that the script I typically use > to invoke checkpatch happens to have "--no-tree" as an argument and > that seems to disable this check. Doh! > > That being said, though, I do wonder a little bit about the value of > enumerating the top-level compatible like this in a yaml file. > Certainly the yaml schema validation in general can be quite useful, > but this top-level listing seems pure overhead. I guess it makes some > tools happy, but other than that it seems to provide very little > value... If compatible is not part of ABI, it is allowed to change in whatever shape one wishes. In such case, how can anyone (e.g. user-space) identify the board? Model name? Also not part of ABI (not documented)... Best regards, Krzysztof