From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E0E71C433F5 for ; Mon, 10 Oct 2022 10:32:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231470AbiJJKcM (ORCPT ); Mon, 10 Oct 2022 06:32:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39732 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231682AbiJJKcL (ORCPT ); Mon, 10 Oct 2022 06:32:11 -0400 Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ED5483ECE2 for ; Mon, 10 Oct 2022 03:32:08 -0700 (PDT) Received: by mail-ej1-x62d.google.com with SMTP id q9so19388114ejd.0 for ; Mon, 10 Oct 2022 03:32:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fairphone.com; s=fair; h=in-reply-to:references:subject:to:from:message-id:date :content-transfer-encoding:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=sUmw0IHEGVDgOguiSCvP9wAQuCGVsQC+HnuP25zWN0U=; b=LmRr3kNfZrjya+cXTq6NOY9D9HWbQCawhGqHsLhSpWXlrNAEPQIm50xmC9ce6ayxWb VXHsMsnSbQGsNS6ohnkNOlbBtIErwKG7Vel5nq9L9MBKef0ctH2iwKRybQlhWyT7FgSI 0IhTlD2paGZRZRX2f6GVEAxTsnlkW8essDcyTreCzDweSlhPal4GtwxVtl1yo9np8E/3 XAg0fPCYjMr6GZJRgBRxrpBxegzsxj6bHTS9/4veev3TnzsScYxTHPQXUKIKxChZBgqy vKdl8ZzPgTPZDVFecGzd1/t96eS4BOfjFGoD8PDBp3AGq700vUjZInavp4hh6HmoHqJF 2Idg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:references:subject:to:from:message-id:date :content-transfer-encoding:mime-version:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=sUmw0IHEGVDgOguiSCvP9wAQuCGVsQC+HnuP25zWN0U=; b=KacgnBi7YgW6S2jl1CoaR/K/1DGUL4kE5id4mj63Wgb6P2DYEP8p9f6ryJVoopZHtS 95tlKNE31kM6GryWTX21JM1NLLdjEJMAm7W1spAaH0EtBmErBPdA+3Fx0QAZBL4nI0hF zGKufkwluK4IYl1UtN+LmBHcEkDA35QXUv+UOrp4r/RFpFLQPdpIv1DdD3esxzLYhZtN xM0EHu/iISvdG8wPOabAMV4LlEk8nIlj5NbobZvFkqOQTLgByzu2EJAE1561bmmZtG1T yzF5rUJGbvOiYdbtFRlssN2GMJisOc4j2QwtDdJV0/UFwl9ajbupsLP1h7NCAJXWOeqp ay3Q== X-Gm-Message-State: ACrzQf2LB2AiyokbTZiFNAw+dywv4Cdbgh6PHSxl/HiB1wtlyY6bJD+F FFxQPd5viZhLmqI34WFw5UREKA== X-Google-Smtp-Source: AMsMyM6qC8gsE/9iSUwLTzN2y/cZjDjz7nNKiEj5v3E8mrkTZ2TT2fyMPxM5Khu1zEiilpzvPd8U6A== X-Received: by 2002:a17:906:8a76:b0:781:7530:8b05 with SMTP id hy22-20020a1709068a7600b0078175308b05mr14279569ejc.489.1665397927517; Mon, 10 Oct 2022 03:32:07 -0700 (PDT) Received: from localhost (144-178-202-138.static.ef-service.nl. [144.178.202.138]) by smtp.gmail.com with ESMTPSA id j10-20020a17090623ea00b007838e332d78sm5108915ejg.128.2022.10.10.03.32.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 10 Oct 2022 03:32:06 -0700 (PDT) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 10 Oct 2022 12:32:05 +0200 Message-Id: From: "Luca Weiss" To: "Krzysztof Kozlowski" , "Andy Gross" , "Bjorn Andersson" , "Konrad Dybcio" , "linux-arm-msm" , "devicetree@vger.kernel.org" , "Dmitry Baryshkov" , "Alex Elder" , "Nicolas Dechesne" , "Manivannan Sadhasivam" , "Bhupesh Sharma" , "Abel Vesa" , "Bryan O'Donoghue" , "Robert Foss" , "Srinivas Kandagatla" , "Johan Hovold" , "Vinod Koul" , "Stephan Gerhold" , "Caleb Connolly" Subject: Re: Qualcomm DT bindings and DTS cleanups - tracking community wide X-Mailer: aerc 0.12.0 References: <62e95ea6-6b72-a159-56ab-8bb11a5800c8@linaro.org> In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.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, > >=20 > > 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. > >=20 > > What to track: > > 1. Which bindings to convert to YAML, > > 2. Missing compatibles (either entirely or because of missing conversio= n), > > 3. `dt_binding_check` warnings (usually connected with 1-2), > > 4. `dtbs_check` warnings. > >=20 > > 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 fin= d > > tasks for them to get contributions to Linux kernel :). Is anyone in > > community interested in tracking it together, in a public way? > >=20 > > 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 pa= ge?) > > 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