devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Caleb Connolly <caleb@connolly.tech>
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>,
	Luca Weiss <luca.weiss@fairphone.com>,
	Vinod Koul <vinod.koul@linaro.org>,
	Stephan Gerhold <stephan@gerhold.net>
Subject: Re: Qualcomm DT bindings and DTS cleanups - tracking community wide
Date: Mon, 10 Oct 2022 11:34:44 +0000	[thread overview]
Message-ID: <a5bc5342-be84-9a1b-e40a-1cb9ceea47ae@connolly.tech> (raw)
In-Reply-To: <faa4e821-00e0-4ee0-0c62-b5eb6f75abf7@linaro.org>



On 04/10/2022 15:50, 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?

Hi Krzysztof,

I think a GitLab repo with some automatically generated issues and some sort of
overall coverage map might be a good way to track this. Especially if it can be
shown on a per-device basis as well.


>
> Best regards,
> Krzysztof
>

--
Kind Regards,
Caleb


  parent reply	other threads:[~2022-10-10 11:34 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 [this message]
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
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=a5bc5342-be84-9a1b-e40a-1cb9ceea47ae@connolly.tech \
    --to=caleb@connolly.tech \
    --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=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=luca.weiss@fairphone.com \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=nicolas.dechesne@linaro.org \
    --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).