* [PATCH] media: dt-bindings: Correct white-space style @ 2026-08-01 19:55 ` Krzysztof Kozlowski 2026-08-01 20:48 ` Bryan O'Donoghue 0 siblings, 1 reply; 2+ messages in thread From: Krzysztof Kozlowski @ 2026-08-01 19:55 UTC (permalink / raw) To: Keke Li, Mauro Carvalho Chehab, Rob Herring, Krzysztof Kozlowski, Conor Dooley, Zhi Mao, Tiffany Lin, Andrew-CT Chen, Yunfei Dong, Bin Liu, Vikash Garodia, Dikshita Agarwal, Bryan O'Donoghue, Jacopo Mondi, Raspberry Pi Kernel Maintenance, Florian Fainelli, Broadcom internal kernel review list, Matthias Brugger, AngeloGioacchino Del Regno, Xia Jiang, Stanimir Varbanov, linux-media, devicetree, linux-kernel, linux-arm-msm, linux-rpi-kernel, linux-arm-kernel, linux-mediatek Cc: Krzysztof Kozlowski Correct a few white-space issues, like double space after '=' or before bracket '{' characters, which will be flagged by dt-check-style. No functional changes. Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> --- .../bindings/media/amlogic,c3-mipi-csi2.yaml | 4 +- .../bindings/media/i2c/galaxycore,gc05a2.yaml | 2 +- .../media/mediatek,vcodec-encoder.yaml | 2 +- .../bindings/media/mediatek-jpeg-decoder.yaml | 4 +- .../bindings/media/mediatek-jpeg-encoder.yaml | 2 +- .../bindings/media/qcom,msm8996-venus.yaml | 40 +++++++++---------- .../bindings/media/raspberrypi,pispbe.yaml | 2 +- 7 files changed, 28 insertions(+), 28 deletions(-) diff --git a/Documentation/devicetree/bindings/media/amlogic,c3-mipi-csi2.yaml b/Documentation/devicetree/bindings/media/amlogic,c3-mipi-csi2.yaml index b0129beab0c3..2f11e5f45839 100644 --- a/Documentation/devicetree/bindings/media/amlogic,c3-mipi-csi2.yaml +++ b/Documentation/devicetree/bindings/media/amlogic,c3-mipi-csi2.yaml @@ -96,8 +96,8 @@ examples: <0x0 0xff01a000 0x0 0x100>; reg-names = "aphy", "dphy", "host"; power-domains = <&pwrc PWRC_C3_MIPI_ISP_WRAP_ID>; - clocks = <&clkc_periphs CLKID_VAPB>, - <&clkc_periphs CLKID_CSI_PHY0>; + clocks = <&clkc_periphs CLKID_VAPB>, + <&clkc_periphs CLKID_CSI_PHY0>; clock-names = "vapb", "phy0"; assigned-clocks = <&clkc_periphs CLKID_VAPB>, <&clkc_periphs CLKID_CSI_PHY0>; diff --git a/Documentation/devicetree/bindings/media/i2c/galaxycore,gc05a2.yaml b/Documentation/devicetree/bindings/media/i2c/galaxycore,gc05a2.yaml index 0e7a7b5ac89f..99d728c47cfb 100644 --- a/Documentation/devicetree/bindings/media/i2c/galaxycore,gc05a2.yaml +++ b/Documentation/devicetree/bindings/media/i2c/galaxycore,gc05a2.yaml @@ -88,7 +88,7 @@ examples: #size-cells = <0>; sensor@37 { - compatible = "galaxycore,gc05a2"; + compatible = "galaxycore,gc05a2"; reg = <0x37>; clocks = <&gc05a2_clk>; diff --git a/Documentation/devicetree/bindings/media/mediatek,vcodec-encoder.yaml b/Documentation/devicetree/bindings/media/mediatek,vcodec-encoder.yaml index 4505e66876a2..551e483f3e51 100644 --- a/Documentation/devicetree/bindings/media/mediatek,vcodec-encoder.yaml +++ b/Documentation/devicetree/bindings/media/mediatek,vcodec-encoder.yaml @@ -160,7 +160,7 @@ examples: vcodec_enc_vp8: vcodec@19002000 { compatible = "mediatek,mt8173-vcodec-enc-vp8"; - reg = <0x19002000 0x1000>; /* VENC_LT_SYS */ + reg = <0x19002000 0x1000>; /* VENC_LT_SYS */ interrupts = <GIC_SPI 202 IRQ_TYPE_LEVEL_LOW>; iommus = <&iommu M4U_PORT_VENC_RCPU_SET2>, <&iommu M4U_PORT_VENC_REC_FRM_SET2>, diff --git a/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.yaml b/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.yaml index a4aacd3eb189..76878050cfd9 100644 --- a/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.yaml +++ b/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.yaml @@ -72,8 +72,8 @@ examples: compatible = "mediatek,mt2701-jpgdec"; reg = <0x15004000 0x1000>; interrupts = <GIC_SPI 143 IRQ_TYPE_LEVEL_LOW>; - clocks = <&imgsys CLK_IMG_JPGDEC_SMI>, - <&imgsys CLK_IMG_JPGDEC>; + clocks = <&imgsys CLK_IMG_JPGDEC_SMI>, + <&imgsys CLK_IMG_JPGDEC>; clock-names = "jpgdec-smi", "jpgdec"; power-domains = <&scpsys MT2701_POWER_DOMAIN_ISP>; diff --git a/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml b/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml index 5b15f8977f67..3bc1ccb25893 100644 --- a/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml +++ b/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml @@ -67,7 +67,7 @@ examples: "mediatek,mtk-jpgenc"; reg = <0x1500a000 0x1000>; interrupts = <GIC_SPI 141 IRQ_TYPE_LEVEL_LOW>; - clocks = <&imgsys CLK_IMG_VENC>; + clocks = <&imgsys CLK_IMG_VENC>; clock-names = "jpgenc"; power-domains = <&scpsys MT2701_POWER_DOMAIN_ISP>; iommus = <&iommu MT2701_M4U_PORT_JPGENC_RDMA>, diff --git a/Documentation/devicetree/bindings/media/qcom,msm8996-venus.yaml b/Documentation/devicetree/bindings/media/qcom,msm8996-venus.yaml index 56c16458e3bb..389b545c9631 100644 --- a/Documentation/devicetree/bindings/media/qcom,msm8996-venus.yaml +++ b/Documentation/devicetree/bindings/media/qcom,msm8996-venus.yaml @@ -119,26 +119,26 @@ examples: <&mmcc VIDEO_MAXI_CLK>; clock-names = "core", "iface", "bus", "mbus"; power-domains = <&mmcc VENUS_GDSC>; - iommus = <&venus_smmu 0x00>, - <&venus_smmu 0x01>, - <&venus_smmu 0x0a>, - <&venus_smmu 0x07>, - <&venus_smmu 0x0e>, - <&venus_smmu 0x0f>, - <&venus_smmu 0x08>, - <&venus_smmu 0x09>, - <&venus_smmu 0x0b>, - <&venus_smmu 0x0c>, - <&venus_smmu 0x0d>, - <&venus_smmu 0x10>, - <&venus_smmu 0x11>, - <&venus_smmu 0x21>, - <&venus_smmu 0x28>, - <&venus_smmu 0x29>, - <&venus_smmu 0x2b>, - <&venus_smmu 0x2c>, - <&venus_smmu 0x2d>, - <&venus_smmu 0x31>; + iommus = <&venus_smmu 0x00>, + <&venus_smmu 0x01>, + <&venus_smmu 0x0a>, + <&venus_smmu 0x07>, + <&venus_smmu 0x0e>, + <&venus_smmu 0x0f>, + <&venus_smmu 0x08>, + <&venus_smmu 0x09>, + <&venus_smmu 0x0b>, + <&venus_smmu 0x0c>, + <&venus_smmu 0x0d>, + <&venus_smmu 0x10>, + <&venus_smmu 0x11>, + <&venus_smmu 0x21>, + <&venus_smmu 0x28>, + <&venus_smmu 0x29>, + <&venus_smmu 0x2b>, + <&venus_smmu 0x2c>, + <&venus_smmu 0x2d>, + <&venus_smmu 0x31>; memory-region = <&venus_mem>; video-decoder { diff --git a/Documentation/devicetree/bindings/media/raspberrypi,pispbe.yaml b/Documentation/devicetree/bindings/media/raspberrypi,pispbe.yaml index 1fc62a1d8eda..5c0f2f7b1d95 100644 --- a/Documentation/devicetree/bindings/media/raspberrypi,pispbe.yaml +++ b/Documentation/devicetree/bindings/media/raspberrypi,pispbe.yaml @@ -53,7 +53,7 @@ examples: #address-cells = <2>; #size-cells = <2>; - isp@880000 { + isp@880000 { compatible = "brcm,bcm2712-pispbe", "raspberrypi,pispbe"; reg = <0x10 0x00880000 0x0 0x4000>; interrupts = <GIC_SPI 72 IRQ_TYPE_LEVEL_HIGH>; -- 2.53.0 ^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] media: dt-bindings: Correct white-space style 2026-08-01 19:55 ` [PATCH] media: dt-bindings: Correct white-space style Krzysztof Kozlowski @ 2026-08-01 20:48 ` Bryan O'Donoghue 0 siblings, 0 replies; 2+ messages in thread From: Bryan O'Donoghue @ 2026-08-01 20:48 UTC (permalink / raw) To: Krzysztof Kozlowski, Keke Li, Mauro Carvalho Chehab, Rob Herring, Krzysztof Kozlowski, Conor Dooley, Zhi Mao, Tiffany Lin, Andrew-CT Chen, Yunfei Dong, Bin Liu, Vikash Garodia, Dikshita Agarwal, Jacopo Mondi, Raspberry Pi Kernel Maintenance, Florian Fainelli, Broadcom internal kernel review list, Matthias Brugger, AngeloGioacchino Del Regno, Xia Jiang, Stanimir Varbanov, linux-media, devicetree, linux-kernel, linux-arm-msm, linux-rpi-kernel, linux-arm-kernel, linux-mediatek On 01/08/2026 20:55, Krzysztof Kozlowski wrote: > Correct a few white-space issues, like double space after '=' or before > bracket '{' characters, which will be flagged by dt-check-style. No > functional changes. > > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com> > --- > .../bindings/media/amlogic,c3-mipi-csi2.yaml | 4 +- > .../bindings/media/i2c/galaxycore,gc05a2.yaml | 2 +- > .../media/mediatek,vcodec-encoder.yaml | 2 +- > .../bindings/media/mediatek-jpeg-decoder.yaml | 4 +- > .../bindings/media/mediatek-jpeg-encoder.yaml | 2 +- > .../bindings/media/qcom,msm8996-venus.yaml | 40 +++++++++---------- > .../bindings/media/raspberrypi,pispbe.yaml | 2 +- > 7 files changed, 28 insertions(+), 28 deletions(-) > > diff --git a/Documentation/devicetree/bindings/media/amlogic,c3-mipi-csi2.yaml b/Documentation/devicetree/bindings/media/amlogic,c3-mipi-csi2.yaml > index b0129beab0c3..2f11e5f45839 100644 > --- a/Documentation/devicetree/bindings/media/amlogic,c3-mipi-csi2.yaml > +++ b/Documentation/devicetree/bindings/media/amlogic,c3-mipi-csi2.yaml > @@ -96,8 +96,8 @@ examples: > <0x0 0xff01a000 0x0 0x100>; > reg-names = "aphy", "dphy", "host"; > power-domains = <&pwrc PWRC_C3_MIPI_ISP_WRAP_ID>; > - clocks = <&clkc_periphs CLKID_VAPB>, > - <&clkc_periphs CLKID_CSI_PHY0>; > + clocks = <&clkc_periphs CLKID_VAPB>, > + <&clkc_periphs CLKID_CSI_PHY0>; > clock-names = "vapb", "phy0"; > assigned-clocks = <&clkc_periphs CLKID_VAPB>, > <&clkc_periphs CLKID_CSI_PHY0>; > diff --git a/Documentation/devicetree/bindings/media/i2c/galaxycore,gc05a2.yaml b/Documentation/devicetree/bindings/media/i2c/galaxycore,gc05a2.yaml > index 0e7a7b5ac89f..99d728c47cfb 100644 > --- a/Documentation/devicetree/bindings/media/i2c/galaxycore,gc05a2.yaml > +++ b/Documentation/devicetree/bindings/media/i2c/galaxycore,gc05a2.yaml > @@ -88,7 +88,7 @@ examples: > #size-cells = <0>; > > sensor@37 { > - compatible = "galaxycore,gc05a2"; > + compatible = "galaxycore,gc05a2"; > reg = <0x37>; > > clocks = <&gc05a2_clk>; > diff --git a/Documentation/devicetree/bindings/media/mediatek,vcodec-encoder.yaml b/Documentation/devicetree/bindings/media/mediatek,vcodec-encoder.yaml > index 4505e66876a2..551e483f3e51 100644 > --- a/Documentation/devicetree/bindings/media/mediatek,vcodec-encoder.yaml > +++ b/Documentation/devicetree/bindings/media/mediatek,vcodec-encoder.yaml > @@ -160,7 +160,7 @@ examples: > > vcodec_enc_vp8: vcodec@19002000 { > compatible = "mediatek,mt8173-vcodec-enc-vp8"; > - reg = <0x19002000 0x1000>; /* VENC_LT_SYS */ > + reg = <0x19002000 0x1000>; /* VENC_LT_SYS */ > interrupts = <GIC_SPI 202 IRQ_TYPE_LEVEL_LOW>; > iommus = <&iommu M4U_PORT_VENC_RCPU_SET2>, > <&iommu M4U_PORT_VENC_REC_FRM_SET2>, > diff --git a/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.yaml b/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.yaml > index a4aacd3eb189..76878050cfd9 100644 > --- a/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.yaml > +++ b/Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.yaml > @@ -72,8 +72,8 @@ examples: > compatible = "mediatek,mt2701-jpgdec"; > reg = <0x15004000 0x1000>; > interrupts = <GIC_SPI 143 IRQ_TYPE_LEVEL_LOW>; > - clocks = <&imgsys CLK_IMG_JPGDEC_SMI>, > - <&imgsys CLK_IMG_JPGDEC>; > + clocks = <&imgsys CLK_IMG_JPGDEC_SMI>, > + <&imgsys CLK_IMG_JPGDEC>; > clock-names = "jpgdec-smi", > "jpgdec"; > power-domains = <&scpsys MT2701_POWER_DOMAIN_ISP>; > diff --git a/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml b/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml > index 5b15f8977f67..3bc1ccb25893 100644 > --- a/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml > +++ b/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml > @@ -67,7 +67,7 @@ examples: > "mediatek,mtk-jpgenc"; > reg = <0x1500a000 0x1000>; > interrupts = <GIC_SPI 141 IRQ_TYPE_LEVEL_LOW>; > - clocks = <&imgsys CLK_IMG_VENC>; > + clocks = <&imgsys CLK_IMG_VENC>; > clock-names = "jpgenc"; > power-domains = <&scpsys MT2701_POWER_DOMAIN_ISP>; > iommus = <&iommu MT2701_M4U_PORT_JPGENC_RDMA>, > diff --git a/Documentation/devicetree/bindings/media/qcom,msm8996-venus.yaml b/Documentation/devicetree/bindings/media/qcom,msm8996-venus.yaml > index 56c16458e3bb..389b545c9631 100644 > --- a/Documentation/devicetree/bindings/media/qcom,msm8996-venus.yaml > +++ b/Documentation/devicetree/bindings/media/qcom,msm8996-venus.yaml > @@ -119,26 +119,26 @@ examples: > <&mmcc VIDEO_MAXI_CLK>; > clock-names = "core", "iface", "bus", "mbus"; > power-domains = <&mmcc VENUS_GDSC>; > - iommus = <&venus_smmu 0x00>, > - <&venus_smmu 0x01>, > - <&venus_smmu 0x0a>, > - <&venus_smmu 0x07>, > - <&venus_smmu 0x0e>, > - <&venus_smmu 0x0f>, > - <&venus_smmu 0x08>, > - <&venus_smmu 0x09>, > - <&venus_smmu 0x0b>, > - <&venus_smmu 0x0c>, > - <&venus_smmu 0x0d>, > - <&venus_smmu 0x10>, > - <&venus_smmu 0x11>, > - <&venus_smmu 0x21>, > - <&venus_smmu 0x28>, > - <&venus_smmu 0x29>, > - <&venus_smmu 0x2b>, > - <&venus_smmu 0x2c>, > - <&venus_smmu 0x2d>, > - <&venus_smmu 0x31>; > + iommus = <&venus_smmu 0x00>, > + <&venus_smmu 0x01>, > + <&venus_smmu 0x0a>, > + <&venus_smmu 0x07>, > + <&venus_smmu 0x0e>, > + <&venus_smmu 0x0f>, > + <&venus_smmu 0x08>, > + <&venus_smmu 0x09>, > + <&venus_smmu 0x0b>, > + <&venus_smmu 0x0c>, > + <&venus_smmu 0x0d>, > + <&venus_smmu 0x10>, > + <&venus_smmu 0x11>, > + <&venus_smmu 0x21>, > + <&venus_smmu 0x28>, > + <&venus_smmu 0x29>, > + <&venus_smmu 0x2b>, > + <&venus_smmu 0x2c>, > + <&venus_smmu 0x2d>, > + <&venus_smmu 0x31>; > memory-region = <&venus_mem>; > > video-decoder { > diff --git a/Documentation/devicetree/bindings/media/raspberrypi,pispbe.yaml b/Documentation/devicetree/bindings/media/raspberrypi,pispbe.yaml > index 1fc62a1d8eda..5c0f2f7b1d95 100644 > --- a/Documentation/devicetree/bindings/media/raspberrypi,pispbe.yaml > +++ b/Documentation/devicetree/bindings/media/raspberrypi,pispbe.yaml > @@ -53,7 +53,7 @@ examples: > #address-cells = <2>; > #size-cells = <2>; > > - isp@880000 { > + isp@880000 { > compatible = "brcm,bcm2712-pispbe", "raspberrypi,pispbe"; > reg = <0x10 0x00880000 0x0 0x4000>; > interrupts = <GIC_SPI 72 IRQ_TYPE_LEVEL_HIGH>; > -- > 2.53.0 > Reviewed-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-08-01 20:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <xIYnc9B56o8xe8HvsOwmdoaAjF_TthVpVNEnPsR7e_zn2SvMHejEb9bzZ6XHny3bojqzBWOX2ic2MV9laa5osQ==@protonmail.internalid>
2026-08-01 19:55 ` [PATCH] media: dt-bindings: Correct white-space style Krzysztof Kozlowski
2026-08-01 20:48 ` Bryan O'Donoghue
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox