From: Heiko Stuebner <heiko@sntech.de>
To: dri-devel@lists.freedesktop.org
Cc: David Airlie <airlied@linux.ie>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
LKML <linux-kernel@vger.kernel.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Steven Price <steven.price@arm.com>
Subject: Re: [PATCH 1/2] panfrost: Make sure GPU is powered on when reading GPU_LATEST_FLUSH_ID
Date: Thu, 11 Jun 2020 11:05:37 +0200 [thread overview]
Message-ID: <4351778.0rgn4tIXvQ@phil> (raw)
In-Reply-To: <20200611085900.49740-1-tomeu.vizoso@collabora.com>
Am Donnerstag, 11. Juni 2020, 10:58:43 CEST schrieb Tomeu Vizoso:
> Bifrost devices do support the flush reduction feature, so on first job
> submit we were trying to read the register while still powered off.
>
> If the GPU is powered off, the feature doesn't bring any benefit, so
> don't try to read.
>
> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
on a PX30-board (sibling of rk3326) with a 720x1280 panel and
glmark2 running all tests
Tested-by: Heiko Stuebner <heiko@sntech.de>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: dri-devel@lists.freedesktop.org
Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>,
LKML <linux-kernel@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
Steven Price <steven.price@arm.com>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
Subject: Re: [PATCH 1/2] panfrost: Make sure GPU is powered on when reading GPU_LATEST_FLUSH_ID
Date: Thu, 11 Jun 2020 11:05:37 +0200 [thread overview]
Message-ID: <4351778.0rgn4tIXvQ@phil> (raw)
In-Reply-To: <20200611085900.49740-1-tomeu.vizoso@collabora.com>
Am Donnerstag, 11. Juni 2020, 10:58:43 CEST schrieb Tomeu Vizoso:
> Bifrost devices do support the flush reduction feature, so on first job
> submit we were trying to read the register while still powered off.
>
> If the GPU is powered off, the feature doesn't bring any benefit, so
> don't try to read.
>
> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
on a PX30-board (sibling of rk3326) with a 720x1280 panel and
glmark2 running all tests
Tested-by: Heiko Stuebner <heiko@sntech.de>
next prev parent reply other threads:[~2020-06-11 9:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 8:58 [PATCH 1/2] panfrost: Make sure GPU is powered on when reading GPU_LATEST_FLUSH_ID Tomeu Vizoso
2020-06-11 8:58 ` Tomeu Vizoso
2020-06-11 8:58 ` [PATCH 2/2] panfrost: Add compatible string for bifrost Tomeu Vizoso
2020-06-11 8:58 ` Tomeu Vizoso
2020-06-11 9:07 ` Heiko Stuebner
2020-06-11 9:07 ` Heiko Stuebner
2020-06-19 9:00 ` Steven Price
2020-06-19 9:00 ` Steven Price
2020-10-05 6:44 ` Tomeu Vizoso
2020-10-05 6:44 ` Tomeu Vizoso
2020-10-05 7:06 ` Tomeu Vizoso
2020-10-05 7:06 ` Tomeu Vizoso
2020-06-11 9:05 ` Heiko Stuebner [this message]
2020-06-11 9:05 ` [PATCH 1/2] panfrost: Make sure GPU is powered on when reading GPU_LATEST_FLUSH_ID Heiko Stuebner
2020-06-11 14:11 ` Alyssa Rosenzweig
2020-06-11 14:11 ` Alyssa Rosenzweig
2020-06-19 8:52 ` Steven Price
2020-06-19 8:52 ` Steven Price
2020-08-07 19:47 ` Rob Herring
2020-08-07 19:47 ` Rob Herring
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=4351778.0rgn4tIXvQ@phil \
--to=heiko@sntech.de \
--cc=airlied@linux.ie \
--cc=alyssa.rosenzweig@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steven.price@arm.com \
--cc=tomeu.vizoso@collabora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.