From: Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ben Skeggs <skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/nouveau: POST the card before GPIO initialization
Date: Fri, 14 Sep 2012 13:45:18 +0200 [thread overview]
Message-ID: <20120914114518.GA3619@joi.lan> (raw)
In-Reply-To: <20120914064459.GE4289-7ZJhIA9XobDzA+JJ9lL7d4GKTjYczspe@public.gmane.org>
On Fri, Sep 14, 2012 at 04:44:59PM +1000, Ben Skeggs wrote:
> On Fri, Sep 14, 2012 at 12:21:33AM +0200, Marcin Slusarz wrote:
> > Otherwise my card (nv92) never resumes from suspend to ram, hanging on
> > nv_mask in nv50_gpio_drive. Before rework, initialization was done only
> > from POST, so this patch restores previous behaviour.
> This patch would break the cold-boot behaviour (DEVINIT needs GPIO etc
> to have been created so it can call out to them).
>
> I've modified nouveau git so that it restores the behaviour of the first
> version of the rework and has DEVINIT be the first in the init ordering,
> but delays its init until all its dependencies have been created.
>
> Can you confirm your issue is resolved now?
Yes.
Two thoughts:
Your commit message states that the next commit triggers the bad behaviour,
but it's not completely true - I had resume lockups even before this commit
hit the tree. Though I don't know what was the problem.
It's a bit sad when ones spends a lot of time on debugging something and
the patch is redone the next day by the maintainer. If you would give me
the feedback on the patch, I would improve it and resend.
Marcin
next prev parent reply other threads:[~2012-09-14 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 22:21 [PATCH] drm/nouveau: POST the card before GPIO initialization Marcin Slusarz
[not found] ` <20120913222133.GA8982-OI9uyE9O0yo@public.gmane.org>
2012-09-14 6:44 ` Ben Skeggs
[not found] ` <20120914064459.GE4289-7ZJhIA9XobDzA+JJ9lL7d4GKTjYczspe@public.gmane.org>
2012-09-14 11:45 ` Marcin Slusarz [this message]
[not found] ` <20120914114518.GA3619-OI9uyE9O0yo@public.gmane.org>
2012-09-14 12:28 ` Ben Skeggs
2012-09-16 23:15 ` Marcin Slusarz
[not found] ` <20120916231524.GA25218-OI9uyE9O0yo@public.gmane.org>
2012-09-18 15:38 ` Ben Skeggs
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=20120914114518.GA3619@joi.lan \
--to=marcin.slusarz-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.