From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Rob Clark <robdclark@gmail.com>, Doug Anderson <dianders@chromium.org>
Cc: Sankeerth Billakanti <quic_sbillaka@quicinc.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@linux.ie>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
freedreno <freedreno@lists.freedesktop.org>
Subject: Re: [RFC PATCH] drm/edid: Make 144 Hz not preferred on Sharp LQ140M1JW46
Date: Thu, 28 Jul 2022 10:34:19 -0700 [thread overview]
Message-ID: <5c8ca71c-5f0b-d5f5-9f16-e312dec0d01b@quicinc.com> (raw)
In-Reply-To: <CAF6AEGv_Vikf80v-7ccz90fvGPrk5pV1tOxRoWKxKHYuEW8=aA@mail.gmail.com>
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.
>>>>
>>>> The argument here is that this is a laptop panel and on a laptop we
>>>> know power will always be a concern. Presumably even if someone using
>>>> this panel wanted to use 144 Hz for some use cases they would only do
>>>> so dynamically and would still want the default to be 60 Hz.
>>>>
>>>> Let's change the default to 60 Hz using a standard quirk.
>>>>
>>>> Signed-off-by: Douglas Anderson <dianders@chromium.org>
>>>
>>> Yes, we were aware that 144Hz was getting picked. We found that while
>>> debugging the screen corruption issue.
>>>
>>> Well, yes power would be less with 60Hz but so will be the performance.
>>
>> What performance specifically will be less with 60 Hz? In general the
>> sc7280 CPU is a bit memory-bandwidth constrained and the LCD refresh
>> from memory is a non-trivial part of that. Reducing to 60 Hz will
>> relieve some of the memory bandwidth pressure and will actually allow
>> tasks on the CPU to run _faster_. I guess the downside is that some
>> animations might be a little less smooth...
>
> I guess he is referring to something that is vblank sync'd running
> faster than 60fps.
>
> but OTOH it is a bit of a waste for fbcon to be using 144Hz. And
> there are enough android games that limit themselves to 30fps to save
> your "phone" battery. So it seems a lot more sane to default to 60Hz
> and let userspace that knows it wants more pick the 144Hz rate when
> needed.
>
> BR,
> -R
Yes i was referring to vblank synced apps.
>
>>
>>
>>> The test teams have been validating with 144Hz so far so we are checking
>>> internally with the team whether its OKAY to goto 60Hz now since that
>>> kind of invalidates the testing they have been doing.
>>
>> You're worried that the panel itself won't work well at 60 Hz, or
>> something else about the system won't? The whole system in general
>> needs to work well with 60 Hz displays and I expect them to be much
>> more common than 144 Hz displays. Quite honestly if switching to 60 Hz
>> uncovers a problem that would be a huge benefit of landing this patch
>> because it would mean we'd find it now rather than down the road when
>> someone hooks up a different panel.
I was worried that it will invalidate the testing they did so far but
since you have confirmed that you would prefer 60Hz to be more
thoroughly tested than 144Hz, I have informed the internal teams of this
change and given the heads up.
You can have my R-b for this change,
Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
I would also wait to see if others have different thought about this.
>>
>> -Doug
next prev parent reply other threads:[~2022-07-28 17:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 22:23 [RFC PATCH] drm/edid: Make 144 Hz not preferred on Sharp LQ140M1JW46 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 [this message]
2022-07-28 21:18 ` Doug Anderson
2022-07-29 7:51 ` Maxime Ripard
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=5c8ca71c-5f0b-d5f5-9f16-e312dec0d01b@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=airlied@linux.ie \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).