Re: Qualcomm DT bindings and DTS cleanups - tracking community wide

From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Andy Gross" <agross@kernel.org>,
	"Bjorn Andersson" <andersson@kernel.org>,
	"Konrad Dybcio" <konrad.dybcio@somainline.org>,
	"linux-arm-msm" <linux-arm-msm@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
	"Alex Elder" <elder@linaro.org>,
	"Nicolas Dechesne" <nicolas.dechesne@linaro.org>,
	"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	"Bhupesh Sharma" <bhupesh.sharma@linaro.org>,
	"Abel Vesa" <abel.vesa@linaro.org>,
	"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>,
	"Robert Foss" <robert.foss@linaro.org>,
	"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
	"Johan Hovold" <johan+linaro@kernel.org>,
	"Vinod Koul" <vinod.koul@linaro.org>,
	"Stephan Gerhold" <stephan@gerhold.net>,
	"Caleb Connolly" <kc@postmarketos.org>
Subject: Re: Qualcomm DT bindings and DTS cleanups - tracking community wide
Date: Mon, 10 Oct 2022 12:32:05 +0200	[thread overview]
Message-ID: <CNI6AL1JKZ1L.2QLO9D3KZJ2MR@otso> (raw)
In-Reply-To: <faa4e821-00e0-4ee0-0c62-b5eb6f75abf7@linaro.org>

Hi Krzysztof,

On Tue Oct 4, 2022 at 4:50 PM CEST, Krzysztof Kozlowski wrote:
> On 22/09/2022 16:32, Krzysztof Kozlowski wrote:
> > Hi everyone,
> > 
> > Quite a lot of people are working on Qualcomm DT bindings conversion
> > (TXT->YAML) and fixups to Qualcomm DTS. We track a bit of this effort
> > internally in Linaro, but that has many shortcomings and we would like
> > to track it rather community-wide with the support and contributions
> > from the community.
> > 
> > What to track:
> > 1. Which bindings to convert to YAML,
> > 2. Missing compatibles (either entirely or because of missing conversion),
> > 3. `dt_binding_check` warnings (usually connected with 1-2),
> > 4. `dtbs_check` warnings.
> > 
> > Rob's bot gives us daily output for 1-4, but how can we track current
> > efforts to avoid duplication of work? Also it would allow people to find
> > tasks for them to get contributions to Linux kernel :). Is anyone in
> > community interested in tracking it together, in a public way?
> > 
> > If so, where?
> > A. elinux.org (needs some formatting when pasting the output from tools)
> > B. gitlab pages/wiki (maybe scripts could parse tools and create the page?)
> > C. gitlab dedicated repo - some text file
> > D. Linux kernel TODO file (might be difficult to keep updated)
> > E. kernel.org wiki (requires LF accounts, AFAIK, a bit pain to edit; I
> > have it for Exynos but I don't find it usable -
> > https://exynos.wiki.kernel.org/todo_tasks)
>
>
> Hi All,
>
> Any thoughts on this? So far I did not receive any responses, so
> probably this could mean that there is little interest in this?

I'd also appreciate having something there. Similar to the count of
similar warnings that Rob is sometimes posting, I personally don't
see those apart from checking my boards (msm8226, msm8974, msm8953,
sm6350), where I recently did a cleanup spree for 8974 for low-hanging
fruit. Of course given that not every device uses all the functionality
some things that are disabled on my fairphone-fp2 device I won't see,
but only when checking other devices e.g. lg-hammerhead.

So some gitlab project with issues for each thing would be pretty nice I
believe. While I probably won't tackle big topics like mdss+mdp5 because
it's just very complex, I'm happy to pick up some small tasks that are
(comparatively) quick to fix.

Regards
Luca

>
> Best regards,
> Krzysztof