From: neil.armstrong@linaro.org
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de
Subject: Re: [PATCH re-send] drm/meson: add support for higher bandwidth HDMI DTDs
Date: Tue, 3 Nov 2026 09:53:39 +0100 [thread overview]
Message-ID: <2fdcea84-8b95-4ec1-af62-07e1803cb418@linaro.org> (raw)
In-Reply-To: <20261102212843.1213021-1-martin.blumenstingl@googlemail.com>
On 11/2/26 22:28, Martin Blumenstingl wrote:
> There's a report from a user with a DELL U3415W monitor and a Khadas
> VIM3 stating that 3440x1440@50Hz works but 3440x1440@60Hz doesn't.
> edid-decode Detailed Timing Descriptor (DTD) extract of that mode:
> DTD 1: 3440x1440 59.972616 Hz 43:18 88.819 kHz 319.750000 MHz
> Hfront 80 Hsync 32 Hback 48 Hpol P
> Vfront 28 Vsync 10 Vback 3 Vpol N
>
> Those high clock rates are currently not supported by the meson_vclk
> code as it limits the PLL OD (output divider) to a minimum of 2. The
> formula to calculate the clock internally is (ignoring fractional
> dividers):
> 319.750MHz * 10 * od = 24MHz * m
>
> With od = 2 this results in m = 266, which is outside the supported
> range of the PLL on G12A SoCs (the driver limits m to 106..247).
> Using od = 2 results in m = 133, which is supported.
>
> Allow the driver to pick OD = 1 to gain support for modes such as
> 3440x1440@60Hz.
>
> Link: https://forum.khadas.com/t/can-not-set-display-resolution-to-3440x1440-for-dell-monitor/26271/12
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> ---
> Re-send of [0] which seems to have slipped through.
>
>
> [0] https://lore.kernel.org/linux-amlogic/20260109204836.790096-1-martin.blumenstingl@googlemail.com/
>
>
> drivers/gpu/drm/meson/meson_vclk.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/meson/meson_vclk.c b/drivers/gpu/drm/meson/meson_vclk.c
> index dfe0c28a0f05..c0be0b7655bf 100644
> --- a/drivers/gpu/drm/meson/meson_vclk.c
> +++ b/drivers/gpu/drm/meson/meson_vclk.c
> @@ -700,8 +700,8 @@ static bool meson_hdmi_pll_find_params(struct meson_drm *priv,
> unsigned int *frac,
> unsigned int *od)
> {
> - /* Cycle from /16 to /2 */
> - for (*od = 16 ; *od > 1 ; *od >>= 1) {
> + /* Cycle from /16 to /1 */
> + for (*od = 16 ; *od > 0 ; *od >>= 1) {
> *m = meson_hdmi_pll_get_m(priv, freq * *od);
> if (!*m)
> continue;
> @@ -750,7 +750,7 @@ static void meson_hdmi_pll_generic_set(struct meson_drm *priv,
> /* OD2 goes to the PHY, and needs to be *10, so keep OD3=1 */
> od3 = 1;
> if (od < 4) {
> - od1 = 2;
> + od1 = od;
> od2 = 1;
> } else {
> od2 = od / 4;
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Thanks,
Neil
prev parent reply other threads:[~2026-11-03 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 21:28 Martin Blumenstingl
2026-11-03 8:53 ` neil.armstrong [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=2fdcea84-8b95-4ec1-af62-07e1803cb418@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.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
all inboxes | Powered by JetHome®