From: Andy Yan <andy.yan@rock-chips.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: algea.cao@rock-chips.com, Sandy Huang <hjc@rock-chips.com>,
dri-devel@lists.freedesktop.org,
Michael Riesch <michael.riesch@wolfvision.net>,
kernel@pengutronix.de
Subject: Re: [PATCH 0/2] drm/rockchip: dw_hdmi: Add 4k@30 support
Date: Sat, 3 Sep 2022 15:53:56 +0800 [thread overview]
Message-ID: <bb8152e7-8c52-090e-1a41-953f789eaf15@rock-chips.com> (raw)
In-Reply-To: <20220824070742.GA28387@pengutronix.de>
Hi Sascha:
On 8/24/22 15:07, Sascha Hauer wrote:
> Hi Andy Et al.,
>
> On Mon, Aug 22, 2022 at 05:20:15PM +0200, Sascha Hauer wrote:
>> This series adds support for 4k@30 to the rockchip HDMI controller. This
>> has been tested on a rk3568 rock3a board. It should be possible to add
>> 4k@60 support the same way, but it doesn't work for me, so let's add
>> 4k@30 as a first step.
> I tried adding 4k@60 support the same way, just by adding the missing
> fields for 600MHz in the PLL/phy settings. I get a picture on the
> screen, but it's not very stable: The monitor often gets black, scans
> through the different HDMI inputs and then syncs again. Also when I
> re-plug the cable while weston is running I won't get any picture
> anymore (the same works fine with lower resolutions). I also tried
> the Rock3a 4.19 Kernel which is based on the Rockchip Kernel and I saw
> similar problems there.
>
> Do you have an idea what could go wrong there?
4K HDMI output from hdmi need very carefully tuning of HDMI PHY and PLL.
I can make sure that HDMI 4K output on rk3399/rk3288/rk356x are work
fine with our
vendor kernel, but the upstream kernel is only can run at 1080p output,
I have tested
on rk3399 and rk3568-evb1[0]
I am not familiar with hdmi tuning, so I am sorry i can't give detail
idea about this issue,
maybe a more carefully comparison with hdmi driver and pll
configuration between upstream kernel and rockchip 4.19 kernel?
I think you have rk356x evb board, do you have a detail test about 4K
HDMI output with this board? If you have issue about 4k hdmi output
on this board with rockchip 4.19 kernel, we can help to figure it out.
Anyway, I loop Algea to the list, he is maintaining our hdmi
development, but I am sorry to say that he is
also very busy😅
I don't have a rock3a, so I can't confirm the problem you described on
4.19 kernel.
[0]https://patchwork.kernel.org/project/linux-rockchip/patch/20220225075150.2729401-16-s.hauer@pengutronix.de/
>
> Sascha
>
>
prev parent reply other threads:[~2022-09-03 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 15:20 [PATCH 0/2] drm/rockchip: dw_hdmi: Add 4k@30 support Sascha Hauer
2022-08-22 15:20 ` [PATCH 1/2] drm/rockchip: dw_hdmi: relax mode_valid hook Sascha Hauer
2022-08-24 16:07 ` Robin Murphy
2022-08-25 11:40 ` Sascha Hauer
2022-09-22 13:09 ` Robin Murphy
2022-08-22 15:20 ` [PATCH 2/2] drm/rockchip: dw_hdmi: Add support for 4k@30 resolution Sascha Hauer
2022-08-24 5:43 ` [PATCH 0/2] drm/rockchip: dw_hdmi: Add 4k@30 support Michael Riesch
2022-08-24 7:10 ` Sascha Hauer
2022-08-24 7:07 ` Sascha Hauer
2022-09-03 7:53 ` Andy Yan [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=bb8152e7-8c52-090e-1a41-953f789eaf15@rock-chips.com \
--to=andy.yan@rock-chips.com \
--cc=algea.cao@rock-chips.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hjc@rock-chips.com \
--cc=kernel@pengutronix.de \
--cc=michael.riesch@wolfvision.net \
--cc=s.hauer@pengutronix.de \
/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).