From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 2/2] drm/i915: check for more ASLC interrupts
Date: Tue, 17 Sep 2013 18:08:16 +0200 [thread overview]
Message-ID: <20130917160816.GQ32145@phenom.ffwll.local> (raw)
In-Reply-To: <87pps7lb4l.fsf@intel.com>
On Tue, Sep 17, 2013 at 06:29:46PM +0300, Jani Nikula wrote:
> On Tue, 17 Sep 2013, Paulo Zanoni <przanoni@gmail.com> wrote:
> > From: Paulo Zanoni <paulo.r.zanoni@intel.com>
> >
> > Sometimes I see the "non asle set request??" message on my Haswell
> > machine, so I decided to get the spec and see if some bits are missing
> > from the mask. We do have some bits missing from the mask, so this
> > patch adds them, and the corresponding code to print "unsupported"
> > messages just like we do with the other bits we don't support.
> >
> > But I still see the "non asle set request??" message on my machine :(
> >
> > Also use the proper ASLC name to indicate the registers we're talking
> > about.
> >
> > v2: - Properly set the new FAILED bits
> > - Rename the old FAILED bits
> > - Print everything we don't support
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Queued for -next, thanks for the patch.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-09-17 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 14:14 [PATCH 1/2] drm/i915: WARN is the DP aux read or write is too big Paulo Zanoni
2013-09-17 14:14 ` [PATCH 2/2] drm/i915: check for more ASLC interrupts Paulo Zanoni
2013-09-17 15:29 ` Jani Nikula
2013-09-17 16:08 ` Daniel Vetter [this message]
2013-09-17 15:15 ` [PATCH 1/2] drm/i915: WARN is the DP aux read or write is too big Jani Nikula
2013-09-17 15:23 ` 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=20130917160816.GQ32145@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=paulo.r.zanoni@intel.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