From: Nicolas Frattaroli <frattaroli.nicolas@gmail.com>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kever Yang <kever.yang@rock-chips.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH] rockchip: rk3328: Set VOP QoS to high priority
Date: Wed, 04 Jan 2023 12:30:10 +0100 [thread overview]
Message-ID: <7408445.TZXBHSJsY6@archbook> (raw)
In-Reply-To: <CAMty3ZBg7aJm64fu-NB7622xu6FZf36uGvQxtmW20-Wi95y2Dw@mail.gmail.com>
On Mittwoch, 4. Januar 2023 12:21:35 CET Jagan Teki wrote:
> On Sat, Jul 23, 2022 at 10:31 PM Nicolas Frattaroli
> <frattaroli.nicolas@gmail.com> wrote:
> >
> > The default priority for the quality of service for the video
> > output results in unsightly glitches on the output whenever there
> > is memory pressure on the system, which happens a lot.
> >
> > This sets the VOP QoS to high priority, which fixes this issue.
>
> Can you point out how it reproduces?
>
> Jagan.
>
To reproduce, run something like glmark2-es2-drm while also
running stress --vm 4, you should see glitchy output on the
HDMI on rk3328.
A more real-world test is to just run a desktop environment,
you will see horizontal lines through the screen the moment
you start typing in e.g. a terminal emulator.
Cheers,
Nicolas Frattaroli
next prev parent reply other threads:[~2023-01-04 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 11:28 [PATCH] rockchip: rk3328: Set VOP QoS to high priority Nicolas Frattaroli
2022-10-21 12:30 ` Nicolas Frattaroli
2023-01-04 11:18 ` Nicolas Frattaroli
2023-01-04 11:21 ` Jagan Teki
2023-01-04 11:30 ` Nicolas Frattaroli [this message]
2023-01-04 12:04 ` Philipp Tomsich
2023-01-05 2:19 ` Kever Yang
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=7408445.TZXBHSJsY6@archbook \
--to=frattaroli.nicolas@gmail.com \
--cc=jagan@amarulasolutions.com \
--cc=kever.yang@rock-chips.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.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