Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Liu Ying <victor.liu@nxp.com>
To: Biju Das <biju.das.jz@bp.renesas.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Cc: "andrzej.hajda@intel.com" <andrzej.hajda@intel.com>,
	"neil.armstrong@linaro.org" <neil.armstrong@linaro.org>,
	"rfoss@kernel.org" <rfoss@kernel.org>,
	"laurent.pinchart" <laurent.pinchart@ideasonboard.com>,
	"jonas@kwiboo.se" <jonas@kwiboo.se>,
	"jernej.skrabec@gmail.com" <jernej.skrabec@gmail.com>,
	"airlied@gmail.com" <airlied@gmail.com>,
	"simona@ffwll.ch" <simona@ffwll.ch>,
	"maarten.lankhorst@linux.intel.com"
	<maarten.lankhorst@linux.intel.com>,
	"mripard@kernel.org" <mripard@kernel.org>,
	"tzimmermann@suse.de" <tzimmermann@suse.de>,
	"robh@kernel.org" <robh@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"quic_jesszhan@quicinc.com" <quic_jesszhan@quicinc.com>,
	"mchehab@kernel.org" <mchehab@kernel.org>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"will@kernel.org" <will@kernel.org>,
	"sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>,
	"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
	"tomi.valkeinen@ideasonboard.com"
	<tomi.valkeinen@ideasonboard.com>,
	"quic_bjorande@quicinc.com" <quic_bjorande@quicinc.com>,
	"geert+renesas@glider.be" <geert+renesas@glider.be>,
	"dmitry.baryshkov@linaro.org" <dmitry.baryshkov@linaro.org>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"nfraprado@collabora.com" <nfraprado@collabora.com>,
	"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	"sam@ravnborg.org" <sam@ravnborg.org>,
	"marex@denx.de" <marex@denx.de>
Subject: Re: [PATCH v3 12/15] drm/bridge: Add ITE IT6263 LVDS to HDMI converter
Date: Fri, 25 Oct 2024 16:24:48 +0800	[thread overview]
Message-ID: <4e78781a-bce6-4582-b6aa-417f57c4725f@nxp.com> (raw)
In-Reply-To: <TY3PR01MB113465BBC5FD4EAAE89D9EA57864E2@TY3PR01MB11346.jpnprd01.prod.outlook.com>

On 10/24/2024, Biju Das wrote:
> Hi Liu Ying,

Hi Biju,

> 
>> -----Original Message-----
>> From: Liu Ying <victor.liu@nxp.com>
>> Sent: Monday, October 21, 2024 7:45 AM
>> Subject: [PATCH v3 12/15] drm/bridge: Add ITE IT6263 LVDS to HDMI converter
>>
>> Add basic HDMI video output support. Currently, only RGB888 output pixel format is supported.  At the
>> LVDS input side, the driver supports single LVDS link and dual LVDS links with "jeida-24" LVDS
>> mapping.
>>
>> Product link:
>> https://www.ite.com.tw/en/product/cate1/IT6263
> 
> Just a question,
> 
> What is the maximum single link and dual link modes you have tested?

With single LVDS link on i.MX8MP EVK, the highest pixel clock rate I
tested is 74.25MHz(1280x720@60).  i.MX8MP LVDS Display Bridge(LDB)
supports the highest 80MHz pixel clock rate with single LVDS link.

With single LVDS link on i.MX8qxp MEK, the highest pixel clock rate I
tested is 148.5MHz(1920x1080@60).  i.MX8qxp LDB supports the highest
150MHz pixel clock rate with single LVDS link.

With dual LVDS links on both i.MX8MP EVK and i.MX8qxp MEK, the highest
pixel clock rate I tested is 148.5MHz(1920x1080@60).

> 
> On Renesas SMARC RZ/G3E platform I have tested with this patch set,
> 
> Dual link :1080p@60
> 
> and
> 
> Single link:720p@60
> 
> For single link > 720p@60, sometimes I get message
> "it6263 7-004c: failed to wait for video stable"

I don't see this with i.MX8MP EVK and i.MX8qxp MEK.

> 
> From SoC side, it can support max dot clock of 87MHz for single link.
> 
> So just wondering other than reject modes greater than 87MHz from SOC
> side, do we need to limit any thing on bridge device for single link Case?

Since IT6263 works with 1920x1080@60(148.5MHz pixel clock rate) on
i.MX8qxp MEK by using single LVDS link, I'm currently fine with
the existing clock rate validation against the maximal 150MHz pixel
clock rate.

> 
> Cheers,
> Biju

