From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Liu Ying <victor.liu@nxp.com>,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: kishon@ti.com, vkoul@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com
Subject: Re: [PATCH v2 2/3] dt-bindings: phy: Add Freescale i.MX8qm Mixel LVDS PHY binding
Date: Mon, 20 Jun 2022 12:32:40 +0200 [thread overview]
Message-ID: <ca5834ea-701f-2260-da2a-84b22d4033db@linaro.org> (raw)
In-Reply-To: <20220620034533.4108170-3-victor.liu@nxp.com>
On 20/06/2022 05:45, Liu Ying wrote:
> Add bindings for Mixel LVDS PHY found on Freescale i.MX8qm SoC.
>
> Signed-off-by: Liu Ying <victor.liu@nxp.com>
> ---
> v1->v2:
> * Set fsl,imx8qm-lvds-phy' and 'mixel,lvds-phy' as compatible's enum. (Krzysztof)
> * Skip 'clock-names' property. (Krzysztof)
> * Drop 'This patch' from commit message. (Krzysztof)
>
> .../bindings/phy/mixel,lvds-phy.yaml | 61 +++++++++++++++++++
> 1 file changed, 61 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/mixel,lvds-phy.yaml
>
> diff --git a/Documentation/devicetree/bindings/phy/mixel,lvds-phy.yaml b/Documentation/devicetree/bindings/phy/mixel,lvds-phy.yaml
> new file mode 100644
> index 000000000000..4bfcc0dd987f
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/mixel,lvds-phy.yaml
Name the file fsl,imx8qm-lvds-phy.yaml
> @@ -0,0 +1,61 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/phy/mixel,lvds-phy.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Mixel LVDS PHY for Freescale i.MX8qm SoC
> +
> +maintainers:
> + - Liu Ying <victor.liu@nxp.com>
> +
> +description: |
> + The Mixel LVDS PHY IP block is found on Freescale i.MX8qm SoC.
> + It converts two groups of four 7/10 bits of CMOS data into two
> + groups of four data lanes of LVDS data streams. A phase-locked
> + transmit clock is transmitted in parallel with each group of
> + data streams over a fifth LVDS link. Every cycle of the transmit
> + clock, 56/80 bits of input data are sampled and transmitted
> + through the two groups of LVDS data streams. Together with the
> + transmit clocks, the two groups of LVDS data streams form two
> + LVDS channels.
> +
> + The Mixel LVDS PHY found on Freescale i.MX8qm SoC is controlled
> + by Control and Status Registers(CSR) module in the SoC. The CSR
> + module, as a system controller, contains the PHY's registers.
> +
> +properties:
> + compatible:
> + enum:
> + - fsl,imx8qm-lvds-phy
> + - mixel,lvds-phy
This is not specific enough compatible.
> +
> + "#phy-cells":
> + const: 1
> + description: |
> + Cell allows setting the LVDS channel index of the PHY.
> + Index 0 is for LVDS channel0 and index 1 is for LVDS channel1.
> +
> + clocks:
> + maxItems: 1
> +
> + power-domains:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - "#phy-cells"
> + - clocks
> + - power-domains
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/firmware/imx/rsrc.h>
> + phy {
> + compatible = "fsl,imx8qm-lvds-phy";
> + #phy-cells = <1>;
> + clocks = <&clk IMX_SC_R_LVDS_0 IMX_SC_PM_CLK_PHY>;
> + power-domains = <&pd IMX_SC_R_LVDS_0>;
> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-06-20 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 3:45 [PATCH v2 0/3] phy: freescale: Add i.MX8qm Mixel LVDS PHY support Liu Ying
2022-06-20 3:45 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add prefix for Mixel, Inc Liu Ying
2022-06-20 10:39 ` Krzysztof Kozlowski
2022-06-20 3:45 ` [PATCH v2 2/3] dt-bindings: phy: Add Freescale i.MX8qm Mixel LVDS PHY binding Liu Ying
2022-06-20 10:32 ` Krzysztof Kozlowski [this message]
2022-06-20 12:10 ` Liu Ying
2022-06-20 3:45 ` [PATCH v2 3/3] phy: freescale: Add i.MX8qm Mixel LVDS PHY support Liu Ying
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ca5834ea-701f-2260-da2a-84b22d4033db@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=victor.liu@nxp.com \
--cc=vkoul@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®