From: Vinod Koul <vkoul@kernel.org>
To: Liu Ying <victor.liu@nxp.com>
Cc: linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kishon@ti.com, 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,
krzysztof.kozlowski@linaro.org
Subject: Re: [PATCH v4 0/3] phy: freescale: Add i.MX8qm Mixel LVDS PHY support
Date: Fri, 8 Jul 2022 10:43:32 +0530 [thread overview]
Message-ID: <Yse8/MjjmShPpltv@matsya> (raw)
In-Reply-To: <20220706034810.2352641-1-victor.liu@nxp.com>
On 06-07-22, 11:48, Liu Ying wrote:
> Hi,
>
> This series aims to add Freescale i.MX8qm LVDS PHY driver and dt-binding
> support.
>
> The PHY IP is from Mixel, Inc.
> The PHY IP supports two LVDS PHYs, thus two LVDS channels.
>
> Each LVDS PHY may work by itself to support a LVDS display device.
>
> When two LVDS PHYs are enabled simultaneously, PHY configurations and reference
> clock rate have to be the same since there is only one set of PHY registers.
> In this case, the two LVDS PHYs are usually used to support a dual LVDS link
> display device, one as master PHY and the other as slave PHY.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2022-07-08 5:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 3:48 [PATCH v4 0/3] phy: freescale: Add i.MX8qm Mixel LVDS PHY support Liu Ying
2022-07-06 3:48 ` [PATCH v4 1/3] dt-bindings: vendor-prefixes: Add prefix for Mixel, Inc Liu Ying
2022-07-06 3:48 ` [PATCH v4 2/3] dt-bindings: phy: Add Freescale i.MX8qm Mixel LVDS PHY binding Liu Ying
2022-07-06 3:48 ` [PATCH v4 3/3] phy: freescale: Add i.MX8qm Mixel LVDS PHY support Liu Ying
2022-07-08 5:13 ` Vinod Koul [this message]
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=Yse8/MjjmShPpltv@matsya \
--to=vkoul@kernel.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=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=victor.liu@nxp.com \
/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).