From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: 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>,
Luca Weiss <luca.weiss@fairphone.com>,
Vinod Koul <vinod.koul@linaro.org>,
Stephan Gerhold <stephan@gerhold.net>,
Caleb Connolly <kc@postmarketos.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Trilok Soni <quic_tsoni@quicinc.com>,
Johan Hovold <johan@kernel.org>
Subject: Re: Qualcomm DT bindings and DTS cleanups - tracking community wide
Date: Tue, 11 Oct 2022 09:57:03 -0400 [thread overview]
Message-ID: <0f5bb12f-814d-37f2-9307-b2b649aedfe3@linaro.org> (raw)
In-Reply-To: <62e95ea6-6b72-a159-56ab-8bb11a5800c8@linaro.org>
On 22/09/2022 10: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)
>
> I am leaning towards Gitlab pages because they could be quite automated
> - with CI or with scripts.
This could be looking like that - the list of missing compatibles from
Rob's tasks:
https://gitlab.com/krzkoz/linux-dt-todo/-/blob/main/todo-compatibles.rst
There is a script which will automatically add new entries to the list
(above RST file), once fed with Rob's job output. Further this could be
probably pipelined with Rob's jobs.
List anyway has to be manually updated with work in progress.
This is for the compatibles. Missing part is doing something similar for
the dtbs_check warnings.
In replies Luca, Caleb and Neil mentioned GitLab issues. That could be
useful, so if someone would like to hook into GitLab API - feel free to
work on that (either in that repo or in separate).
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-10-11 13:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 14:32 Qualcomm DT bindings and DTS cleanups - tracking community wide Krzysztof Kozlowski
2022-10-04 14:50 ` Krzysztof Kozlowski
2022-10-04 16:37 ` Trilok Soni
2022-10-06 7:57 ` Krzysztof Kozlowski
2022-10-10 10:32 ` Luca Weiss
2022-10-10 15:10 ` Krzysztof Kozlowski
2022-10-10 16:52 ` Neil Armstrong
2022-10-10 11:34 ` Caleb Connolly
2022-10-10 15:10 ` Krzysztof Kozlowski
2022-10-06 8:21 ` Johan Hovold
2022-10-06 8:39 ` Krzysztof Kozlowski
2022-10-06 15:07 ` Johan Hovold
2022-10-06 9:44 ` Dmitry Baryshkov
2022-10-06 15:20 ` Johan Hovold
2022-10-11 13:57 ` Krzysztof Kozlowski [this message]
2022-10-13 12:46 ` Krzysztof Kozlowski
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=0f5bb12f-814d-37f2-9307-b2b649aedfe3@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhupesh.sharma@linaro.org \
--cc=bryan.odonoghue@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=elder@linaro.org \
--cc=johan+linaro@kernel.org \
--cc=johan@kernel.org \
--cc=kc@postmarketos.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=neil.armstrong@linaro.org \
--cc=nicolas.dechesne@linaro.org \
--cc=quic_tsoni@quicinc.com \
--cc=robert.foss@linaro.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=stephan@gerhold.net \
--cc=vinod.koul@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).