-- 
Regards,
Liu Ying


  reply	other threads:[~2024-10-25  8:24 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21  6:44 [PATCH v3 00/15] Add ITE IT6263 LVDS to HDMI converter support Liu Ying
2024-10-21  6:44 ` [PATCH v3 01/15] arm64: dts: imx8mp-skov-revb-mi1010ait-1cp1: Set "media_disp2_pix" clock rate to 70MHz Liu Ying
2024-10-21  6:44 ` [PATCH v3 02/15] drm/bridge: fsl-ldb: Get the next non-panel bridge Liu Ying
2024-10-21  6:44 ` [PATCH v3 03/15] drm/bridge: fsl-ldb: Use clk_round_rate() to validate "ldb" clock rate Liu Ying
2024-10-21  6:44 ` [PATCH v3 04/15] media: uapi: Add MEDIA_BUS_FMT_RGB101010_1X7X5_{SPWG,JEIDA} Liu Ying
2024-10-21  6:44 ` [PATCH v3 05/15] drm: of: Get MEDIA_BUS_FMT_RGB101010_1X7X5_{JEIDA,SPWG} LVDS data mappings Liu Ying
2024-10-21 11:17   ` Dmitry Baryshkov
2024-10-21  6:44 ` [PATCH v3 06/15] drm: of: Add drm_of_lvds_get_dual_link_pixel_order_sink() Liu Ying
2024-10-21 12:15   ` Dmitry Baryshkov
2024-10-21  6:44 ` [PATCH v3 07/15] dt-bindings: display: lvds-data-mapping: Add 30-bit RGB pixel data mappings Liu Ying
2024-10-21  7:39   ` Krzysztof Kozlowski
2024-10-21  6:44 ` [PATCH v3 08/15] dt-bindings: display: Document dual-link LVDS display common properties Liu Ying
2024-10-21  7:42   ` Krzysztof Kozlowski
2024-10-21  8:19     ` Liu Ying
2024-10-21 19:32       ` Rob Herring
2024-10-21  6:44 ` [PATCH v3 09/15] dt-bindings: display: panel-simple-lvds-dual-ports: Reference lvds-dual-ports.yaml Liu Ying
2024-10-21  7:43   ` Krzysztof Kozlowski
2024-10-21  8:23     ` Liu Ying
2024-10-21 11:06     ` Dmitry Baryshkov
2024-10-21 19:43     ` Rob Herring
2024-10-21 19:40   ` Rob Herring
2024-10-22  7:42     ` Liu Ying
2024-10-21  6:44 ` [PATCH v3 10/15] dt-bindings: display: advantech,idk-2121wr: " Liu Ying
2024-10-21  6:44 ` [PATCH v3 11/15] dt-bindings: display: bridge: Add ITE IT6263 LVDS to HDMI converter Liu Ying
2024-10-21  6:44 ` [PATCH v3 12/15] drm/bridge: " Liu Ying
2024-10-21 10:12   ` Biju Das
2024-10-22  7:30     ` Liu Ying
2024-10-21 12:38   ` Maxime Ripard
2024-10-22  7:36     ` Liu Ying
2024-10-22  7:53       ` Maxime Ripard
2024-10-22  8:10         ` Liu Ying
2024-10-22  8:15           ` Maxime Ripard
2024-10-24 15:10   ` Biju Das
2024-10-25  8:24     ` Liu Ying [this message]
2024-10-25  8:57       ` Biju Das
2024-10-21  6:44 ` [PATCH v3 13/15] arm64: dts: imx8mp-evk: Add NXP LVDS to HDMI adapter cards Liu Ying
2024-10-21  6:44 ` [PATCH v3 14/15] arm64: defconfig: Enable ITE IT6263 driver Liu Ying
2024-10-21  6:44 ` [PATCH v3 15/15] MAINTAINERS: Add maintainer for " 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=4e78781a-bce6-4582-b6aa-417f57c4725f@nxp.com \
    --to=victor.liu@nxp.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=arnd@arndb.de \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=festevam@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=hverkuil@xs4all.nl \
    --cc=imx@lists.linux.dev \
    --cc=jernej.skrabec@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=marex@denx.de \
    --cc=mchehab@kernel.org \
    --cc=mripard@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=nfraprado@collabora.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=quic_bjorande@quicinc.com \
    --cc=quic_jesszhan@quicinc.com \
    --cc=rfoss@kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sam@ravnborg.org \
    --cc=shawnguo@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=thierry.reding@gmail.com \
    --cc=tomi.valkeinen@ideasonboard.com \
    --cc=tzimmermann@suse.de \
    --cc=will@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