From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Eric Anholt <eric@anholt.net>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: maxime@cerno.tech, linux-rpi-kernel@lists.infradead.org,
f.fainelli@gmail.com, Stefan Wahren <stefan.wahren@i2se.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/vc4: Fix HDMI mode validation
Date: Fri, 27 Mar 2020 12:46:52 +0100 [thread overview]
Message-ID: <65a2d18ec2b901c6a89acc091cf9573a98fda75f.camel@suse.de> (raw)
In-Reply-To: <20200326122001.22215-1-nsaenzjulienne@suse.de>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
Hi Daniel,
On Thu, 2020-03-26 at 13:20 +0100, Nicolas Saenz Julienne wrote:
> Current mode validation impedes setting up some video modes which should
> be supported otherwise. Namely 1920x1200@60Hz.
>
> Fix this by lowering the minimum HDMI state machine clock to pixel clock
> ratio allowed.
>
> Fixes: 32e823c63e90 ("drm/vc4: Reject HDMI modes with too high of clocks")
> Reported-by: Stefan Wahren <stefan.wahren@i2se.com>
> Suggested-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
> Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Would it be possible for you to take this in for v5.7 (or as a fix for v5.6,
but it seems a little late)?
A device-tree patch I have to channel trough the SoC tree depends on this to
avoid regressions.
Regards,
Nicolas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-03-27 11:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 12:20 Nicolas Saenz Julienne
2020-03-26 12:32 ` Maxime Ripard
2020-03-26 17:19 ` Stefan Wahren
2020-03-26 17:21 ` Stefan Wahren
2020-03-26 17:36 ` Nicolas Saenz Julienne
2020-03-26 17:52 ` Stefan Wahren
2020-03-27 11:46 ` Nicolas Saenz Julienne [this message]
2020-03-27 12:40 ` Maxime Ripard
2020-03-27 12:40 ` Nicolas Saenz Julienne
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=65a2d18ec2b901c6a89acc091cf9573a98fda75f.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dave.stevenson@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maxime@cerno.tech \
--cc=stefan.wahren@i2se.com \
/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®