From: Michael Riesch <michael.riesch@wolfvision.net>
To: Sascha Hauer <s.hauer@pengutronix.de>, dri-devel@lists.freedesktop.org
Cc: "Sandy Huang" <hjc@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>,
kernel@pengutronix.de,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>
Subject: Re: [PATCH 0/2] drm/rockchip: dw_hdmi: Add 4k@30 support
Date: Wed, 24 Aug 2022 07:43:03 +0200 [thread overview]
Message-ID: <ef70b8b7-c1ff-a6b9-077b-83ea48c66c24@wolfvision.net> (raw)
In-Reply-To: <20220822152017.1523679-1-s.hauer@pengutronix.de>
Hi Sascha,
Can you Cc: linux-rockchip list to get more feedback?
On 8/22/22 17:20, 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.
>
> Sascha
>
> Sascha Hauer (2):
> drm/rockchip: dw_hdmi: relax mode_valid hook
> drm/rockchip: dw_hdmi: Add support for 4k@30 resolution
Great stuff, thanks!
On a Radxa ROCK3 Model A with a HP 27f 4k monitor
Tested-by: Michael Riesch <michael.riesch@wolfvision.net>
Best regards,
Michael
>
> drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next parent reply other threads:[~2022-08-24 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220822152017.1523679-1-s.hauer@pengutronix.de>
2022-08-24 5:43 ` Michael Riesch [this message]
2022-08-24 7:10 ` [PATCH 0/2] drm/rockchip: dw_hdmi: Add 4k@30 support Sascha Hauer
2022-08-24 12:03 ` Dan Johansen
[not found] ` <20220822152017.1523679-2-s.hauer@pengutronix.de>
2022-08-24 16:07 ` [PATCH 1/2] drm/rockchip: dw_hdmi: relax mode_valid hook Robin Murphy
2022-08-25 11:40 ` Sascha Hauer
2022-09-22 13:09 ` Robin Murphy
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=ef70b8b7-c1ff-a6b9-077b-83ea48c66c24@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=kernel@pengutronix.de \
--cc=linux-rockchip@lists.infradead.org \
--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).