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;
Date:   Mon, 5 Dec 2022 14:12:48 +0100
From:   Johan Hovold <johan@kernel.org>
To:     Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc:     Johan Hovold <johan+linaro@kernel.org>,
        Bjorn Andersson <andersson@kernel.org>,
        Alim Akhtar <alim.akhtar@samsung.com>,
        Avri Altman <avri.altman@wdc.com>,
        Andy Gross <agross@kernel.org>,
        Konrad Dybcio <konrad.dybcio@linaro.org>,
        Bart Van Assche <bvanassche@acm.org>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
        devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: ufs: qcom: allow 'dma-coherent' property
Message-ID: <Y43uUA2X4Vzn+VLF@hovoldconsulting.com>
References: <20221205100837.29212-1-johan+linaro@kernel.org>
 <20221205100837.29212-2-johan+linaro@kernel.org>
 <20221205115906.GA20192@thinkpad>
 <Y43e9KRDsTCS5VI4@hovoldconsulting.com>
 <20221205122018.GC20192@thinkpad>
 <Y43jtpHqlyiIEZ0S@hovoldconsulting.com>
 <20221205130048.GD20192@thinkpad>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20221205130048.GD20192@thinkpad>
Precedence: bulk

On Mon, Dec 05, 2022 at 06:30:48PM +0530, Manivannan Sadhasivam wrote:
> On Mon, Dec 05, 2022 at 01:27:34PM +0100, Johan Hovold wrote:
> > On Mon, Dec 05, 2022 at 05:50:18PM +0530, Manivannan Sadhasivam wrote:
> > > On Mon, Dec 05, 2022 at 01:07:16PM +0100, Johan Hovold wrote:
> > > > On Mon, Dec 05, 2022 at 05:29:06PM +0530, Manivannan Sadhasivam wrote:
> > > > > On Mon, Dec 05, 2022 at 11:08:36AM +0100, Johan Hovold wrote:
> > > > > > UFS controllers may be cache coherent and must be marked as such in the
> > > > > > devicetree to avoid data corruption.
> > > > > > 
> > > > > > This is specifically needed on recent Qualcomm platforms like SC8280XP.
> > > > > > 
> > > > > > Signed-off-by: Johan Hovold <johan+linaro@kernel.org>

> > > > Yes, it would be a valid, but it will only be added to the DTs of SoCs
> > > > that actually require it. No need to re-encode the dtsi in the binding.
> > > > 
> > > 
> > > But if you make a property valid in the binding then it implies that anyone
> > > could add it to DTS which is wrong. You should make this property valid for
> > > SoCs that actually support it.
> > 
> > No, it's not wrong.
> > 
> > Note that the binding only requires 'compatible' and 'regs', all other
> > properties are optional, and you could, for example, add a
> > 'reset' property to a node for a device which does not have a reset
> > without the DT validation failing.
> > 
> 
> Then what is the point of devicetree validation using bindings?

You're still making sure that no properties are added that are not
documented, number of clocks, names of clocks, etc.

> There is also a comment from Krzysztof: https://lkml.org/lkml/2022/11/24/390

Speaking of Krzysztof:

	https://lore.kernel.org/lkml/20221204094717.74016-5-krzysztof.kozlowski@linaro.org/

Johan