From: Liu Ying <victor.liu@nxp.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
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 1/2] dt-bindings: phy: Add Freescale i.MX8qm Mixel LVDS PHY binding
Date: Mon, 20 Jun 2022 11:06:18 +0800 [thread overview]
Message-ID: <89a29795e918343583f45b0f8a65a002592f8b15.camel@nxp.com> (raw)
In-Reply-To: <b83e3100-edd6-4f91-75e0-8a87447d8a4c@linaro.org>
On Sun, 2022-06-19 at 14:11 +0200, Krzysztof Kozlowski wrote:
> On 18/06/2022 11:22, Liu Ying wrote:
> > This patch adds bindings for Mixel LVDS PHY found on
> > Freescale i.MX8qm SoC.
> >
> > Signed-off-by: Liu Ying <victor.liu@nxp.com>
> > ---
> > .../bindings/phy/mixel,lvds-phy.yaml | 64
> > +++++++++++++++++++
> > 1 file changed, 64 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..de964ffb9356
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/phy/mixel,lvds-phy.yaml
> > @@ -0,0 +1,64 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id:
> > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdevicetree.org%2Fschemas%2Fphy%2Fmixel%2Clvds-phy.yaml%23&data=05%7C01%7Cvictor.liu%40nxp.com%7Cb68f9012ddcc44bc10cd08da51ece7f7%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637912375188731290%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=MdBILPYmfYeWeCXXNxy1mu1NcU0b6EW3QztYc294dd4%3D&reserved=0
> > +$schema:
> > https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdevicetree.org%2Fmeta-schemas%2Fcore.yaml%23&data=05%7C01%7Cvictor.liu%40nxp.com%7Cb68f9012ddcc44bc10cd08da51ece7f7%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637912375188731290%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=MhHwku8rbDLAZAQh1T9CGFULMkk5MaNoj3LQnQJ6VXM%3D&reserved=0
> > +
> > +title: Mixel LVDS PHY for Freescale i.MX8qm SoC
>
> If Mixel is a vendor, it needs it's vendor prefix documented and used
> in
> compatible. Filename should match compatible. If it is not a vendor,
> then filename should be "fsl,imx8qm-lvds-phy.yaml"
Mixel is a vendor. I'll document the vendor prefix and set
'fsl,imx8qm-lvds-phy' and 'mixel,lvds-phy' as compatible's enum.
I'll keep the filename as-is.
>
> > +
> > +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:
> > + const: fsl,imx8qm-lvds-phy
> > +
> > + "#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
> > +
> > + clock-names:
> > + const: phy_ref
>
> Maybe just skip the clock-names, it's not bringing anything useful,
> unless you expect some more clocks to be documented later? (but in
> such
> case question would be why they are not documented now)
I'll skip it, because it is the only clock required by the PHY IP that
I'm aware of.
Thanks,
Liu Ying
>
> > +
> > + power-domains:
> > + maxItems: 1
> > +
> > +required:
> > + - compatible
> > + - "#phy-cells"
> > + - clocks
> > + - clock-names
> > + - 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>;
> > + clock-names = "phy_ref";
> > + power-domains = <&pd IMX_SC_R_LVDS_0>;
> > + };
>
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2022-06-20 3:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 9:21 [PATCH 0/2] phy: freescale: Add i.MX8qm Mixel LVDS PHY support Liu Ying
2022-06-18 9:22 ` [PATCH 1/2] dt-bindings: phy: Add Freescale i.MX8qm Mixel LVDS PHY binding Liu Ying
2022-06-19 12:11 ` Krzysztof Kozlowski
2022-06-20 3:06 ` Liu Ying [this message]
2022-06-20 7:35 ` Krzysztof Kozlowski
2022-06-20 7:56 ` Liu Ying
2022-06-20 10:38 ` Krzysztof Kozlowski
2022-06-20 12:08 ` Liu Ying
2022-06-18 9:22 ` [PATCH 2/2] phy: freescale: Add i.MX8qm Mixel LVDS PHY support Liu Ying
2022-06-19 12:15 ` Krzysztof Kozlowski
2022-06-20 3:08 ` 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=89a29795e918343583f45b0f8a65a002592f8b15.camel@nxp.com \
--to=victor.liu@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@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=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;
as well as URLs for NNTP newsgroup(s).