* [RESEND PATCH v4 0/3] Convert adi,adv7511.txt DT bindings to yaml @ 2021-06-15 13:13 ` Ricardo Cañuelo 0 siblings, 0 replies; 16+ messages in thread From: Ricardo Cañuelo @ 2021-06-15 13:13 UTC (permalink / raw) To: airlied, daniel, michal.simek, alexandre.torgue, laurent.pinchart Cc: kernel, devicetree, linux-arm-kernel, robh+dt, xuwei5, mcoquelin.stm32, marex Hi all, I'm rescuing and resending this patch series again, as it got reviewed but parts of it didn't make it to mainline. The previous version can be found in https://lore.kernel.org/linux-devicetree/20200601063308.13045-1-ricardo.canuelo@collabora.com/ This series convert the adi,adv7511.txt DT bindings to json-schema. As a result of the conversion some dts files needed to be updated. The changes to the dts files are of three types: - Reordering of the I2C slave addresses list of the ADV75xx node. The addresses in the 'reg' property and the matching names in 'reg-names' for an I2C slave don't need to be in any particular order, but the DT schema defines these properties as a cell array and a string array respectively, which are ordered, so the definitions in the dts files must match the order in the binding. - Filling the minimum binding requirements. Most of the time this means creating a 'ports' node in the boards that don't define them. Note, however, that the purpose of this is simply to make the definition compliant with the binding. I didn't define any endpoints for the ports. - Removing unneeded properties. About the binding conversion: - The original binding covered five different devices: ADV7511, ADV7511W, ADV7513, ADV7533 and ADV7535. They all share a common set of properties but ADV7533 and ADV7535 have enough differences from the rest to warrant their own binding file. In v1 I modelled all the properties constraints for all five devices in a single file but it turned out a bit too complex. Splitting the binding into one for ADV7511/11W/13 and another for ADV7533/35 makes them much easier to read and maintain. Patches 1/4 to 3/4 contain the dts changes. Patch 4/4 contains the binding conversion. NOTE: the bindings have been tested with: make dt_binding_check ARCH=<arch> DT_SCHEMA_FILES=<...adi,adv7511.yaml> make dt_binding_check ARCH=<arch> DT_SCHEMA_FILES=<...adi,adv7533.yaml> make dtbs_check ARCH=<arch> DT_SCHEMA_FILES=<...adi,adv7511.yaml> make dtbs_check ARCH=<arch> DT_SCHEMA_FILES=<...adi,adv7533.yaml> for <arch> = arm and arm64. dts changes haven't been tested in hardware. Some existing DTs are expected to fail after this conversion. Changes in v4: - Removed from the patch series (already in mainline): - arm64: dts: hisilicon: hikey: fixes to comply with adi,adv7533 DT binding. - Update binding examples to comply with the current schema checks. - Update the license in the binding files. Ricardo Cañuelo (3): ARM: dts: zynq: add port definitions to hdmi-tx@39 ARM: dts: stm32: make hdmi-transmitter node compliant with DT bindings dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml .../bindings/display/bridge/adi,adv7511.txt | 143 ----------- .../bindings/display/bridge/adi,adv7511.yaml | 241 ++++++++++++++++++ .../bindings/display/bridge/adi,adv7533.yaml | 184 +++++++++++++ .../boot/dts/stm32mp15xx-dhcor-avenger96.dtsi | 6 +- arch/arm/boot/dts/zynq-zc702.dts | 10 + arch/arm/boot/dts/zynq-zc706.dts | 10 + 6 files changed, 447 insertions(+), 147 deletions(-) delete mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt create mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7533.yaml -- 2.25.1 ^ permalink raw reply [flat|nested] 16+ messages in thread
* [RESEND PATCH v4 0/3] Convert adi,adv7511.txt DT bindings to yaml @ 2021-06-15 13:13 ` Ricardo Cañuelo 0 siblings, 0 replies; 16+ messages in thread From: Ricardo Cañuelo @ 2021-06-15 13:13 UTC (permalink / raw) To: airlied, daniel, michal.simek, alexandre.torgue, laurent.pinchart Cc: kernel, devicetree, linux-arm-kernel, robh+dt, xuwei5, mcoquelin.stm32, marex Hi all, I'm rescuing and resending this patch series again, as it got reviewed but parts of it didn't make it to mainline. The previous version can be found in https://lore.kernel.org/linux-devicetree/20200601063308.13045-1-ricardo.canuelo@collabora.com/ This series convert the adi,adv7511.txt DT bindings to json-schema. As a result of the conversion some dts files needed to be updated. The changes to the dts files are of three types: - Reordering of the I2C slave addresses list of the ADV75xx node. The addresses in the 'reg' property and the matching names in 'reg-names' for an I2C slave don't need to be in any particular order, but the DT schema defines these properties as a cell array and a string array respectively, which are ordered, so the definitions in the dts files must match the order in the binding. - Filling the minimum binding requirements. Most of the time this means creating a 'ports' node in the boards that don't define them. Note, however, that the purpose of this is simply to make the definition compliant with the binding. I didn't define any endpoints for the ports. - Removing unneeded properties. About the binding conversion: - The original binding covered five different devices: ADV7511, ADV7511W, ADV7513, ADV7533 and ADV7535. They all share a common set of properties but ADV7533 and ADV7535 have enough differences from the rest to warrant their own binding file. In v1 I modelled all the properties constraints for all five devices in a single file but it turned out a bit too complex. Splitting the binding into one for ADV7511/11W/13 and another for ADV7533/35 makes them much easier to read and maintain. Patches 1/4 to 3/4 contain the dts changes. Patch 4/4 contains the binding conversion. NOTE: the bindings have been tested with: make dt_binding_check ARCH=<arch> DT_SCHEMA_FILES=<...adi,adv7511.yaml> make dt_binding_check ARCH=<arch> DT_SCHEMA_FILES=<...adi,adv7533.yaml> make dtbs_check ARCH=<arch> DT_SCHEMA_FILES=<...adi,adv7511.yaml> make dtbs_check ARCH=<arch> DT_SCHEMA_FILES=<...adi,adv7533.yaml> for <arch> = arm and arm64. dts changes haven't been tested in hardware. Some existing DTs are expected to fail after this conversion. Changes in v4: - Removed from the patch series (already in mainline): - arm64: dts: hisilicon: hikey: fixes to comply with adi,adv7533 DT binding. - Update binding examples to comply with the current schema checks. - Update the license in the binding files. Ricardo Cañuelo (3): ARM: dts: zynq: add port definitions to hdmi-tx@39 ARM: dts: stm32: make hdmi-transmitter node compliant with DT bindings dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml .../bindings/display/bridge/adi,adv7511.txt | 143 ----------- .../bindings/display/bridge/adi,adv7511.yaml | 241 ++++++++++++++++++ .../bindings/display/bridge/adi,adv7533.yaml | 184 +++++++++++++ .../boot/dts/stm32mp15xx-dhcor-avenger96.dtsi | 6 +- arch/arm/boot/dts/zynq-zc702.dts | 10 + arch/arm/boot/dts/zynq-zc706.dts | 10 + 6 files changed, 447 insertions(+), 147 deletions(-) delete mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt create mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7533.yaml -- 2.25.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* [RESEND PATCH v4 1/3] ARM: dts: zynq: add port definitions to hdmi-tx@39 2021-06-15 13:13 ` Ricardo Cañuelo @ 2021-06-15 13:13 ` Ricardo Cañuelo -1 siblings, 0 replies; 16+ messages in thread From: Ricardo Cañuelo @ 2021-06-15 13:13 UTC (permalink / raw) To: airlied, daniel, michal.simek, alexandre.torgue, laurent.pinchart Cc: kernel, devicetree, linux-arm-kernel, robh+dt, xuwei5, mcoquelin.stm32, marex Define a 'ports' node for 'adv7511: hdmi-tx@39' to make it compliant with the adi,adv7511 DT binding. This fills the minimum requirements to meet the binding requirements, remote endpoints are not defined. Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Acked-by: Michal Simek <michal.simek@xilinx.com> --- Michal, this was already reviewed and acked a long time ago but it never made it into mainline. Can you take a look at it? Thanks. arch/arm/boot/dts/zynq-zc702.dts | 10 ++++++++++ arch/arm/boot/dts/zynq-zc706.dts | 10 ++++++++++ 2 files changed, 20 insertions(+) diff --git a/arch/arm/boot/dts/zynq-zc702.dts b/arch/arm/boot/dts/zynq-zc702.dts index cf70aff26c66..13b8ff1bced3 100644 --- a/arch/arm/boot/dts/zynq-zc702.dts +++ b/arch/arm/boot/dts/zynq-zc702.dts @@ -141,6 +141,16 @@ adv7511: hdmi-tx@39 { adi,input-clock = "1x"; adi,input-style = <3>; adi,input-justification = "right"; + ports { + #address-cells = <1>; + #size-cells = <0>; + port@0 { + reg = <0>; + }; + port@1 { + reg = <1>; + }; + }; }; }; diff --git a/arch/arm/boot/dts/zynq-zc706.dts b/arch/arm/boot/dts/zynq-zc706.dts index 77943c16d33f..99fa51ba6e93 100644 --- a/arch/arm/boot/dts/zynq-zc706.dts +++ b/arch/arm/boot/dts/zynq-zc706.dts @@ -93,6 +93,16 @@ adv7511: hdmi-tx@39 { adi,input-clock = "1x"; adi,input-style = <3>; adi,input-justification = "evenly"; + ports { + #address-cells = <1>; + #size-cells = <0>; + port@0 { + reg = <0>; + }; + port@1 { + reg = <1>; + }; + }; }; }; -- 2.25.1 ^ permalink raw reply related [flat|nested] 16+ messages in thread
* [RESEND PATCH v4 1/3] ARM: dts: zynq: add port definitions to hdmi-tx@39 @ 2021-06-15 13:13 ` Ricardo Cañuelo 0 siblings, 0 replies; 16+ messages in thread From: Ricardo Cañuelo @ 2021-06-15 13:13 UTC (permalink / raw) To: airlied, daniel, michal.simek, alexandre.torgue, laurent.pinchart Cc: kernel, devicetree, linux-arm-kernel, robh+dt, xuwei5, mcoquelin.stm32, marex Define a 'ports' node for 'adv7511: hdmi-tx@39' to make it compliant with the adi,adv7511 DT binding. This fills the minimum requirements to meet the binding requirements, remote endpoints are not defined. Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Acked-by: Michal Simek <michal.simek@xilinx.com> --- Michal, this was already reviewed and acked a long time ago but it never made it into mainline. Can you take a look at it? Thanks. arch/arm/boot/dts/zynq-zc702.dts | 10 ++++++++++ arch/arm/boot/dts/zynq-zc706.dts | 10 ++++++++++ 2 files changed, 20 insertions(+) diff --git a/arch/arm/boot/dts/zynq-zc702.dts b/arch/arm/boot/dts/zynq-zc702.dts index cf70aff26c66..13b8ff1bced3 100644 --- a/arch/arm/boot/dts/zynq-zc702.dts +++ b/arch/arm/boot/dts/zynq-zc702.dts @@ -141,6 +141,16 @@ adv7511: hdmi-tx@39 { adi,input-clock = "1x"; adi,input-style = <3>; adi,input-justification = "right"; + ports { + #address-cells = <1>; + #size-cells = <0>; + port@0 { + reg = <0>; + }; + port@1 { + reg = <1>; + }; + }; }; }; diff --git a/arch/arm/boot/dts/zynq-zc706.dts b/arch/arm/boot/dts/zynq-zc706.dts index 77943c16d33f..99fa51ba6e93 100644 --- a/arch/arm/boot/dts/zynq-zc706.dts +++ b/arch/arm/boot/dts/zynq-zc706.dts @@ -93,6 +93,16 @@ adv7511: hdmi-tx@39 { adi,input-clock = "1x"; adi,input-style = <3>; adi,input-justification = "evenly"; + ports { + #address-cells = <1>; + #size-cells = <0>; + port@0 { + reg = <0>; + }; + port@1 { + reg = <1>; + }; + }; }; }; -- 2.25.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply related [flat|nested] 16+ messages in thread
* [RESEND PATCH v4 2/3] ARM: dts: stm32: make hdmi-transmitter node compliant with DT bindings 2021-06-15 13:13 ` Ricardo Cañuelo @ 2021-06-15 13:13 ` Ricardo Cañuelo -1 siblings, 0 replies; 16+ messages in thread From: Ricardo Cañuelo @ 2021-06-15 13:13 UTC (permalink / raw) To: airlied, daniel, michal.simek, alexandre.torgue, laurent.pinchart Cc: kernel, devicetree, linux-arm-kernel, robh+dt, xuwei5, mcoquelin.stm32, marex Reorder the I2C slave addresses of the hdmi-transmitter node and remove the adi,input-style and adi,input-justification properties to meet the adi,adv7513 binding requirements. Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> --- arch/arm/boot/dts/stm32mp15xx-dhcor-avenger96.dtsi | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/arch/arm/boot/dts/stm32mp15xx-dhcor-avenger96.dtsi b/arch/arm/boot/dts/stm32mp15xx-dhcor-avenger96.dtsi index 64dca5b7f748..7d7b002e7d6c 100644 --- a/arch/arm/boot/dts/stm32mp15xx-dhcor-avenger96.dtsi +++ b/arch/arm/boot/dts/stm32mp15xx-dhcor-avenger96.dtsi @@ -220,8 +220,8 @@ &i2c2 { /* X6 I2C2 */ &i2c4 { hdmi-transmitter@3d { compatible = "adi,adv7513"; - reg = <0x3d>, <0x2d>, <0x4d>, <0x5d>; - reg-names = "main", "cec", "edid", "packet"; + reg = <0x3d>, <0x4d>, <0x2d> , <0x5d>; + reg-names = "main", "edid", "cec", "packet"; clocks = <&cec_clock>; clock-names = "cec"; @@ -239,8 +239,6 @@ hdmi-transmitter@3d { adi,input-depth = <8>; adi,input-colorspace = "rgb"; adi,input-clock = "1x"; - adi,input-style = <1>; - adi,input-justification = "evenly"; ports { #address-cells = <1>; -- 2.25.1 ^ permalink raw reply related [flat|nested] 16+ messages in thread
* [RESEND PATCH v4 2/3] ARM: dts: stm32: make hdmi-transmitter node compliant with DT bindings @ 2021-06-15 13:13 ` Ricardo Cañuelo 0 siblings, 0 replies; 16+ messages in thread From: Ricardo Cañuelo @ 2021-06-15 13:13 UTC (permalink / raw) To: airlied, daniel, michal.simek, alexandre.torgue, laurent.pinchart Cc: kernel, devicetree, linux-arm-kernel, robh+dt, xuwei5, mcoquelin.stm32, marex Reorder the I2C slave addresses of the hdmi-transmitter node and remove the adi,input-style and adi,input-justification properties to meet the adi,adv7513 binding requirements. Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> --- arch/arm/boot/dts/stm32mp15xx-dhcor-avenger96.dtsi | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/arch/arm/boot/dts/stm32mp15xx-dhcor-avenger96.dtsi b/arch/arm/boot/dts/stm32mp15xx-dhcor-avenger96.dtsi index 64dca5b7f748..7d7b002e7d6c 100644 --- a/arch/arm/boot/dts/stm32mp15xx-dhcor-avenger96.dtsi +++ b/arch/arm/boot/dts/stm32mp15xx-dhcor-avenger96.dtsi @@ -220,8 +220,8 @@ &i2c2 { /* X6 I2C2 */ &i2c4 { hdmi-transmitter@3d { compatible = "adi,adv7513"; - reg = <0x3d>, <0x2d>, <0x4d>, <0x5d>; - reg-names = "main", "cec", "edid", "packet"; + reg = <0x3d>, <0x4d>, <0x2d> , <0x5d>; + reg-names = "main", "edid", "cec", "packet"; clocks = <&cec_clock>; clock-names = "cec"; @@ -239,8 +239,6 @@ hdmi-transmitter@3d { adi,input-depth = <8>; adi,input-colorspace = "rgb"; adi,input-clock = "1x"; - adi,input-style = <1>; - adi,input-justification = "evenly"; ports { #address-cells = <1>; -- 2.25.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply related [flat|nested] 16+ messages in thread
* [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml 2021-06-15 13:13 ` Ricardo Cañuelo @ 2021-06-15 13:13 ` Ricardo Cañuelo -1 siblings, 0 replies; 16+ messages in thread From: Ricardo Cañuelo @ 2021-06-15 13:13 UTC (permalink / raw) To: airlied, daniel, michal.simek, alexandre.torgue, laurent.pinchart Cc: kernel, devicetree, linux-arm-kernel, robh+dt, xuwei5, mcoquelin.stm32, marex Convert the ADV7511/11w/13/33/35 DT bindings to json-schema. The original binding has been split into two files: adi,adv7511.yaml for ADV7511/11W/13 and adi,adv7533.yaml for ADV7533/35. Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com> Reviewed-by: Rob Herring <robh@kernel.org> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> --- .../bindings/display/bridge/adi,adv7511.txt | 143 ----------- .../bindings/display/bridge/adi,adv7511.yaml | 241 ++++++++++++++++++ .../bindings/display/bridge/adi,adv7533.yaml | 184 +++++++++++++ 3 files changed, 425 insertions(+), 143 deletions(-) delete mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt create mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7533.yaml diff --git a/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt deleted file mode 100644 index 659523f538bf..000000000000 --- a/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt +++ /dev/null @@ -1,143 +0,0 @@ -Analog Devices ADV7511(W)/13/33/35 HDMI Encoders ------------------------------------------------- - -The ADV7511, ADV7511W, ADV7513, ADV7533 and ADV7535 are HDMI audio and video -transmitters compatible with HDMI 1.4 and DVI 1.0. They support color space -conversion, S/PDIF, CEC and HDCP. ADV7533/5 supports the DSI interface for input -pixels, while the others support RGB interface. - -Required properties: - -- compatible: Should be one of: - "adi,adv7511" - "adi,adv7511w" - "adi,adv7513" - "adi,adv7533" - "adi,adv7535" - -- reg: I2C slave addresses - The ADV7511 internal registers are split into four pages exposed through - different I2C addresses, creating four register maps. Each map has it own - I2C address and acts as a standard slave device on the I2C bus. The main - address is mandatory, others are optional and revert to defaults if not - specified. - - -The ADV7511 supports a large number of input data formats that differ by their -color depth, color format, clock mode, bit justification and random -arrangement of components on the data bus. The combination of the following -properties describe the input and map directly to the video input tables of the -ADV7511 datasheet that document all the supported combinations. - -- adi,input-depth: Number of bits per color component at the input (8, 10 or - 12). -- adi,input-colorspace: The input color space, one of "rgb", "yuv422" or - "yuv444". -- adi,input-clock: The input clock type, one of "1x" (one clock cycle per - pixel), "2x" (two clock cycles per pixel), "ddr" (one clock cycle per pixel, - data driven on both edges). - -The following input format properties are required except in "rgb 1x" and -"yuv444 1x" modes, in which case they must not be specified. - -- adi,input-style: The input components arrangement variant (1, 2 or 3), as - listed in the input format tables in the datasheet. -- adi,input-justification: The input bit justification ("left", "evenly", - "right"). - -- avdd-supply: A 1.8V supply that powers up the AVDD pin on the chip. -- dvdd-supply: A 1.8V supply that powers up the DVDD pin on the chip. -- pvdd-supply: A 1.8V supply that powers up the PVDD pin on the chip. -- dvdd-3v-supply: A 3.3V supply that powers up the pin called DVDD_3V - on the chip. -- bgvdd-supply: A 1.8V supply that powers up the BGVDD pin. This is - needed only for ADV7511. - -The following properties are required for ADV7533 and ADV7535: - -- adi,dsi-lanes: Number of DSI data lanes connected to the DSI host. It should - be one of 1, 2, 3 or 4. -- a2vdd-supply: 1.8V supply that powers up the A2VDD pin on the chip. -- v3p3-supply: A 3.3V supply that powers up the V3P3 pin on the chip. -- v1p2-supply: A supply that powers up the V1P2 pin on the chip. It can be - either 1.2V or 1.8V for ADV7533 but only 1.8V for ADV7535. - -Optional properties: - -- interrupts: Specifier for the ADV7511 interrupt -- pd-gpios: Specifier for the GPIO connected to the power down signal - -- adi,clock-delay: Video data clock delay relative to the pixel clock, in ps - (-1200 ps .. 1600 ps). Defaults to no delay. -- adi,embedded-sync: The input uses synchronization signals embedded in the - data stream (similar to BT.656). Defaults to separate H/V synchronization - signals. -- adi,disable-timing-generator: Only for ADV7533 and ADV7535. Disables the - internal timing generator. The chip will rely on the sync signals in the - DSI data lanes, rather than generate its own timings for HDMI output. -- clocks: from common clock binding: reference to the CEC clock. -- clock-names: from common clock binding: must be "cec". -- reg-names : Names of maps with programmable addresses. - It can contain any map needing a non-default address. - Possible maps names are : "main", "edid", "cec", "packet" - -Required nodes: - -The ADV7511 has two video ports. Their connections are modelled using the OF -graph bindings specified in Documentation/devicetree/bindings/graph.txt. - -- Video port 0 for the RGB, YUV or DSI input. In the case of ADV7533/5, the - remote endpoint phandle should be a reference to a valid mipi_dsi_host device - node. -- Video port 1 for the HDMI output -- Audio port 2 for the HDMI audio input - - -Example -------- - - adv7511w: hdmi@39 { - compatible = "adi,adv7511w"; - /* - * The EDID page will be accessible on address 0x66 on the I2C - * bus. All other maps continue to use their default addresses. - */ - reg = <0x39>, <0x66>; - reg-names = "main", "edid"; - interrupt-parent = <&gpio3>; - interrupts = <29 IRQ_TYPE_EDGE_FALLING>; - clocks = <&cec_clock>; - clock-names = "cec"; - - adi,input-depth = <8>; - adi,input-colorspace = "rgb"; - adi,input-clock = "1x"; - adi,input-style = <1>; - adi,input-justification = "evenly"; - - ports { - #address-cells = <1>; - #size-cells = <0>; - - port@0 { - reg = <0>; - adv7511w_in: endpoint { - remote-endpoint = <&dpi_out>; - }; - }; - - port@1 { - reg = <1>; - adv7511_out: endpoint { - remote-endpoint = <&hdmi_connector_in>; - }; - }; - - port@2 { - reg = <2>; - codec_endpoint: endpoint { - remote-endpoint = <&i2s0_cpu_endpoint>; - }; - }; - }; - }; diff --git a/Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml new file mode 100644 index 000000000000..87f485ee2fb5 --- /dev/null +++ b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml @@ -0,0 +1,241 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/display/bridge/adi,adv7511.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Analog Devices ADV7511/11W/13 HDMI Encoders + +maintainers: + - Laurent Pinchart <laurent.pinchart@ideasonboard.com> + +description: | + The ADV7511, ADV7511W and ADV7513 are HDMI audio and video + transmitters compatible with HDMI 1.4 and DVI 1.0. They support color + space conversion, S/PDIF, CEC and HDCP. The transmitter input is + parallel RGB or YUV data. + +properties: + compatible: + enum: + - adi,adv7511 + - adi,adv7511w + - adi,adv7513 + + reg: + description: | + I2C slave addresses. + + The ADV7511/11W/13 internal registers are split into four pages + exposed through different I2C addresses, creating four register + maps. Each map has it own I2C address and acts as a standard slave + device on the I2C bus. The main address is mandatory, others are + optional and revert to defaults if not specified. + minItems: 1 + maxItems: 4 + + reg-names: + description: + Names of maps with programmable addresses. It can contain any map + needing a non-default address. + minItems: 1 + maxItems: 4 + items: + - const: main + - const: edid + - const: cec + - const: packet + + clocks: + description: Reference to the CEC clock. + maxItems: 1 + + clock-names: + const: cec + + interrupts: + maxItems: 1 + + pd-gpios: + description: GPIO connected to the power down signal. + maxItems: 1 + + avdd-supply: + description: A 1.8V supply that powers up the AVDD pin. + + dvdd-supply: + description: A 1.8V supply that powers up the DVDD pin. + + pvdd-supply: + description: A 1.8V supply that powers up the PVDD pin. + + dvdd-3v-supply: + description: A 3.3V supply that powers up the DVDD_3V pin. + + bgvdd-supply: + description: A 1.8V supply that powers up the BGVDD pin. + + adi,input-depth: + description: Number of bits per color component at the input. + allOf: + - $ref: /schemas/types.yaml#/definitions/uint32 + - enum: [ 8, 10, 12 ] + + adi,input-colorspace: + description: Input color space. + enum: [ rgb, yuv422, yuv444 ] + + adi,input-clock: + description: | + Input clock type. + "1x": one clock cycle per pixel + "2x": two clock cycles per pixel + "dd": one clock cycle per pixel, data driven on both edges + enum: [ 1x, 2x, dd ] + + adi,clock-delay: + description: + Video data clock delay relative to the pixel clock, in ps + (-1200ps .. 1600 ps). + $ref: /schemas/types.yaml#/definitions/uint32 + default: 0 + + adi,embedded-sync: + description: + If defined, the input uses synchronization signals embedded in the + data stream (similar to BT.656). + type: boolean + + adi,input-style: + description: + Input components arrangement variant as listed in the input + format tables in the datasheet. + $ref: /schemas/types.yaml#/definitions/uint32 + enum: [ 1, 2, 3 ] + + adi,input-justification: + description: Input bit justification. + enum: [ left, evenly, right ] + + ports: + description: + The ADV7511(W)/13 has two video ports and one audio port. This node + models their connections as documented in + Documentation/devicetree/bindings/media/video-interfaces.txt + Documentation/devicetree/bindings/graph.txt + type: object + properties: + port@0: + description: Video port for the RGB or YUV input. + type: object + + port@1: + description: Video port for the HDMI output. + type: object + + port@2: + description: Audio port for the HDMI output. + type: object + +# adi,input-colorspace and adi,input-clock are required except in +# "rgb 1x" and "yuv444 1x" modes, in which case they must not be +# specified. +if: + not: + properties: + adi,input-colorspace: + contains: + enum: [ rgb, yuv444 ] + adi,input-clock: + contains: + const: 1x + +then: + required: + - adi,input-style + - adi,input-justification + +else: + properties: + adi,input-style: false + adi,input-justification: false + + +required: + - compatible + - reg + - ports + - adi,input-depth + - adi,input-colorspace + - adi,input-clock + - avdd-supply + - dvdd-supply + - pvdd-supply + - dvdd-3v-supply + - bgvdd-supply + +additionalProperties: false + +examples: + - | + #include <dt-bindings/interrupt-controller/irq.h> + + i2c@e6500000 { + #address-cells = <1>; + #size-cells = <0>; + + reg = <0 0xe6500000>; + + adv7511w: hdmi@39 { + compatible = "adi,adv7511w"; + /* + * The EDID page will be accessible on address 0x66 on the I2C + * bus. All other maps continue to use their default addresses. + */ + reg = <0x39>, <0x66>; + reg-names = "main", "edid"; + interrupt-parent = <&gpio3>; + interrupts = <29 IRQ_TYPE_EDGE_FALLING>; + clocks = <&cec_clock>; + clock-names = "cec"; + avdd-supply = <&v1v8>; + dvdd-supply = <&v1v8>; + pvdd-supply = <&v1v8>; + dvdd-3v-supply = <&v3v3>; + bgvdd-supply = <&v1v8>; + + adi,input-depth = <8>; + adi,input-colorspace = "yuv422"; + adi,input-clock = "1x"; + + adi,input-style = <3>; + adi,input-justification = "right"; + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + reg = <0>; + adv7511w_in: endpoint { + remote-endpoint = <&dpi_out>; + }; + }; + + port@1 { + reg = <1>; + adv7511_out: endpoint { + remote-endpoint = <&hdmi_connector_in>; + }; + }; + + port@2 { + reg = <2>; + codec_endpoint: endpoint { + remote-endpoint = <&i2s0_cpu_endpoint>; + }; + }; + }; + }; + }; + +... diff --git a/Documentation/devicetree/bindings/display/bridge/adi,adv7533.yaml b/Documentation/devicetree/bindings/display/bridge/adi,adv7533.yaml new file mode 100644 index 000000000000..f36209137c8a --- /dev/null +++ b/Documentation/devicetree/bindings/display/bridge/adi,adv7533.yaml @@ -0,0 +1,184 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/display/bridge/adi,adv7533.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Analog Devices ADV7533/35 HDMI Encoders + +maintainers: + - Laurent Pinchart <laurent.pinchart@ideasonboard.com> + +description: | + The ADV7533 and ADV7535 are HDMI audio and video transmitters + compatible with HDMI 1.4 and DVI 1.0. They support color space + conversion, S/PDIF, CEC and HDCP. The transmitter input is MIPI DSI. + +properties: + compatible: + enum: + - adi,adv7533 + - adi,adv7535 + + reg: + description: | + I2C slave addresses. + + The ADV7533/35 internal registers are split into four pages + exposed through different I2C addresses, creating four register + maps. Each map has it own I2C address and acts as a standard slave + device on the I2C bus. The main address is mandatory, others are + optional and revert to defaults if not specified. + minItems: 1 + maxItems: 4 + + reg-names: + description: + Names of maps with programmable addresses. It can contain any map + needing a non-default address. + minItems: 1 + items: + - const: main + - const: edid + - const: cec + - const: packet + + clocks: + description: Reference to the CEC clock. + maxItems: 1 + + clock-names: + const: cec + + interrupts: + maxItems: 1 + + pd-gpios: + description: GPIO connected to the power down signal. + maxItems: 1 + + avdd-supply: + description: A 1.8V supply that powers up the AVDD pin. + + dvdd-supply: + description: A 1.8V supply that powers up the DVDD pin. + + pvdd-supply: + description: A 1.8V supply that powers up the PVDD pin. + + a2vdd-supply: + description: A 1.8V supply that powers up the A2VDD pin. + + v3p3-supply: + description: A 3.3V supply that powers up the V3P3 pin. + + v1p2-supply: + description: + A supply that powers up the V1P2 pin. It can be either 1.2V + or 1.8V for ADV7533 but only 1.8V for ADV7535. + + adi,disable-timing-generator: + description: + Disables the internal timing generator. The chip will rely on the + sync signals in the DSI data lanes, rather than generating its own + timings for HDMI output. + type: boolean + + adi,dsi-lanes: + description: Number of DSI data lanes connected to the DSI host. + $ref: /schemas/types.yaml#/definitions/uint32 + enum: [ 1, 2, 3, 4 ] + + ports: + description: + The ADV7533/35 has two video ports and one audio port. This node + models their connections as documented in + Documentation/devicetree/bindings/media/video-interfaces.txt + Documentation/devicetree/bindings/graph.txt + type: object + properties: + port@0: + description: + Video port for the DSI input. The remote endpoint phandle + should be a reference to a valid mipi_dsi_host_device. + type: object + + port@1: + description: Video port for the HDMI output. + type: object + + port@2: + description: Audio port for the HDMI output. + type: object + +required: + - compatible + - reg + - ports + - adi,dsi-lanes + - avdd-supply + - dvdd-supply + - pvdd-supply + - a2vdd-supply + - v3p3-supply + +additionalProperties: false + +examples: + - | + #include <dt-bindings/interrupt-controller/irq.h> + + i2c@e6500000 { + #address-cells = <1>; + #size-cells = <0>; + + reg = <0 0xe6500000>; + + adv7533: hdmi@39 { + compatible = "adi,adv7533"; + /* + * The EDID page will be accessible on address 0x66 on the I2C + * bus. All other maps continue to use their default addresses. + */ + reg = <0x39>, <0x66>; + reg-names = "main", "edid"; + interrupt-parent = <&gpio3>; + interrupts = <29 IRQ_TYPE_EDGE_FALLING>; + clocks = <&cec_clock>; + clock-names = "cec"; + adi,dsi-lanes = <4>; + avdd-supply = <&v1v8>; + dvdd-supply = <&v1v8>; + pvdd-supply = <&v1v8>; + a2vdd-supply = <&v1v8>; + v3p3-supply = <&v3v3>; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + reg = <0>; + adv7533_in: endpoint { + remote-endpoint = <&dsi_out>; + }; + }; + + port@1 { + reg = <1>; + adv7533_out: endpoint { + remote-endpoint = <&hdmi_connector_in>; + }; + }; + + port@2 { + reg = <2>; + codec_endpoint: endpoint { + remote-endpoint = <&i2s0_cpu_endpoint>; + }; + }; + }; + }; + }; + +... -- 2.25.1 ^ permalink raw reply related [flat|nested] 16+ messages in thread
* [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi, adv7511.txt: convert to yaml @ 2021-06-15 13:13 ` Ricardo Cañuelo 0 siblings, 0 replies; 16+ messages in thread From: Ricardo Cañuelo @ 2021-06-15 13:13 UTC (permalink / raw) To: airlied, daniel, michal.simek, alexandre.torgue, laurent.pinchart Cc: kernel, devicetree, linux-arm-kernel, robh+dt, xuwei5, mcoquelin.stm32, marex Convert the ADV7511/11w/13/33/35 DT bindings to json-schema. The original binding has been split into two files: adi,adv7511.yaml for ADV7511/11W/13 and adi,adv7533.yaml for ADV7533/35. Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com> Reviewed-by: Rob Herring <robh@kernel.org> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> --- .../bindings/display/bridge/adi,adv7511.txt | 143 ----------- .../bindings/display/bridge/adi,adv7511.yaml | 241 ++++++++++++++++++ .../bindings/display/bridge/adi,adv7533.yaml | 184 +++++++++++++ 3 files changed, 425 insertions(+), 143 deletions(-) delete mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt create mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml create mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7533.yaml diff --git a/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt deleted file mode 100644 index 659523f538bf..000000000000 --- a/Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt +++ /dev/null @@ -1,143 +0,0 @@ -Analog Devices ADV7511(W)/13/33/35 HDMI Encoders ------------------------------------------------- - -The ADV7511, ADV7511W, ADV7513, ADV7533 and ADV7535 are HDMI audio and video -transmitters compatible with HDMI 1.4 and DVI 1.0. They support color space -conversion, S/PDIF, CEC and HDCP. ADV7533/5 supports the DSI interface for input -pixels, while the others support RGB interface. - -Required properties: - -- compatible: Should be one of: - "adi,adv7511" - "adi,adv7511w" - "adi,adv7513" - "adi,adv7533" - "adi,adv7535" - -- reg: I2C slave addresses - The ADV7511 internal registers are split into four pages exposed through - different I2C addresses, creating four register maps. Each map has it own - I2C address and acts as a standard slave device on the I2C bus. The main - address is mandatory, others are optional and revert to defaults if not - specified. - - -The ADV7511 supports a large number of input data formats that differ by their -color depth, color format, clock mode, bit justification and random -arrangement of components on the data bus. The combination of the following -properties describe the input and map directly to the video input tables of the -ADV7511 datasheet that document all the supported combinations. - -- adi,input-depth: Number of bits per color component at the input (8, 10 or - 12). -- adi,input-colorspace: The input color space, one of "rgb", "yuv422" or - "yuv444". -- adi,input-clock: The input clock type, one of "1x" (one clock cycle per - pixel), "2x" (two clock cycles per pixel), "ddr" (one clock cycle per pixel, - data driven on both edges). - -The following input format properties are required except in "rgb 1x" and -"yuv444 1x" modes, in which case they must not be specified. - -- adi,input-style: The input components arrangement variant (1, 2 or 3), as - listed in the input format tables in the datasheet. -- adi,input-justification: The input bit justification ("left", "evenly", - "right"). - -- avdd-supply: A 1.8V supply that powers up the AVDD pin on the chip. -- dvdd-supply: A 1.8V supply that powers up the DVDD pin on the chip. -- pvdd-supply: A 1.8V supply that powers up the PVDD pin on the chip. -- dvdd-3v-supply: A 3.3V supply that powers up the pin called DVDD_3V - on the chip. -- bgvdd-supply: A 1.8V supply that powers up the BGVDD pin. This is - needed only for ADV7511. - -The following properties are required for ADV7533 and ADV7535: - -- adi,dsi-lanes: Number of DSI data lanes connected to the DSI host. It should - be one of 1, 2, 3 or 4. -- a2vdd-supply: 1.8V supply that powers up the A2VDD pin on the chip. -- v3p3-supply: A 3.3V supply that powers up the V3P3 pin on the chip. -- v1p2-supply: A supply that powers up the V1P2 pin on the chip. It can be - either 1.2V or 1.8V for ADV7533 but only 1.8V for ADV7535. - -Optional properties: - -- interrupts: Specifier for the ADV7511 interrupt -- pd-gpios: Specifier for the GPIO connected to the power down signal - -- adi,clock-delay: Video data clock delay relative to the pixel clock, in ps - (-1200 ps .. 1600 ps). Defaults to no delay. -- adi,embedded-sync: The input uses synchronization signals embedded in the - data stream (similar to BT.656). Defaults to separate H/V synchronization - signals. -- adi,disable-timing-generator: Only for ADV7533 and ADV7535. Disables the - internal timing generator. The chip will rely on the sync signals in the - DSI data lanes, rather than generate its own timings for HDMI output. -- clocks: from common clock binding: reference to the CEC clock. -- clock-names: from common clock binding: must be "cec". -- reg-names : Names of maps with programmable addresses. - It can contain any map needing a non-default address. - Possible maps names are : "main", "edid", "cec", "packet" - -Required nodes: - -The ADV7511 has two video ports. Their connections are modelled using the OF -graph bindings specified in Documentation/devicetree/bindings/graph.txt. - -- Video port 0 for the RGB, YUV or DSI input. In the case of ADV7533/5, the - remote endpoint phandle should be a reference to a valid mipi_dsi_host device - node. -- Video port 1 for the HDMI output -- Audio port 2 for the HDMI audio input - - -Example -------- - - adv7511w: hdmi@39 { - compatible = "adi,adv7511w"; - /* - * The EDID page will be accessible on address 0x66 on the I2C - * bus. All other maps continue to use their default addresses. - */ - reg = <0x39>, <0x66>; - reg-names = "main", "edid"; - interrupt-parent = <&gpio3>; - interrupts = <29 IRQ_TYPE_EDGE_FALLING>; - clocks = <&cec_clock>; - clock-names = "cec"; - - adi,input-depth = <8>; - adi,input-colorspace = "rgb"; - adi,input-clock = "1x"; - adi,input-style = <1>; - adi,input-justification = "evenly"; - - ports { - #address-cells = <1>; - #size-cells = <0>; - - port@0 { - reg = <0>; - adv7511w_in: endpoint { - remote-endpoint = <&dpi_out>; - }; - }; - - port@1 { - reg = <1>; - adv7511_out: endpoint { - remote-endpoint = <&hdmi_connector_in>; - }; - }; - - port@2 { - reg = <2>; - codec_endpoint: endpoint { - remote-endpoint = <&i2s0_cpu_endpoint>; - }; - }; - }; - }; diff --git a/Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml new file mode 100644 index 000000000000..87f485ee2fb5 --- /dev/null +++ b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml @@ -0,0 +1,241 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/display/bridge/adi,adv7511.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Analog Devices ADV7511/11W/13 HDMI Encoders + +maintainers: + - Laurent Pinchart <laurent.pinchart@ideasonboard.com> + +description: | + The ADV7511, ADV7511W and ADV7513 are HDMI audio and video + transmitters compatible with HDMI 1.4 and DVI 1.0. They support color + space conversion, S/PDIF, CEC and HDCP. The transmitter input is + parallel RGB or YUV data. + +properties: + compatible: + enum: + - adi,adv7511 + - adi,adv7511w + - adi,adv7513 + + reg: + description: | + I2C slave addresses. + + The ADV7511/11W/13 internal registers are split into four pages + exposed through different I2C addresses, creating four register + maps. Each map has it own I2C address and acts as a standard slave + device on the I2C bus. The main address is mandatory, others are + optional and revert to defaults if not specified. + minItems: 1 + maxItems: 4 + + reg-names: + description: + Names of maps with programmable addresses. It can contain any map + needing a non-default address. + minItems: 1 + maxItems: 4 + items: + - const: main + - const: edid + - const: cec + - const: packet + + clocks: + description: Reference to the CEC clock. + maxItems: 1 + + clock-names: + const: cec + + interrupts: + maxItems: 1 + + pd-gpios: + description: GPIO connected to the power down signal. + maxItems: 1 + + avdd-supply: + description: A 1.8V supply that powers up the AVDD pin. + + dvdd-supply: + description: A 1.8V supply that powers up the DVDD pin. + + pvdd-supply: + description: A 1.8V supply that powers up the PVDD pin. + + dvdd-3v-supply: + description: A 3.3V supply that powers up the DVDD_3V pin. + + bgvdd-supply: + description: A 1.8V supply that powers up the BGVDD pin. + + adi,input-depth: + description: Number of bits per color component at the input. + allOf: + - $ref: /schemas/types.yaml#/definitions/uint32 + - enum: [ 8, 10, 12 ] + + adi,input-colorspace: + description: Input color space. + enum: [ rgb, yuv422, yuv444 ] + + adi,input-clock: + description: | + Input clock type. + "1x": one clock cycle per pixel + "2x": two clock cycles per pixel + "dd": one clock cycle per pixel, data driven on both edges + enum: [ 1x, 2x, dd ] + + adi,clock-delay: + description: + Video data clock delay relative to the pixel clock, in ps + (-1200ps .. 1600 ps). + $ref: /schemas/types.yaml#/definitions/uint32 + default: 0 + + adi,embedded-sync: + description: + If defined, the input uses synchronization signals embedded in the + data stream (similar to BT.656). + type: boolean + + adi,input-style: + description: + Input components arrangement variant as listed in the input + format tables in the datasheet. + $ref: /schemas/types.yaml#/definitions/uint32 + enum: [ 1, 2, 3 ] + + adi,input-justification: + description: Input bit justification. + enum: [ left, evenly, right ] + + ports: + description: + The ADV7511(W)/13 has two video ports and one audio port. This node + models their connections as documented in + Documentation/devicetree/bindings/media/video-interfaces.txt + Documentation/devicetree/bindings/graph.txt + type: object + properties: + port@0: + description: Video port for the RGB or YUV input. + type: object + + port@1: + description: Video port for the HDMI output. + type: object + + port@2: + description: Audio port for the HDMI output. + type: object + +# adi,input-colorspace and adi,input-clock are required except in +# "rgb 1x" and "yuv444 1x" modes, in which case they must not be +# specified. +if: + not: + properties: + adi,input-colorspace: + contains: + enum: [ rgb, yuv444 ] + adi,input-clock: + contains: + const: 1x + +then: + required: + - adi,input-style + - adi,input-justification + +else: + properties: + adi,input-style: false + adi,input-justification: false + + +required: + - compatible + - reg + - ports + - adi,input-depth + - adi,input-colorspace + - adi,input-clock + - avdd-supply + - dvdd-supply + - pvdd-supply + - dvdd-3v-supply + - bgvdd-supply + +additionalProperties: false + +examples: + - | + #include <dt-bindings/interrupt-controller/irq.h> + + i2c@e6500000 { + #address-cells = <1>; + #size-cells = <0>; + + reg = <0 0xe6500000>; + + adv7511w: hdmi@39 { + compatible = "adi,adv7511w"; + /* + * The EDID page will be accessible on address 0x66 on the I2C + * bus. All other maps continue to use their default addresses. + */ + reg = <0x39>, <0x66>; + reg-names = "main", "edid"; + interrupt-parent = <&gpio3>; + interrupts = <29 IRQ_TYPE_EDGE_FALLING>; + clocks = <&cec_clock>; + clock-names = "cec"; + avdd-supply = <&v1v8>; + dvdd-supply = <&v1v8>; + pvdd-supply = <&v1v8>; + dvdd-3v-supply = <&v3v3>; + bgvdd-supply = <&v1v8>; + + adi,input-depth = <8>; + adi,input-colorspace = "yuv422"; + adi,input-clock = "1x"; + + adi,input-style = <3>; + adi,input-justification = "right"; + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + reg = <0>; + adv7511w_in: endpoint { + remote-endpoint = <&dpi_out>; + }; + }; + + port@1 { + reg = <1>; + adv7511_out: endpoint { + remote-endpoint = <&hdmi_connector_in>; + }; + }; + + port@2 { + reg = <2>; + codec_endpoint: endpoint { + remote-endpoint = <&i2s0_cpu_endpoint>; + }; + }; + }; + }; + }; + +... diff --git a/Documentation/devicetree/bindings/display/bridge/adi,adv7533.yaml b/Documentation/devicetree/bindings/display/bridge/adi,adv7533.yaml new file mode 100644 index 000000000000..f36209137c8a --- /dev/null +++ b/Documentation/devicetree/bindings/display/bridge/adi,adv7533.yaml @@ -0,0 +1,184 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/display/bridge/adi,adv7533.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Analog Devices ADV7533/35 HDMI Encoders + +maintainers: + - Laurent Pinchart <laurent.pinchart@ideasonboard.com> + +description: | + The ADV7533 and ADV7535 are HDMI audio and video transmitters + compatible with HDMI 1.4 and DVI 1.0. They support color space + conversion, S/PDIF, CEC and HDCP. The transmitter input is MIPI DSI. + +properties: + compatible: + enum: + - adi,adv7533 + - adi,adv7535 + + reg: + description: | + I2C slave addresses. + + The ADV7533/35 internal registers are split into four pages + exposed through different I2C addresses, creating four register + maps. Each map has it own I2C address and acts as a standard slave + device on the I2C bus. The main address is mandatory, others are + optional and revert to defaults if not specified. + minItems: 1 + maxItems: 4 + + reg-names: + description: + Names of maps with programmable addresses. It can contain any map + needing a non-default address. + minItems: 1 + items: + - const: main + - const: edid + - const: cec + - const: packet + + clocks: + description: Reference to the CEC clock. + maxItems: 1 + + clock-names: + const: cec + + interrupts: + maxItems: 1 + + pd-gpios: + description: GPIO connected to the power down signal. + maxItems: 1 + + avdd-supply: + description: A 1.8V supply that powers up the AVDD pin. + + dvdd-supply: + description: A 1.8V supply that powers up the DVDD pin. + + pvdd-supply: + description: A 1.8V supply that powers up the PVDD pin. + + a2vdd-supply: + description: A 1.8V supply that powers up the A2VDD pin. + + v3p3-supply: + description: A 3.3V supply that powers up the V3P3 pin. + + v1p2-supply: + description: + A supply that powers up the V1P2 pin. It can be either 1.2V + or 1.8V for ADV7533 but only 1.8V for ADV7535. + + adi,disable-timing-generator: + description: + Disables the internal timing generator. The chip will rely on the + sync signals in the DSI data lanes, rather than generating its own + timings for HDMI output. + type: boolean + + adi,dsi-lanes: + description: Number of DSI data lanes connected to the DSI host. + $ref: /schemas/types.yaml#/definitions/uint32 + enum: [ 1, 2, 3, 4 ] + + ports: + description: + The ADV7533/35 has two video ports and one audio port. This node + models their connections as documented in + Documentation/devicetree/bindings/media/video-interfaces.txt + Documentation/devicetree/bindings/graph.txt + type: object + properties: + port@0: + description: + Video port for the DSI input. The remote endpoint phandle + should be a reference to a valid mipi_dsi_host_device. + type: object + + port@1: + description: Video port for the HDMI output. + type: object + + port@2: + description: Audio port for the HDMI output. + type: object + +required: + - compatible + - reg + - ports + - adi,dsi-lanes + - avdd-supply + - dvdd-supply + - pvdd-supply + - a2vdd-supply + - v3p3-supply + +additionalProperties: false + +examples: + - | + #include <dt-bindings/interrupt-controller/irq.h> + + i2c@e6500000 { + #address-cells = <1>; + #size-cells = <0>; + + reg = <0 0xe6500000>; + + adv7533: hdmi@39 { + compatible = "adi,adv7533"; + /* + * The EDID page will be accessible on address 0x66 on the I2C + * bus. All other maps continue to use their default addresses. + */ + reg = <0x39>, <0x66>; + reg-names = "main", "edid"; + interrupt-parent = <&gpio3>; + interrupts = <29 IRQ_TYPE_EDGE_FALLING>; + clocks = <&cec_clock>; + clock-names = "cec"; + adi,dsi-lanes = <4>; + avdd-supply = <&v1v8>; + dvdd-supply = <&v1v8>; + pvdd-supply = <&v1v8>; + a2vdd-supply = <&v1v8>; + v3p3-supply = <&v3v3>; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + reg = <0>; + adv7533_in: endpoint { + remote-endpoint = <&dsi_out>; + }; + }; + + port@1 { + reg = <1>; + adv7533_out: endpoint { + remote-endpoint = <&hdmi_connector_in>; + }; + }; + + port@2 { + reg = <2>; + codec_endpoint: endpoint { + remote-endpoint = <&i2s0_cpu_endpoint>; + }; + }; + }; + }; + }; + +... -- 2.25.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply related [flat|nested] 16+ messages in thread
* Re: [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml 2021-06-15 13:13 ` [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi, adv7511.txt: " Ricardo Cañuelo @ 2021-06-17 14:46 ` Rob Herring -1 siblings, 0 replies; 16+ messages in thread From: Rob Herring @ 2021-06-17 14:46 UTC (permalink / raw) To: Ricardo Cañuelo Cc: laurent.pinchart, airlied, xuwei5, mcoquelin.stm32, marex, alexandre.torgue, daniel, michal.simek, kernel, linux-arm-kernel, robh+dt, devicetree On Tue, 15 Jun 2021 15:13:33 +0200, Ricardo Cañuelo wrote: > Convert the ADV7511/11w/13/33/35 DT bindings to json-schema. The > original binding has been split into two files: adi,adv7511.yaml for > ADV7511/11W/13 and adi,adv7533.yaml for ADV7533/35. > > Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com> > Reviewed-by: Rob Herring <robh@kernel.org> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> > --- > .../bindings/display/bridge/adi,adv7511.txt | 143 ----------- > .../bindings/display/bridge/adi,adv7511.yaml | 241 ++++++++++++++++++ > .../bindings/display/bridge/adi,adv7533.yaml | 184 +++++++++++++ > 3 files changed, 425 insertions(+), 143 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt > create mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml > create mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7533.yaml > Applied, thanks! ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi, adv7511.txt: convert to yaml @ 2021-06-17 14:46 ` Rob Herring 0 siblings, 0 replies; 16+ messages in thread From: Rob Herring @ 2021-06-17 14:46 UTC (permalink / raw) To: Ricardo Cañuelo Cc: laurent.pinchart, airlied, xuwei5, mcoquelin.stm32, marex, alexandre.torgue, daniel, michal.simek, kernel, linux-arm-kernel, robh+dt, devicetree On Tue, 15 Jun 2021 15:13:33 +0200, Ricardo Cañuelo wrote: > Convert the ADV7511/11w/13/33/35 DT bindings to json-schema. The > original binding has been split into two files: adi,adv7511.yaml for > ADV7511/11W/13 and adi,adv7533.yaml for ADV7533/35. > > Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com> > Reviewed-by: Rob Herring <robh@kernel.org> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> > --- > .../bindings/display/bridge/adi,adv7511.txt | 143 ----------- > .../bindings/display/bridge/adi,adv7511.yaml | 241 ++++++++++++++++++ > .../bindings/display/bridge/adi,adv7533.yaml | 184 +++++++++++++ > 3 files changed, 425 insertions(+), 143 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7511.txt > create mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml > create mode 100644 Documentation/devicetree/bindings/display/bridge/adi,adv7533.yaml > Applied, thanks! _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml 2021-06-15 13:13 ` [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi, adv7511.txt: " Ricardo Cañuelo @ 2021-06-18 7:55 ` Geert Uytterhoeven -1 siblings, 0 replies; 16+ messages in thread From: Geert Uytterhoeven @ 2021-06-18 7:55 UTC (permalink / raw) To: Ricardo Cañuelo Cc: David Airlie, Daniel Vetter, Michal Simek, alexandre.torgue, Laurent Pinchart, Collabora Kernel ML, open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS, Linux ARM, Rob Herring, Wei Xu, Maxime Coquelin, Marek Vasut, Linux-Renesas Hi Ricardo, On Tue, Jun 15, 2021 at 3:15 PM Ricardo Cañuelo <ricardo.canuelo@collabora.com> wrote: > Convert the ADV7511/11w/13/33/35 DT bindings to json-schema. The > original binding has been split into two files: adi,adv7511.yaml for > ADV7511/11W/13 and adi,adv7533.yaml for ADV7533/35. > > Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com> > Reviewed-by: Rob Herring <robh@kernel.org> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Thanks for your patch, which is now commit cfe34bb7a770c5d8 ("dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml") in robh/for-next. > --- /dev/null > +++ b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml > +required: > + - compatible > + - reg > + - ports > + - adi,input-depth > + - adi,input-colorspace > + - adi,input-clock > + - avdd-supply > + - dvdd-supply > + - pvdd-supply > + - dvdd-3v-supply > + - bgvdd-supply This causes lots of failures like: arm/boot/dts/r8a7743-iwg20d-q7-dbcm-ca.dt.yaml: hdmi@39: 'avdd-supply' is a required property Should all supplies be required? Looking at the driver, missing supplies are automatically replaced by dummy regulators by the regulator framework. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi, adv7511.txt: convert to yaml @ 2021-06-18 7:55 ` Geert Uytterhoeven 0 siblings, 0 replies; 16+ messages in thread From: Geert Uytterhoeven @ 2021-06-18 7:55 UTC (permalink / raw) To: Ricardo Cañuelo Cc: David Airlie, Daniel Vetter, Michal Simek, alexandre.torgue, Laurent Pinchart, Collabora Kernel ML, open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS, Linux ARM, Rob Herring, Wei Xu, Maxime Coquelin, Marek Vasut, Linux-Renesas Hi Ricardo, On Tue, Jun 15, 2021 at 3:15 PM Ricardo Cañuelo <ricardo.canuelo@collabora.com> wrote: > Convert the ADV7511/11w/13/33/35 DT bindings to json-schema. The > original binding has been split into two files: adi,adv7511.yaml for > ADV7511/11W/13 and adi,adv7533.yaml for ADV7533/35. > > Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com> > Reviewed-by: Rob Herring <robh@kernel.org> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Thanks for your patch, which is now commit cfe34bb7a770c5d8 ("dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml") in robh/for-next. > --- /dev/null > +++ b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml > +required: > + - compatible > + - reg > + - ports > + - adi,input-depth > + - adi,input-colorspace > + - adi,input-clock > + - avdd-supply > + - dvdd-supply > + - pvdd-supply > + - dvdd-3v-supply > + - bgvdd-supply This causes lots of failures like: arm/boot/dts/r8a7743-iwg20d-q7-dbcm-ca.dt.yaml: hdmi@39: 'avdd-supply' is a required property Should all supplies be required? Looking at the driver, missing supplies are automatically replaced by dummy regulators by the regulator framework. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml 2021-06-18 7:55 ` [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi, adv7511.txt: " Geert Uytterhoeven @ 2021-06-18 8:51 ` Laurent Pinchart -1 siblings, 0 replies; 16+ messages in thread From: Laurent Pinchart @ 2021-06-18 8:51 UTC (permalink / raw) To: Geert Uytterhoeven Cc: Ricardo Cañuelo, David Airlie, Daniel Vetter, Michal Simek, alexandre.torgue, Collabora Kernel ML, open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS, Linux ARM, Rob Herring, Wei Xu, Maxime Coquelin, Marek Vasut, Linux-Renesas Hi Geert, On Fri, Jun 18, 2021 at 09:55:38AM +0200, Geert Uytterhoeven wrote: > On Tue, Jun 15, 2021 at 3:15 PM Ricardo Cañuelo wrote: > > Convert the ADV7511/11w/13/33/35 DT bindings to json-schema. The > > original binding has been split into two files: adi,adv7511.yaml for > > ADV7511/11W/13 and adi,adv7533.yaml for ADV7533/35. > > > > Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com> > > Reviewed-by: Rob Herring <robh@kernel.org> > > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> > > Thanks for your patch, which is now commit cfe34bb7a770c5d8 > ("dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml") > in robh/for-next. > > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml > > > +required: > > + - compatible > > + - reg > > + - ports > > + - adi,input-depth > > + - adi,input-colorspace > > + - adi,input-clock > > + - avdd-supply > > + - dvdd-supply > > + - pvdd-supply > > + - dvdd-3v-supply > > + - bgvdd-supply > > This causes lots of failures like: > > arm/boot/dts/r8a7743-iwg20d-q7-dbcm-ca.dt.yaml: hdmi@39: > 'avdd-supply' is a required property > > Should all supplies be required? > Looking at the driver, missing supplies are automatically replaced by > dummy regulators by the regulator framework. Generally speaking, I like DT bindings to be descriptive of the hardware, and thus require power supplies that are needed for the device to function, even if they are fixed supplies. This being said, I think there's also room to group some power supplies together in the bindings, when they are not meant by the device to be controlled separately. In this specific case, we also need to take into account that the adv7511 and adv7533 have different supplies. -- Regards, Laurent Pinchart ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi, adv7511.txt: convert to yaml @ 2021-06-18 8:51 ` Laurent Pinchart 0 siblings, 0 replies; 16+ messages in thread From: Laurent Pinchart @ 2021-06-18 8:51 UTC (permalink / raw) To: Geert Uytterhoeven Cc: Ricardo Cañuelo, David Airlie, Daniel Vetter, Michal Simek, alexandre.torgue, Collabora Kernel ML, open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS, Linux ARM, Rob Herring, Wei Xu, Maxime Coquelin, Marek Vasut, Linux-Renesas Hi Geert, On Fri, Jun 18, 2021 at 09:55:38AM +0200, Geert Uytterhoeven wrote: > On Tue, Jun 15, 2021 at 3:15 PM Ricardo Cañuelo wrote: > > Convert the ADV7511/11w/13/33/35 DT bindings to json-schema. The > > original binding has been split into two files: adi,adv7511.yaml for > > ADV7511/11W/13 and adi,adv7533.yaml for ADV7533/35. > > > > Signed-off-by: Ricardo Cañuelo <ricardo.canuelo@collabora.com> > > Reviewed-by: Rob Herring <robh@kernel.org> > > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> > > Thanks for your patch, which is now commit cfe34bb7a770c5d8 > ("dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml") > in robh/for-next. > > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/display/bridge/adi,adv7511.yaml > > > +required: > > + - compatible > > + - reg > > + - ports > > + - adi,input-depth > > + - adi,input-colorspace > > + - adi,input-clock > > + - avdd-supply > > + - dvdd-supply > > + - pvdd-supply > > + - dvdd-3v-supply > > + - bgvdd-supply > > This causes lots of failures like: > > arm/boot/dts/r8a7743-iwg20d-q7-dbcm-ca.dt.yaml: hdmi@39: > 'avdd-supply' is a required property > > Should all supplies be required? > Looking at the driver, missing supplies are automatically replaced by > dummy regulators by the regulator framework. Generally speaking, I like DT bindings to be descriptive of the hardware, and thus require power supplies that are needed for the device to function, even if they are fixed supplies. This being said, I think there's also room to group some power supplies together in the bindings, when they are not meant by the device to be controlled separately. In this specific case, we also need to take into account that the adv7511 and adv7533 have different supplies. -- Regards, Laurent Pinchart _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml 2021-06-18 8:51 ` [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi, adv7511.txt: " Laurent Pinchart @ 2021-06-23 6:11 ` Ricardo Cañuelo -1 siblings, 0 replies; 16+ messages in thread From: Ricardo Cañuelo @ 2021-06-23 6:11 UTC (permalink / raw) To: Laurent Pinchart, Geert Uytterhoeven Cc: David Airlie, Daniel Vetter, Michal Simek, alexandre.torgue, Collabora Kernel ML, open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS, Linux ARM, Rob Herring, Wei Xu, Maxime Coquelin, Marek Vasut, Linux-Renesas Hi, > On Fri, Jun 18, 2021 at 09:55:38AM +0200, Geert Uytterhoeven wrote: > > This causes lots of failures like: > > > > arm/boot/dts/r8a7743-iwg20d-q7-dbcm-ca.dt.yaml: hdmi@39: > > 'avdd-supply' is a required property > > > > Should all supplies be required? > > Looking at the driver, missing supplies are automatically replaced by > > dummy regulators by the regulator framework. > > Generally speaking, I like DT bindings to be descriptive of the > hardware, and thus require power supplies that are needed for the device > to function, even if they are fixed supplies. > > This being said, I think there's also room to group some power supplies > together in the bindings, when they are not meant by the device to be > controlled separately. In this specific case, we also need to take into > account that the adv7511 and adv7533 have different supplies. Thanks for the review, guys. Yes, there were some dtbs check warnings to be expected, the consensus in a previous version of the patch was that that shouldn't be a blocker for a binding conversion and that the *.dts definitions should eventually be fixed to comply with the binding, which is, IMO, a more reasonable process to keep the binding conversion effort progressing. Cheers, Ricardo ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml @ 2021-06-23 6:11 ` Ricardo Cañuelo 0 siblings, 0 replies; 16+ messages in thread From: Ricardo Cañuelo @ 2021-06-23 6:11 UTC (permalink / raw) To: Laurent Pinchart, Geert Uytterhoeven Cc: David Airlie, Daniel Vetter, Michal Simek, alexandre.torgue, Collabora Kernel ML, open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS, Linux ARM, Rob Herring, Wei Xu, Maxime Coquelin, Marek Vasut, Linux-Renesas Hi, > On Fri, Jun 18, 2021 at 09:55:38AM +0200, Geert Uytterhoeven wrote: > > This causes lots of failures like: > > > > arm/boot/dts/r8a7743-iwg20d-q7-dbcm-ca.dt.yaml: hdmi@39: > > 'avdd-supply' is a required property > > > > Should all supplies be required? > > Looking at the driver, missing supplies are automatically replaced by > > dummy regulators by the regulator framework. > > Generally speaking, I like DT bindings to be descriptive of the > hardware, and thus require power supplies that are needed for the device > to function, even if they are fixed supplies. > > This being said, I think there's also room to group some power supplies > together in the bindings, when they are not meant by the device to be > controlled separately. In this specific case, we also need to take into > account that the adv7511 and adv7533 have different supplies. Thanks for the review, guys. Yes, there were some dtbs check warnings to be expected, the consensus in a previous version of the patch was that that shouldn't be a blocker for a binding conversion and that the *.dts definitions should eventually be fixed to comply with the binding, which is, IMO, a more reasonable process to keep the binding conversion effort progressing. Cheers, Ricardo _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2021-06-23 6:13 UTC | newest] Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-06-15 13:13 [RESEND PATCH v4 0/3] Convert adi,adv7511.txt DT bindings to yaml Ricardo Cañuelo 2021-06-15 13:13 ` Ricardo Cañuelo 2021-06-15 13:13 ` [RESEND PATCH v4 1/3] ARM: dts: zynq: add port definitions to hdmi-tx@39 Ricardo Cañuelo 2021-06-15 13:13 ` Ricardo Cañuelo 2021-06-15 13:13 ` [RESEND PATCH v4 2/3] ARM: dts: stm32: make hdmi-transmitter node compliant with DT bindings Ricardo Cañuelo 2021-06-15 13:13 ` Ricardo Cañuelo 2021-06-15 13:13 ` [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi,adv7511.txt: convert to yaml Ricardo Cañuelo 2021-06-15 13:13 ` [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi, adv7511.txt: " Ricardo Cañuelo 2021-06-17 14:46 ` [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi,adv7511.txt: " Rob Herring 2021-06-17 14:46 ` [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi, adv7511.txt: " Rob Herring 2021-06-18 7:55 ` [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi,adv7511.txt: " Geert Uytterhoeven 2021-06-18 7:55 ` [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi, adv7511.txt: " Geert Uytterhoeven 2021-06-18 8:51 ` [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi,adv7511.txt: " Laurent Pinchart 2021-06-18 8:51 ` [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi, adv7511.txt: " Laurent Pinchart 2021-06-23 6:11 ` [RESEND PATCH v4 3/3] dt-bindings: drm: bridge: adi,adv7511.txt: " Ricardo Cañuelo 2021-06-23 6:11 ` Ricardo Cañuelo
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.