From: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
To: linux-samsung-soc@vger.kernel.org
Cc: dri-devel@lists.freedesktop.org, m.szyprowski@samsung.com
Subject: Re: [RFC] drm/exynos: g2d: fix runtime PM
Date: Fri, 23 Sep 2016 17:15:48 +0200 [thread overview]
Message-ID: <57E54724.5030803@math.uni-bielefeld.de> (raw)
In-Reply-To: <1474643436-24844-2-git-send-email-tjakobi@math.uni-bielefeld.de>
Tobias Jakobi wrote:
> The commit b05984e21a7e000bf5074ace00d7a574944b2c16 broke
> operation of the G2D. After this commit the following
> happens.
> - exynos_g2d_exec_ioctl() prepares a runqueue node and
> calls g2d_exec_runqueue()
> - g2d_exec_runqueue() calls g2d_dma_start() which gets
> runtime PM sync
> - runtime PM calls g2d_runtime_resume()
> - g2d_runtime_resume() calls g2d_exec_runqueue()
>
> Luckily for us this doesn't really loop, but creates a
> mutex lockup, which the kernel even predicts.
>
> Anyway, we fix this by reintroducing dedicated sleep
> operations again, and only letting runtime PM control
> the gate clock.
>
> This is not enough to fix the issue though.
> - We switch runtime PM to autosuspend. Currently clocks get
> disabled, and then re-enabled again in the runqueue worker
> when a node is completed and the next is started.
> With the upcoming introduction of IOMMU runtime PM this
> situations gets worse, since now also the IOMMU goes
> through a disable/enable cycle before the next node is
> started.
> - We consolidate all runtime PM management to the runqueue
> worker.
> - We introduce g2d_wait_finish() which waits until the currently
> processed runqueue node is finished.
> If this takes too long, the engine is forcibly reset. This
> is necessary to properly close the driver in case the engine
> should hang with read/write access to some area of memory.
> In this situation we can't properly unmap GEM/userptr
> objects, since this might create a pagefault.
> - Sleep suspend issues a suspend of the runqueue and then calls
> g2d_wait_finished(), which returns the engine in the idle state.
This should read 'g2d_wait_finish()'.
> The current runqueue node gets completed, all other queued
> nodes stay in the queue. There is no hardware state that
> needs to be retained.
> - Sleep resume just pokes the runqueue worker, which, should
> something be in queue, continues its work, or just exits.
>
> Signed-off-by: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
<snip>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-09-23 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 15:10 [RFC] drm/exynos: g2d: runpm fixing attempt Tobias Jakobi
2016-09-23 15:10 ` [RFC] drm/exynos: g2d: fix runtime PM Tobias Jakobi
2016-09-23 15:15 ` Tobias Jakobi [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=57E54724.5030803@math.uni-bielefeld.de \
--to=tjakobi@math.uni-bielefeld.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.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 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).