Message ID | 20230725101610.75122-1-krzysztof.kozlowski@linaro.org |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:9010:0:b0:3e4:2afc:c1 with SMTP id l16csp2383257vqg; Tue, 25 Jul 2023 03:55:11 -0700 (PDT) X-Google-Smtp-Source: APBJJlEtbTYd7Fi12UJcT8GdaOXUQOxHpss+X3ar1b/T83YvDgMhmY8MuGaIy70ShPlkiUhF9Z2x X-Received: by 2002:a05:6e02:12c1:b0:348:dc65:3cc with SMTP id i1-20020a056e0212c100b00348dc6503ccmr2863667ilm.12.1690282511234; Tue, 25 Jul 2023 03:55:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1690282511; cv=none; d=google.com; s=arc-20160816; b=SQViB5IW97qrUBfNR5dbJduOb5/8pYHy1kgHww0evQWnfjLyzKTquUNbElr+Y2TPh8 e+x8J1iKxVjTCMjmrmot34S7AH0BlC8RndvX5hnrbeQ9FBsvJ4PA/9gm7pSDnpg1cf2m we3JSe4VH9B/SgAm6QssJX1biwOWGAb4qWaUIo0BMWWnyON5siXlXShP5U0uH3t0svQx YuQUN49DmCjRmO219hOgn+cODFzzSVtsUxfdYB89kIHkwthEXIL3E1XYok5iwN+ZOYfW +ce91LNr8lGHrOs6yznkuqm/RBW5dP+MXrTQKpDs+qb2GZpO6KJyGl51mh6dQmcSvomc T5gQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=kgjzM14QEiL69p/YLX8lqgzuetXlnguUNrcPLd50K6I=; fh=gOk0pNcYx/8/TRg4qJzroDwcpzwtpESU5OT09hL7HyU=; b=00Cr7cEKKkY5DKdgcgWWMnkFSTk1rs7Yh1Y0QfabQxM1wmaVRjbXztY0QtEgqcbKDj 7rYpF7LZfUy5phtt1HvrA2igNZa6WKMhAWEABntjwyX8Ji94BCza03N5C6EroGJB9kwu LtqxISQF7z7iEsQqGm0/4koX1J38p3+bB8R6jPJCQJOu6eZKt9NDW/GPiqQFsnD+W6vq j8xkjX8mV595STxdNPUTUTSbQ3BzGY6yU089Woabncs4koJKm+P9XvpugyTH9TBqvSrp 2vNhocCBHlnQ6d1AYYKcEvsUkA37Y4elsHwNSSsYdJcpP5VDWfzb4pM/hsjv2EuuXzJg s5Og== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b="C4czm/+X"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l63-20020a639142000000b0055c875d784dsi11554897pge.374.2023.07.25.03.54.58; Tue, 25 Jul 2023 03:55:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b="C4czm/+X"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232109AbjGYKQq (ORCPT <rfc822;kloczko.tomasz@gmail.com> + 99 others); Tue, 25 Jul 2023 06:16:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41560 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232849AbjGYKQm (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Tue, 25 Jul 2023 06:16:42 -0400 Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CB8561BCB for <linux-kernel@vger.kernel.org>; Tue, 25 Jul 2023 03:16:17 -0700 (PDT) Received: by mail-ed1-x52f.google.com with SMTP id 4fb4d7f45d1cf-5221f193817so4212490a12.3 for <linux-kernel@vger.kernel.org>; Tue, 25 Jul 2023 03:16:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1690280176; x=1690884976; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=kgjzM14QEiL69p/YLX8lqgzuetXlnguUNrcPLd50K6I=; b=C4czm/+Xz2UutJXlca3VkY/5VlywrDLHuMNp4CGjo7VZ0TpqzJjydvmrSDzTVSgAEt +K3IZtgfB7epGyj4hbxX3wdBDlHFLyGYF8k87sMiH+G1gcqAMx40aZLy7MF9s5xeQP5x fhnbmSwYWkAVdLsXKHBG7KQami1/9ue4beRYmJdyrSe/ka3umBmFTIAsEMhYhkmED0+n h/tD+XzOhnhPcv7zRtsI2fsZdxpvyQNcwnEGlJZJJczCbDOtfM40WLASHHbA4aiLIfjA D/rEU4Og78VLM9QbuzZ0XS+STA60ygyZjzHaQn79vehoGSKmUMX5h5wYMfmhLuvrMwXR vuJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690280176; x=1690884976; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=kgjzM14QEiL69p/YLX8lqgzuetXlnguUNrcPLd50K6I=; b=kHoVgVIg7k3TranJqQ8E0iLtdA45ojOiG9vdBiueq/82mZZ08/BLebDj7YtlBqzyT4 L8uGv/CDaYnBsaK8az3x50uItVlvkyYXr5qAOQNZ//78C9/lZ2UvDyZXZ1Y3/Bp1wiAU IyVDJQxrmUYaXdKxXWVYhZ9sSbL04qzmUzrv2edZ22ea+r2aOxokF/JpTeHWyQGzfJHQ NG70WNTeXzF0lJhecSgoHfegTWwhBzd2+b9pATd/ydTbTfZIPCmmnxxlnrSnu2wGrIGx iCK+0LxvJVingLBoQ9FG9UHohbhrn9n/AGy3VppXa0xApTF0/wDvhPiL/27LB1jujRlU hlKg== X-Gm-Message-State: ABy/qLaIVBvN/F44gm4aOKlazkbSOg7DyCFBTGukDeUfZZpzL78UgJmg opw5W3kvCXcifCleoUmKqMdg/A== X-Received: by 2002:aa7:d410:0:b0:522:3a0d:38c2 with SMTP id z16-20020aa7d410000000b005223a0d38c2mr3214909edq.9.1690280176127; Tue, 25 Jul 2023 03:16:16 -0700 (PDT) Received: from krzk-bin.. ([178.197.223.104]) by smtp.gmail.com with ESMTPSA id f23-20020a05640214d700b005224ec27dd7sm544171edx.66.2023.07.25.03.16.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 25 Jul 2023 03:16:15 -0700 (PDT) From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> To: Rob Clark <robdclark@gmail.com>, Abhinav Kumar <quic_abhinavk@quicinc.com>, Dmitry Baryshkov <dmitry.baryshkov@linaro.org>, Sean Paul <sean@poorly.run>, Marijn Suijten <marijn.suijten@somainline.org>, David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>, linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Subject: [PATCH] dt-bindings: display: msm: sm6125-mdss: drop unneeded status from examples Date: Tue, 25 Jul 2023 12:16:10 +0200 Message-Id: <20230725101610.75122-1-krzysztof.kozlowski@linaro.org> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: 1772389674480258236 X-GMAIL-MSGID: 1772389674480258236 |
Series |
dt-bindings: display: msm: sm6125-mdss: drop unneeded status from examples
|
|
Commit Message
Krzysztof Kozlowski
July 25, 2023, 10:16 a.m. UTC
Example DTS should not have 'status' property.
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
---
.../devicetree/bindings/display/msm/qcom,sm6125-mdss.yaml | 6 ------
1 file changed, 6 deletions(-)
Comments
On 2023-07-25 12:16:10, Krzysztof Kozlowski wrote: > Example DTS should not have 'status' property. > > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > --- > .../devicetree/bindings/display/msm/qcom,sm6125-mdss.yaml | 6 ------ This is not needed: it has already been corrected in v3 and v4 of the respective series (among other changes) and the patches were only picked to a preliminary (draft) pull to get an overview of the outstanding work for this subsystem. That branch happens to be included in regular -next releases though. 6.6 drm/msm display pull: https://gitlab.freedesktop.org/drm/msm/-/merge_requests/69 v3: https://lore.kernel.org/linux-arm-msm/20230718-sm6125-dpu-v3-0-6c5a56e99820@somainline.org/ v4: https://lore.kernel.org/linux-arm-msm/20230723-sm6125-dpu-v4-0-a3f287dd6c07@somainline.org/ - Marijn > 1 file changed, 6 deletions(-) > > diff --git a/Documentation/devicetree/bindings/display/msm/qcom,sm6125-mdss.yaml b/Documentation/devicetree/bindings/display/msm/qcom,sm6125-mdss.yaml > index 2525482424cb..479c82e6a0d8 100644 > --- a/Documentation/devicetree/bindings/display/msm/qcom,sm6125-mdss.yaml > +++ b/Documentation/devicetree/bindings/display/msm/qcom,sm6125-mdss.yaml > @@ -95,8 +95,6 @@ examples: > #size-cells = <1>; > ranges; > > - status = "disabled"; > - > display-controller@5e01000 { > compatible = "qcom,sm6125-dpu"; > reg = <0x05e01000 0x83208>, > @@ -170,8 +168,6 @@ examples: > #address-cells = <1>; > #size-cells = <0>; > > - status = "disabled"; > - > ports { > #address-cells = <1>; > #size-cells = <0>; > @@ -210,8 +206,6 @@ examples: > > required-opps = <&rpmpd_opp_svs>; > power-domains = <&rpmpd SM6125_VDDMX>; > - > - status = "disabled"; > }; > }; > ... > -- > 2.34.1 >
On 25/07/2023 13:46, Marijn Suijten wrote: > On 2023-07-25 12:16:10, Krzysztof Kozlowski wrote: >> Example DTS should not have 'status' property. >> >> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> >> --- >> .../devicetree/bindings/display/msm/qcom,sm6125-mdss.yaml | 6 ------ > > This is not needed: it has already been corrected in v3 and v4 of the > respective series (among other changes) and the patches were only picked > to a preliminary (draft) pull to get an overview of the outstanding work > for this subsystem. That branch happens to be included in regular -next > releases though. > > 6.6 drm/msm display pull: https://gitlab.freedesktop.org/drm/msm/-/merge_requests/69 > v3: https://lore.kernel.org/linux-arm-msm/20230718-sm6125-dpu-v3-0-6c5a56e99820@somainline.org/ > v4: https://lore.kernel.org/linux-arm-msm/20230723-sm6125-dpu-v4-0-a3f287dd6c07@somainline.org/ What do you mean? The old code (one I am fixing) is in current next... If this was fixed, why next gets some outdated branches of drm next? Each maintainers next tree is supposed to be fed into the next, without delays. Best regards, Krzysztof
On 26/07/2023 09:27, Krzysztof Kozlowski wrote: > On 25/07/2023 13:46, Marijn Suijten wrote: >> On 2023-07-25 12:16:10, Krzysztof Kozlowski wrote: >>> Example DTS should not have 'status' property. >>> >>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> >>> --- >>> .../devicetree/bindings/display/msm/qcom,sm6125-mdss.yaml | 6 ------ >> >> This is not needed: it has already been corrected in v3 and v4 of the >> respective series (among other changes) and the patches were only picked >> to a preliminary (draft) pull to get an overview of the outstanding work >> for this subsystem. That branch happens to be included in regular -next >> releases though. >> >> 6.6 drm/msm display pull: https://gitlab.freedesktop.org/drm/msm/-/merge_requests/69 >> v3: https://lore.kernel.org/linux-arm-msm/20230718-sm6125-dpu-v3-0-6c5a56e99820@somainline.org/ >> v4: https://lore.kernel.org/linux-arm-msm/20230723-sm6125-dpu-v4-0-a3f287dd6c07@somainline.org/ > > What do you mean? The old code (one I am fixing) is in current next... > > If this was fixed, why next gets some outdated branches of drm next? > Each maintainers next tree is supposed to be fed into the next, without > delays. > Ah, I think I understood - some work in progress was applied to work-in-progress branch of drm/msm and this somehow got pushed to linux-next? How anyone is supposed to work on next branches if they are outdated or have stuff known to be incomplete? Best regards, Krzysztof
On 26/07/2023 10:31, Krzysztof Kozlowski wrote: > On 26/07/2023 09:27, Krzysztof Kozlowski wrote: >> On 25/07/2023 13:46, Marijn Suijten wrote: >>> On 2023-07-25 12:16:10, Krzysztof Kozlowski wrote: >>>> Example DTS should not have 'status' property. >>>> >>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> >>>> --- >>>> .../devicetree/bindings/display/msm/qcom,sm6125-mdss.yaml | 6 ------ >>> >>> This is not needed: it has already been corrected in v3 and v4 of the >>> respective series (among other changes) and the patches were only picked >>> to a preliminary (draft) pull to get an overview of the outstanding work >>> for this subsystem. That branch happens to be included in regular -next >>> releases though. >>> >>> 6.6 drm/msm display pull: https://gitlab.freedesktop.org/drm/msm/-/merge_requests/69 >>> v3: https://lore.kernel.org/linux-arm-msm/20230718-sm6125-dpu-v3-0-6c5a56e99820@somainline.org/ >>> v4: https://lore.kernel.org/linux-arm-msm/20230723-sm6125-dpu-v4-0-a3f287dd6c07@somainline.org/ >> >> What do you mean? The old code (one I am fixing) is in current next... >> >> If this was fixed, why next gets some outdated branches of drm next? >> Each maintainers next tree is supposed to be fed into the next, without >> delays. >> > > Ah, I think I understood - some work in progress was applied to > work-in-progress branch of drm/msm and this somehow got pushed to > linux-next? How anyone is supposed to work on next branches if they are > outdated or have stuff known to be incomplete? The drm/msm & bindings parts were considered final, but then I failed to send 'applied' series for some reason. And then it was natural for Marijn to send an updated revision.
On 2023-07-26 10:42:24, Dmitry Baryshkov wrote: > On 26/07/2023 10:31, Krzysztof Kozlowski wrote: > > On 26/07/2023 09:27, Krzysztof Kozlowski wrote: > >> On 25/07/2023 13:46, Marijn Suijten wrote: > >>> On 2023-07-25 12:16:10, Krzysztof Kozlowski wrote: > >>>> Example DTS should not have 'status' property. > >>>> > >>>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > >>>> --- > >>>> .../devicetree/bindings/display/msm/qcom,sm6125-mdss.yaml | 6 ------ > >>> > >>> This is not needed: it has already been corrected in v3 and v4 of the > >>> respective series (among other changes) and the patches were only picked > >>> to a preliminary (draft) pull to get an overview of the outstanding work > >>> for this subsystem. That branch happens to be included in regular -next > >>> releases though. > >>> > >>> 6.6 drm/msm display pull: https://gitlab.freedesktop.org/drm/msm/-/merge_requests/69 > >>> v3: https://lore.kernel.org/linux-arm-msm/20230718-sm6125-dpu-v3-0-6c5a56e99820@somainline.org/ > >>> v4: https://lore.kernel.org/linux-arm-msm/20230723-sm6125-dpu-v4-0-a3f287dd6c07@somainline.org/ > >> > >> What do you mean? The old code (one I am fixing) is in current next... > >> > >> If this was fixed, why next gets some outdated branches of drm next? > >> Each maintainers next tree is supposed to be fed into the next, without > >> delays. > >> > > > > Ah, I think I understood - some work in progress was applied to > > work-in-progress branch of drm/msm and this somehow got pushed to > > linux-next? How anyone is supposed to work on next branches if they are > > outdated or have stuff known to be incomplete? > > The drm/msm & bindings parts were considered final, but then I failed to > send 'applied' series for some reason. And then it was natural for > Marijn to send an updated revision. There were comments on some of the patches that would have an effect on the binding parts (including the examples). - Marijn
diff --git a/Documentation/devicetree/bindings/display/msm/qcom,sm6125-mdss.yaml b/Documentation/devicetree/bindings/display/msm/qcom,sm6125-mdss.yaml index 2525482424cb..479c82e6a0d8 100644 --- a/Documentation/devicetree/bindings/display/msm/qcom,sm6125-mdss.yaml +++ b/Documentation/devicetree/bindings/display/msm/qcom,sm6125-mdss.yaml @@ -95,8 +95,6 @@ examples: #size-cells = <1>; ranges; - status = "disabled"; - display-controller@5e01000 { compatible = "qcom,sm6125-dpu"; reg = <0x05e01000 0x83208>, @@ -170,8 +168,6 @@ examples: #address-cells = <1>; #size-cells = <0>; - status = "disabled"; - ports { #address-cells = <1>; #size-cells = <0>; @@ -210,8 +206,6 @@ examples: required-opps = <&rpmpd_opp_svs>; power-domains = <&rpmpd SM6125_VDDMX>; - - status = "disabled"; }; }; ...