From: Brian Norris <briannorris@chromium.org>
To: "Michel Dänzer" <michel.daenzer@mailbox.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
kernelci-results@groups.io, bot@kernelci.org,
Jonas Karlman <jonas@kwiboo.se>,
Robert Foss <robert.foss@linaro.org>,
Douglas Anderson <dianders@chromium.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Mark Brown <broonie@kernel.org>,
Sean Paul <seanpaul@chromium.org>,
dri-devel@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
gtucker@collabora.com, linux-arm-kernel@lists.infradead.org,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
Subject: Re: renesas/master bisection: igt-kms-rockchip.kms_vblank.pipe-A-wait-forked on rk3399-gru-kevin
Date: Thu, 5 Jan 2023 17:43:52 -0800 [thread overview]
Message-ID: <Y7d82A9FrHDraRYB@google.com> (raw)
In-Reply-To: <Y7dyh1AkJRZnf+Dq@google.com>
On Thu, Jan 05, 2023 at 04:59:55PM -0800, Brian Norris wrote:
> On Wed, Jan 04, 2023 at 10:11:46AM +0100, Michel Dänzer wrote:
> > On 1/4/23 03:11, Brian Norris wrote:
> > > On Tue, Jan 03, 2023 at 07:04:00PM +0100, Michel Dänzer wrote:
> > >> On 12/21/22 23:02, Brian Norris wrote:
> > >>> 3. leave vblank enabled even in the presence of PSR
> > >
> > > I'm leaning toward this.
> >
> > If this means vblank interrupts will arrive as expected even while in PSR, that may be the ideal solution indeed.
>
> Yes. And I think I have a working patchset for this now. It passes all
> the igt-gpu-tools/kms_vblank tests for me now, and I don't think it
> causes any other issues. I'll send it out shortly, after a bit more
> testing.
For the record, that's here:
https://lore.kernel.org/lkml/20230105174001.2.Ic07cba4ab9a7bd3618a9e4258b8f92ea7d10ae5a@changeid/
I didn't CC everyone who got this report. In included a:
Reported-by: "kernelci.org bot" <bot@kernelci.org>
even though it didn't really bisect the right thing. Let me know if
there's a different/better way to give credit.
Brian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-01-06 1:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6398848e.170a0220.f8e8e.d44f@mx.google.com>
2022-12-13 16:51 ` renesas/master bisection: igt-kms-rockchip.kms_vblank.pipe-A-wait-forked on rk3399-gru-kevin Mark Brown
2022-12-14 10:06 ` Geert Uytterhoeven
2022-12-14 12:55 ` Guillaume Tucker
2022-12-14 13:50 ` Mark Brown
2022-12-14 14:27 ` Guillaume Tucker
2022-12-14 14:54 ` Mark Brown
2022-12-14 14:03 ` Geert Uytterhoeven
2022-12-14 14:16 ` Guillaume Tucker
2022-12-14 14:39 ` Mark Brown
2022-12-14 15:02 ` Geert Uytterhoeven
2022-12-14 15:06 ` Geert Uytterhoeven
2022-12-15 3:04 ` Brian Norris
2022-12-21 22:02 ` Brian Norris
2023-01-03 18:04 ` Michel Dänzer
2023-01-04 2:11 ` Brian Norris
2023-01-04 9:11 ` Michel Dänzer
2023-01-06 0:59 ` Brian Norris
2023-01-06 1:43 ` Brian Norris [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=Y7d82A9FrHDraRYB@google.com \
--to=briannorris@chromium.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gtucker@collabora.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernelci-results@groups.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=michel.daenzer@mailbox.org \
--cc=neil.armstrong@linaro.org \
--cc=robert.foss@linaro.org \
--cc=seanpaul@chromium.org \
/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).