From: Maxime Ripard <maxime@cerno.tech>
To: Doug Anderson <dianders@chromium.org>
Cc: Abhinav Kumar <quic_abhinavk@quicinc.com>,
Rob Clark <robdclark@gmail.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
freedreno <freedreno@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
Sankeerth Billakanti <quic_sbillaka@quicinc.com>
Subject: Re: [RFC PATCH] drm/edid: Make 144 Hz not preferred on Sharp LQ140M1JW46
Date: Fri, 29 Jul 2022 09:51:18 +0200 [thread overview]
Message-ID: <20220729075118.ofnpk52tk4usm3n3@penduick> (raw)
In-Reply-To: <CAD=FV=UGYV1mZenDCRrbpC+gpE12-Uis7fm_=H3PeEjK=t36yA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2848 bytes --]
On Thu, Jul 28, 2022 at 02:18:38PM -0700, Doug Anderson wrote:
> Hi,
>
> On Thu, Jul 28, 2022 at 10:34 AM Abhinav Kumar
> <quic_abhinavk@quicinc.com> wrote:
> >
> > Hi Rob and Doug
> >
> > On 7/22/2022 10:36 AM, Rob Clark wrote:
> > > On Fri, Jul 22, 2022 at 9:48 AM Doug Anderson <dianders@chromium.org> wrote:
> > >>
> > >> Hi,
> > >>
> > >> On Fri, Jul 22, 2022 at 9:37 AM Abhinav Kumar <quic_abhinavk@quicinc.com> wrote:
> > >>>
> > >>> + sankeerth
> > >>>
> > >>> Hi Doug
> > >>>
> > >>> On 7/21/2022 3:23 PM, Douglas Anderson wrote:
> > >>>> The Sharp LQ140M1JW46 panel is on the Qualcomm sc7280 CRD reference
> > >>>> board. This panel supports 144 Hz and 60 Hz. In the EDID, the 144 Hz
> > >>>> mode is listed first and thus is marked preferred. The EDID decode I
> > >>>> ran says:
> > >>>>
> > >>>> First detailed timing includes the native pixel format and preferred
> > >>>> refresh rate.
> > >>>>
> > >>>> ...
> > >>>>
> > >>>> Detailed Timing Descriptors:
> > >>>> DTD 1: 1920x1080 143.981 Hz 16:9 166.587 kHz 346.500 MHz
> > >>>> Hfront 48 Hsync 32 Hback 80 Hpol N
> > >>>> Vfront 3 Vsync 5 Vback 69 Vpol N
> > >>>> DTD 2: 1920x1080 59.990 Hz 16:9 69.409 kHz 144.370 MHz
> > >>>> Hfront 48 Hsync 32 Hback 80 Hpol N
> > >>>> Vfront 3 Vsync 5 Vback 69 Vpol N
> > >>>>
> > >>>> I'm proposing here that the above is actually a bug and that the 60 Hz
> > >>>> mode really should be considered preferred by Linux.
> >
> > Its a bit tricky to say that this is a bug but I think we can certainly
> > add here that for an internal display we would have ideally had the
> > lower resolution first to indicate it as default.
>
> Yeah, it gets into the vagueness of the EDID spec in general. As far
> as I can find it's really up to the monitor to decide by what means it
> chooses the "preferred" refresh rate if the monitor can support many.
> Some displays may decide that the normal rate is "preferred" and some
> may decide that the high refresh rate is "preferred". Neither display
> is "wrong" per say, but it's nice to have some consistency here and to
> make it so that otherwise "dumb" userspace will get something
> reasonable by default. I'll change it to say:
>
> While the EDID spec appears to allow a display to use any criteria for
> picking which refresh mode is "preferred" or "optimal", that vagueness
> is a bit annoying. From Linux's point of view let's choose the 60 Hz
> one as the default.
And if we start making that decision, it should be for all panels with a
similar constraint, so most likely handled by the core, and the new
policy properly documented.
Doing that just for a single panel is weird.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-07-29 7:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 22:23 Douglas Anderson
2022-07-22 16:37 ` Abhinav Kumar
2022-07-22 16:48 ` Doug Anderson
2022-07-22 17:36 ` Rob Clark
2022-07-28 17:34 ` Abhinav Kumar
2022-07-28 21:18 ` Doug Anderson
2022-07-29 7:51 ` Maxime Ripard [this message]
2022-07-29 14:50 ` Doug Anderson
2022-07-29 16:41 ` Maxime Ripard
2022-07-29 19:57 ` Doug Anderson
2022-08-15 6:45 ` Maxime Ripard
2022-08-17 23:45 ` Doug Anderson
2022-08-18 10:31 ` Jani Nikula
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=20220729075118.ofnpk52tk4usm3n3@penduick \
--to=maxime@cerno.tech \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_sbillaka@quicinc.com \
--cc=robdclark@gmail.com \
--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®