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
