From: Daniel Vetter <daniel@ffwll.ch>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Meyer <thomas@m3y3r.de>
Subject: Re: Linux 3.16-rc2
Date: Tue, 8 Jul 2014 10:35:05 +0200 [thread overview]
Message-ID: <20140708083505.GQ17271@phenom.ffwll.local> (raw)
In-Reply-To: <alpine.LNX.2.00.1407080013030.1655@pobox.suse.cz>
On Tue, Jul 08, 2014 at 12:15:31AM +0200, Jiri Kosina wrote:
> On Mon, 7 Jul 2014, Chris Wilson wrote:
>
> > > > this patch on top of v3.16-rc3-62-gd92a333 makes the resume from ram
> > > > regression go away on my machine:
> > >
> > > Hm, we could conditionalize this hack on IS_G4X ... Chris, thoughts?
> >
> > As different machines favour different w/a, I think the issue is mostly
> > timing related. It could be sequence of register writes, but we tried
> > different orders early on. The next experiment I guess would be to
> > insert small delays between each write to see if that helps. Or to write
> > each register twice.
>
> I actually tried to introduce rather large delays between individual
> I915_WRITE() calls in the ring initialization sequence a couple weeks ago
> already, but it resulted in complete machine lockup (which is worse than
> my usual symptoms) during resume. Therefore I probably lack the knowledge
> of internal workings of the HW that would allow me to guess what the
> reasonable timeout value should be.
Have you used msleep or udelay? The latter just spins the cpu and might be
less dangerous.
-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-08 8:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+55aFxdAhp-esuGiY4VEugiiwcMJgg1r6fPiR9Fb+HOz_5tLg@mail.gmail.com>
2014-06-23 23:07 ` Linux 3.16-rc2 Thomas Meyer
2014-06-24 11:06 ` Jani Nikula
2014-06-24 11:57 ` Chris Wilson
2014-06-24 12:24 ` Thomas Meyer
2014-06-24 12:27 ` Chris Wilson
2014-06-30 10:02 ` Pavel Machek
2014-06-30 10:09 ` Chris Wilson
2014-07-02 16:18 ` Thomas Meyer
2014-07-07 15:16 ` Daniel Vetter
2014-07-07 15:32 ` Jiri Kosina
2014-07-07 16:04 ` Chris Wilson
2014-07-07 22:15 ` Jiri Kosina
2014-07-08 8:35 ` Daniel Vetter [this message]
2014-07-08 8:59 ` Chris Wilson
2014-07-08 12:46 ` Jiri Kosina
2014-07-08 12:55 ` Chris Wilson
2014-07-08 12:59 ` Jiri Kosina
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=20140708083505.GQ17271@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=thomas@m3y3r.de \
--cc=torvalds@linux-foundation.org \
/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