Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp4756506pxb; Tue, 28 Sep 2021 03:27:44 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwdvlGZ8MPph77hdSGjKRWYMkUMZ1SpJqXA6mhOYbnucNTfS2GeP1IG8lUWlMPC5d1VYriz X-Received: by 2002:a17:906:ece1:: with SMTP id qt1mr5760760ejb.281.1632824864189; Tue, 28 Sep 2021 03:27:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1632824864; cv=none; d=google.com; s=arc-20160816; b=0TrC7D+hy9P+wgQfv0Er/J4nClW2swX3v25odGYcyj97KmPtuk0bZReHUj5lXt+7vc O/3t0fRDzkW9ZUQtVenc6qgd/nlpr8pl0a5B8sRYBHk1SyP9pOu4fh0/RUqm5r2h/xjT ezTipfh0lkdd2luAxJjDGgL/NyBut7+gj7eQMRdP+T8pwL6GI2h5iFCLTx+C8JCMegEJ fSKNKET/QCMeq8IJCm0SxogM2A6KlvO5xsw+1OyO4qFKAwrTcqBid5w3RbD4kKOcsfT0 24AVI3EIk3yTLy0oC7KNi2UeYLWTxtuv/vhPmBPhO8xBkI9I+f1LoBfo1FVBTjNaz4B7 CVnw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=zlZ7tFTRJhpCCgiAaXyQJqTvywOUygVuhXAlOlCKPKc=; b=0y0prM6hrR0nB0Q70nueBjnO527XaW0yz1Q0TIQgujinITf+L+aCb2toSwpwh/MZ5d XP6qhsPkpB/9K73KaPdvmRQ23KUf8gwsIqCkM8Rm6+5J+PdAr+ty/ZZAS4oSzQwvHf2l WZbbAqhU2ezdTlxCbjrKKlnGiIg/kFtKgfuFM31Xt9j5dvVgSuP1Bc6daD2kJZUUu+PQ Y4sivm5RztQaqu+LIFbX4IK0BqtBi22OLzvRKMcpqOHUJM8BgJgMP17uh9L+XzMLzqR1 XZu7gqM1BCO53tcS/RDOkMs6KcWau0QyNSQAht5lgZ3HCGnHktkS/JCIK2Uu/O8pttKl r1FQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gerhold.net header.s=strato-dkim-0002 header.b=SxeLQAe7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id hz13si2624050ejc.2.2021.09.28.03.27.17; Tue, 28 Sep 2021 03:27:44 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gerhold.net header.s=strato-dkim-0002 header.b=SxeLQAe7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240068AbhI1K0x (ORCPT + 99 others); Tue, 28 Sep 2021 06:26:53 -0400 Received: from mo4-p01-ob.smtp.rzone.de ([85.215.255.54]:9000 "EHLO mo4-p01-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239952AbhI1K0w (ORCPT ); Tue, 28 Sep 2021 06:26:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1632824530; s=strato-dkim-0002; d=gerhold.net; h=In-Reply-To:References:Message-ID:Subject:Cc:To:From:Date:Cc:Date: From:Subject:Sender; bh=zlZ7tFTRJhpCCgiAaXyQJqTvywOUygVuhXAlOlCKPKc=; b=SxeLQAe7vkBWh3xilHdNU4/rM3gOEPswGTM6DAnd55Pli8SYFBgXGGmVlY+T/v/s/W UIwdlyBWjyGFk17puCrmW4akytuQjgo8hLVwVY73zJ3hJbPrLLby5zElzlEgUFn4P0zE uA5qTsBk4zfHYU5M7ny4K3aqQHfaqbCKtRkBbPzNsUL5c6UX1yBcGP1yv+sxX6C6QOJb ntlNMcyv8AOQX5WC/lF7Y/eteAZmGNGaKSUXjrRpjMrGXu98m5bgy20HB2FIVs4QKBn+ oTHhk5pN08/oxzhUGTgFzhdsEUo18L9zFgtk48uxf9puRav0kl6j0a5BKKRMaRqOwR6H a3uw== Authentication-Results: strato.com; dkim=none X-RZG-AUTH: ":P3gBZUipdd93FF5ZZvYFPugejmSTVR2nRPhVOQ/OcYgojyw4j34+u261EJF5OxJD4pSA8ZyK1A==" X-RZG-CLASS-ID: mo00 Received: from gerhold.net by smtp.strato.de (RZmta 47.33.8 DYNA|AUTH) with ESMTPSA id 301038x8SAM9jsq (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Tue, 28 Sep 2021 12:22:09 +0200 (CEST) Date: Tue, 28 Sep 2021 12:22:05 +0200 From: Stephan Gerhold To: Bjorn Andersson , Rob Herring Cc: Andy Gross , Frank Rowand , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/3] dt-bindings: soc: smem: Make indirection optional Message-ID: References: <20210928044546.4111223-1-bjorn.andersson@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210928044546.4111223-1-bjorn.andersson@linaro.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 27, 2021 at 09:45:44PM -0700, Bjorn Andersson wrote: > In the olden days the Qualcomm shared memory (SMEM) region consisted of > multiple chunks of memory, so SMEM was described as a standalone node > with references to its various memory regions. > > But practically all modern Qualcomm platforms has a single reserved memory > region used for SMEM. So rather than having to use two nodes to describe > the one SMEM region, update the binding to allow the reserved-memory > region alone to describe SMEM. > > The olden format is preserved as valid, as this is widely used already. > > Signed-off-by: Bjorn Andersson > --- > .../bindings/soc/qcom/qcom,smem.yaml | 34 ++++++++++++++++--- > 1 file changed, 30 insertions(+), 4 deletions(-) > > diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,smem.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,smem.yaml > index f7e17713b3d8..4149cf2b66be 100644 > --- a/Documentation/devicetree/bindings/soc/qcom/qcom,smem.yaml > +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,smem.yaml > [...] > @@ -43,6 +55,20 @@ examples: > #size-cells = <1>; > ranges; > > + smem@fa00000 { I think this is a good opportunity to make a decision which node name should be used here. :) You use smem@ here but mentioned before that you think using the generic memory@ would be better [1]. And you use memory@ in PATCH 3/3: - smem_mem: memory@86000000 { + memory@86000000 { + compatible = "qcom,smem"; reg = <0x0 0x86000000 0 0x200000>; no-map; + hwlocks = <&tcsr_mutex 3>; }; However, if you would use memory@ as example in this DT schema, Rob's bot would complain with the same error that I mentioned earlier [2]: soc/qcom/qcom,smem.example.dt.yaml: memory@fa00000: 'device_type' is a required property From schema: dtschema/schemas/memory.yaml We should either fix the error when using memory@ or start using some different node name (Stephen Boyd suggested shared-memory@ for example). Otherwise we'll just keep introducing more and more dtbs_check errors for the Qualcomm device trees. Thanks, Stephan [1]: https://lore.kernel.org/linux-arm-msm/YUo0suaIugOco1Vu@builder.lan/ [2]: https://lore.kernel.org/linux-arm-msm/YUo2ZzQktf2iSec%2F@gerhold.net/