From: Jonathan Marek <jonathan@marek.ca>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sm8450: delete incorrect ufs interconnect fields
Date: Thu, 7 Apr 2022 18:38:34 -0400 [thread overview]
Message-ID: <f1fb2d71-4adf-bcc7-76b3-c7102ab9f2e9@marek.ca> (raw)
In-Reply-To: <865ff6bc-95a2-8b39-5cf2-bb2d3f592c5a@linaro.org>
On 4/7/22 5:16 PM, Krzysztof Kozlowski wrote:
> On 07/04/2022 21:40, Vladimir Zapolskiy wrote:
>> On 4/7/22 20:21, Jonathan Marek wrote:
>>> Upstream sm8450.dtsi has #interconnect-cells = <2>; so these are wrong.
>>> Ignored and undocumented with upstream UFS driver so delete for now.
>
> This is the upstream and they are documented here, although as pointed
> by Vladimir this was rather a reverse-documentation. The documentation
> might be incorrect, but then the bindings should be corrected instead of
> only modifying the DTS.
>
>>
>> Basically the description was added by a commit 462c5c0aa798 ("dt-bindings: ufs:
>> qcom,ufs: convert to dtschema").
>>
>> It's questionable, if an example in the new yaml file is totally correct
>> in connection to the discussed issue.
>
> To be honest - the example probably is not correct, because it was based
> on existing DTS without your patch. :)
>
> Another question is whether the interconnect properties are here correct
> at all. I assumed that DTS is correct because it should describe the
> hardware, even if driver does not use it. However maybe that was a false
> assumption...
>
writing-bindings.rst says it is OK to document even if it isn't used by
the driver (seems wrong to me, at least for interconnects which are a
firmware abstraction and not hardware).
462c5c0aa798 wasn't in my 5.17+ tree pulled after dts changes were
merged (I guess doc changes come later), so my commit message is
incorrect, but I think it makes more sense to have the documentation
reflect the driver. Its also not an important issue, so I'll let others
sort it out.
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2022-04-07 22:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 17:21 [PATCH] arm64: dts: qcom: sm8450: delete incorrect ufs interconnect fields Jonathan Marek
2022-04-07 19:40 ` Vladimir Zapolskiy
2022-04-07 21:16 ` Krzysztof Kozlowski
2022-04-07 22:38 ` Jonathan Marek [this message]
2022-04-12 2:16 ` Bjorn Andersson
2022-04-12 4:04 ` Jonathan Marek
2022-04-12 20:51 ` Bjorn Andersson
2022-04-12 21:07 ` Jonathan Marek
2022-04-14 18:35 ` Dmitry Baryshkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1fb2d71-4adf-bcc7-76b3-c7102ab9f2e9@marek.ca \
--to=jonathan@marek.ca \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
--cc=vladimir.zapolskiy@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).