From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 4/4] drm/i915: set pm._irqs_disabled at IRQ init time
Date: Mon, 14 Jul 2014 19:26:33 +0200 [thread overview]
Message-ID: <20140714172633.GH15237@phenom.ffwll.local> (raw)
In-Reply-To: <CA+gsUGQC=0gKxkzD7BF0r2tDJsD71gNKojxR0poRofifqqaLGQ@mail.gmail.com>
On Mon, Jul 14, 2014 at 12:23:11PM -0300, Paulo Zanoni wrote:
> 2014-06-20 13:29 GMT-03:00 Jesse Barnes <jbarnes@virtuousgeek.org>:
> > Before we've installed the handler, we can set this and avoid confusing
> > init code that then thinks IRQs are enabled and spews complaints
> > everywhere.
>
> But then at some point the DRM layer will call our IRQ init callbacks,
> which will initalize the interrupts but leave irqs_disabled as true,
> which will also confuse some code somewhere at some point. And it will
> only be set to false after we {runtime,}-suspend/resume.
The drm irq stuff is _strictly_ a helper library, at least for modesetting
drivers. Which means it will never call our callbacks on its own.
> This is why I had kept the runtime PM code only used by the runtime PM
> stuff. Recently we tried to reuse the runtime PM interrupt code at
> other contexts, got regressions and now we're fixing the regressions
> using duct tape... Maybe the best approach would be to revert some
> patches...
Those patches where for soix, so feature work.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-07-14 17:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 16:29 [PATCH 1/4] drm/i915: don't warn if IRQs are disabled when shutting down display IRQs Jesse Barnes
2014-06-20 16:29 ` [PATCH 2/4] drm/i915: add helper for checking whether IRQs are enabled Jesse Barnes
2014-07-14 15:06 ` Paulo Zanoni
2014-07-14 15:19 ` Paulo Zanoni
2014-07-14 15:58 ` Jesse Barnes
2014-06-20 16:29 ` [PATCH 3/4] drm/i915: drop runtime PM get/put pair around DP detect Jesse Barnes
2014-07-14 15:11 ` Paulo Zanoni
2014-06-20 16:29 ` [PATCH 4/4] drm/i915: set pm._irqs_disabled at IRQ init time Jesse Barnes
2014-07-14 15:23 ` Paulo Zanoni
2014-07-14 17:26 ` Daniel Vetter [this message]
2014-07-14 17:47 ` Paulo Zanoni
2014-07-14 20:25 ` Jesse Barnes
2014-06-20 16:39 ` [PATCH] drm/i915: clear pm._irqs_disabled field after installing IRQs Jesse Barnes
2014-06-20 18:57 ` [PATCH] drm/i915: mark IRQs as disabled on unload Jesse Barnes
2014-07-17 8:27 ` Daniel Vetter
2014-07-07 21:48 ` [PATCH 1/4] drm/i915: don't warn if IRQs are disabled when shutting down display IRQs Paulo Zanoni
2014-07-07 21:53 ` Jesse Barnes
2014-07-14 14:56 ` Paulo Zanoni
2014-07-14 17:34 ` Daniel Vetter
2014-07-16 21:19 ` Paulo Zanoni
2014-07-17 8:06 ` Daniel Vetter
2014-07-17 13:42 ` Paulo Zanoni
2014-07-17 16:55 ` Daniel Vetter
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=20140714172633.GH15237@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=przanoni@gmail.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