mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Stefan Schake <stschake@gmail.com>,
	David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: linux-rpi-kernel@lists.infradead.org, Stefan Schake <stschake@gmail.com>
Subject: Re: [PATCH] drm/vc4: Move IRQ enable to PM path
Date: Wed, 03 Jan 2018 16:28:12 -0800	[thread overview]
Message-ID: <87mv1uv55v.fsf@anholt.net> (raw)
In-Reply-To: <1514563543-32511-1-git-send-email-stschake@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 873 bytes --]

Stefan Schake <stschake@gmail.com> writes:

> We were calling enable_irq on bind, where it was already enabled previously
> by the IRQ helper. Additionally, dev->irq is not set correctly until after
> postinstall and so was always zero here, triggering a warning in 4.15.
> Fix both by moving the enable to the power management resume path, where we
> know there was a previous disable invocation during suspend.
>
> Fixes: 253696ccd613 ("drm/vc4: Account for interrupts in flight")
> Signed-off-by: Stefan Schake <stschake@gmail.com>
> ---
> I tested replacing the enable/disable dance with just synchronize_irq,
> but that only made the original kernel OOPS more sporadic.

Reviewed and applied.  Thanks!

Somewhere on the infinite TODO list is to stop using the DRM IRQ helpers
and just install our IRQ handler on our own, which I think would have
avoided this trouble.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      parent reply	other threads:[~2018-01-04  0:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 16:05 Stefan Schake
2017-12-30 20:03 ` Stefan Wahren
2018-01-04  0:28 ` Eric Anholt [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=87mv1uv55v.fsf@anholt.net \
    --to=eric@anholt.net \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=stschake@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

Powered by JetHome