[PATCH] dt-bindings: bridge: Convert Samsung MIPI DSIM bridge to yaml
Marek Vasut
marex at denx.de
Sun Apr 2 17:52:05 UTC 2023
On 3/31/23 21:57, Fabio Estevam wrote:
> From: Jagan Teki <jagan at amarulasolutions.com>
>
> Samsung MIPI DSIM bridge can be found on Exynos and NXP's
> i.MX8M Mini and Nano SoC's.
MX8M Plus too .
> Convert exynos_dsim.txt to yaml.
>
> Used the example node from latest Exynos SoC instead of
> the one used in legacy exynos_dsim.txt.
>
> Signed-off-by: Jagan Teki <jagan at amarulasolutions.com>
> Signed-off-by: Fabio Estevam <festevam at denx.de>
> ---
> .../display/bridge/samsung,mipi-dsim.yaml | 275 ++++++++++++++++++
> .../bindings/display/exynos/exynos_dsim.txt | 92 ------
> 2 files changed, 275 insertions(+), 92 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/display/bridge/samsung,mipi-dsim.yaml
> delete mode 100644 Documentation/devicetree/bindings/display/exynos/exynos_dsim.txt
>
> diff --git a/Documentation/devicetree/bindings/display/bridge/samsung,mipi-dsim.yaml b/Documentation/devicetree/bindings/display/bridge/samsung,mipi-dsim.yaml
> new file mode 100644
> index 000000000000..c131bd879caf
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/bridge/samsung,mipi-dsim.yaml
> @@ -0,0 +1,275 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/display/bridge/samsung,mipi-dsim.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Samsung MIPI DSIM bridge controller
> +
> +maintainers:
> + - Inki Dae <inki.dae at samsung.com>
> + - Jagan Teki <jagan at amarulasolutions.com>
> +
> +description: |
> + Samsung MIPI DSIM bridge controller can be found it on Exynos
> + and i.MX8M Mini and Nano SoC's.
Plus too.
> +properties:
> + compatible:
> + enum:
> + - samsung,exynos3250-mipi-dsi
> + - samsung,exynos4210-mipi-dsi
> + - samsung,exynos5410-mipi-dsi
> + - samsung,exynos5422-mipi-dsi
> + - samsung,exynos5433-mipi-dsi
> + - fsl,imx8mm-mipi-dsim
> + - fsl,imx8mp-mipi-dsim
You have plus here already, so just update the description.
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + '#address-cells':
> + const: 1
> +
> + '#size-cells':
> + const: 0
> +
> + clocks:
> + minItems: 2
> + maxItems: 5
> +
> + clock-names:
> + minItems: 2
> + maxItems: 5
> +
> + phys:
> + maxItems: 1
> + description: phandle to the phy module representing the DPHY
> +
> + phy-names:
> + items:
> + - const: dsim
> +
> + samsung,phy-type:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: phandle to the samsung phy-type
> +
> + power-domains:
> + description: phandle to the associated power domain
> + maxItems: 1
> +
> + samsung,power-domain:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description: phandle to the associated samsung power domain
> +
> + vddcore-supply:
> + description: MIPI DSIM Core voltage supply (e.g. 1.1V)
> +
> + vddio-supply:
> + description: MIPI DSIM I/O and PLL voltage supply (e.g. 1.8V)
> +
> + samsung,burst-clock-frequency:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + DSIM high speed burst mode frequency.
> +
> + samsung,esc-clock-frequency:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + DSIM escape mode frequency.
> +
> + samsung,pll-clock-frequency:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + DSIM oscillator clock frequency.
> +
> + ports:
> + $ref: /schemas/graph.yaml#/properties/ports
> +
> + properties:
> + port at 0:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + description:
> + Input port node to receive pixel data from the
> + display controller. Exactly one endpoint must be
> + specified.
> + properties:
> + endpoint at 0:
Why endpoint at 0 if this only has one endpoint ?
> + $ref: /schemas/graph.yaml#/properties/endpoint
> + description: sub-node describing the input from MIC
> +
> + unevaluatedProperties: false
> +
> + port at 1:
> + $ref: /schemas/graph.yaml#/properties/port
> + description:
> + DSI output port node to the panel or the next bridge
> + in the chain
[...]
More information about the dri-devel
mailing list