From: "Heiko Stübner" <heiko@sntech.de>
To: Andy Yan <andyshrk@163.com>, Alex Bee <knaerzche@gmail.com>
Cc: conor+dt@kernel.org, krzk+dt@kernel.org, robh@kernel.org,
hjc@rock-chips.com, mripard@kernel.org,
neil.armstrong@linaro.org, dmitry.baryshkov@oss.qualcomm.com,
knaerzche@gmail.com, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Andy Yan <andy.yan@rock-chips.com>
Subject: Re: [PATCH v4 0/7] Convert inno hdmi to drm bridge
Date: Thu, 01 May 2025 14:28:57 +0200 [thread overview]
Message-ID: <3554727.QJadu78ljV@diego> (raw)
In-Reply-To: <20250422070455.432666-1-andyshrk@163.com>
Hi Alex,
Am Dienstag, 22. April 2025, 09:04:39 Mitteleuropäische Sommerzeit schrieb Andy Yan:
> From: Andy Yan <andy.yan@rock-chips.com>
>
> When preparing to convert the current inno hdmi driver into a
> bridge driver, I found that there are several issues currently
> existing with it:
>
> 1. When the system starts up, the first time it reads the EDID, it
> will fail. This is because RK3036 HDMI DDC bus requires it's PHY's
> reference clock to be enabled first before normal DDC communication
> can be carried out.
>
> 2. The signal is unstable. When running the glmark2 test on the screen,
> there is a small probability of seeing some screen flickering.
> This is because The HSYNC/VSYNC polarity of rk3036 HDMI are controlled
> by GRF. This part is missing in the current driver.
>
> PATCH 1~6 are try to Fix Document in the dt-binding, then add the
> missing part in driver and dts.
> PATCH 7 converts the curren driver to drm bridge mode.
this looks all pretty okay to me, but could you check that your rk3128
keeps working and maybe provide a Tested-by?
Thanks a lot
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Andy Yan <andyshrk@163.com>, Alex Bee <knaerzche@gmail.com>
Cc: conor+dt@kernel.org, krzk+dt@kernel.org, robh@kernel.org,
hjc@rock-chips.com, mripard@kernel.org,
neil.armstrong@linaro.org, dmitry.baryshkov@oss.qualcomm.com,
knaerzche@gmail.com, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Andy Yan <andy.yan@rock-chips.com>
Subject: Re: [PATCH v4 0/7] Convert inno hdmi to drm bridge
Date: Thu, 01 May 2025 14:28:57 +0200 [thread overview]
Message-ID: <3554727.QJadu78ljV@diego> (raw)
In-Reply-To: <20250422070455.432666-1-andyshrk@163.com>
Hi Alex,
Am Dienstag, 22. April 2025, 09:04:39 Mitteleuropäische Sommerzeit schrieb Andy Yan:
> From: Andy Yan <andy.yan@rock-chips.com>
>
> When preparing to convert the current inno hdmi driver into a
> bridge driver, I found that there are several issues currently
> existing with it:
>
> 1. When the system starts up, the first time it reads the EDID, it
> will fail. This is because RK3036 HDMI DDC bus requires it's PHY's
> reference clock to be enabled first before normal DDC communication
> can be carried out.
>
> 2. The signal is unstable. When running the glmark2 test on the screen,
> there is a small probability of seeing some screen flickering.
> This is because The HSYNC/VSYNC polarity of rk3036 HDMI are controlled
> by GRF. This part is missing in the current driver.
>
> PATCH 1~6 are try to Fix Document in the dt-binding, then add the
> missing part in driver and dts.
> PATCH 7 converts the curren driver to drm bridge mode.
this looks all pretty okay to me, but could you check that your rk3128
keeps working and maybe provide a Tested-by?
Thanks a lot
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-05-01 12:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 7:04 [PATCH v4 0/7] Convert inno hdmi to drm bridge Andy Yan
2025-04-22 7:04 ` Andy Yan
2025-04-22 7:04 ` [PATCH v4 1/7] dt-bindings: display: rockchip,inno-hdmi: Fix Document of RK3036 compatible Andy Yan
2025-04-22 7:04 ` [PATCH v4 1/7] dt-bindings: display: rockchip, inno-hdmi: " Andy Yan
2025-04-22 7:04 ` [PATCH v4 1/7] dt-bindings: display: rockchip,inno-hdmi: " Andy Yan
2025-04-22 7:04 ` [PATCH v4 2/7] dt-bindings: display: rockchip,inno-hdmi: Document GRF for RK3036 HDMI Andy Yan
2025-04-22 7:04 ` [PATCH v4 2/7] dt-bindings: display: rockchip, inno-hdmi: " Andy Yan
2025-04-22 7:04 ` [PATCH v4 2/7] dt-bindings: display: rockchip,inno-hdmi: " Andy Yan
2025-04-22 7:04 ` [PATCH v4 3/7] drm/rockchip: inno-hdmi: Simplify error handler with dev_err_probe Andy Yan
2025-04-22 7:04 ` Andy Yan
2025-04-22 7:04 ` [PATCH v4 4/7] drm/rockchip: inno-hdmi: Fix video timing HSYNC/VSYNC polarity setting for rk3036 Andy Yan
2025-04-22 7:04 ` Andy Yan
2025-04-22 7:04 ` [PATCH v4 5/7] ARM: dts: rockchip: Add ref clk for hdmi Andy Yan
2025-04-22 7:04 ` Andy Yan
2025-04-22 7:04 ` [PATCH v4 6/7] Revert "ARM: dts: rockchip: drop grf reference from rk3036 hdmi" Andy Yan
2025-04-22 7:04 ` Andy Yan
2025-04-22 7:04 ` [PATCH v4 7/7] drm/rockchip: inno-hdmi: Convert to drm bridge Andy Yan
2025-04-22 7:04 ` Andy Yan
2025-05-01 12:28 ` Heiko Stübner [this message]
2025-05-01 12:28 ` [PATCH v4 0/7] Convert inno hdmi " Heiko Stübner
2025-05-03 14:42 ` Heiko Stübner
2025-05-03 14:42 ` Heiko Stübner
2025-05-04 16:16 ` Dmitry Baryshkov
2025-05-04 16:16 ` Dmitry Baryshkov
2025-05-09 1:58 ` Andy Yan
2025-05-09 1:58 ` Andy Yan
2025-05-09 15:19 ` Dmitry Baryshkov
2025-05-09 15:19 ` Dmitry Baryshkov
2025-05-04 10:59 ` (subset) " Heiko Stuebner
2025-05-04 10:59 ` Heiko Stuebner
2025-05-05 8:26 ` Heiko Stuebner
2025-05-05 8:26 ` Heiko Stuebner
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=3554727.QJadu78ljV@diego \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hjc@rock-chips.com \
--cc=knaerzche@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.