linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Paul Mundt <lethal@linux-sh.org>
Cc: kuninori.morimoto.gx@renesas.com,
	Magnus Damm <magnus.damm@gmail.com>,
	"Linux-sh list" <linux-sh@vger.kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
Subject: Re: [Regression, post-3.5] System suspend broken on the Mackerel board
Date: Thu, 9 Aug 2012 23:20:22 +0200	[thread overview]
Message-ID: <201208092320.23075.rjw@sisk.pl> (raw)
In-Reply-To: <20120809044057.GH1614@linux-sh.org>

On Thursday, August 09, 2012, Paul Mundt wrote:
> On Wed, Aug 08, 2012 at 11:23:04AM +0200, Rafael J. Wysocki wrote:
> > On Tuesday, August 07, 2012, Paul Mundt wrote:
> > > On Sun, Aug 05, 2012 at 12:02:43AM +0200, Rafael J. Wysocki wrote:
> > > > On Wednesday, August 01, 2012, Paul Mundt wrote:
> > > > > Turns out we can just collapse the probe/init stuff anyways, so this
> > > > > ought to fix it. I've verified that it fixes Morimoto-san's issue, my
> > > > > expectation is that the mackerel case is likewise getting tripped up but
> > > > > no one bothered implementing any error detecting logic for gpio_request()
> > > > > failing, so it doesn't fail gracefully.
> > > > > 
> > > > > I'll be pushing this out to Linus shortly:
> > > > 
> > > > Thanks, this helped.  Resume works correctly on Mackerel with 3.6-rc1.
> > > > 
> > > > However, I'm now seeing a different problem related to system suspend on that,
> > > > board which is that sh7372_enter_a3sm_common() returns immediately, as though
> > > > at least one of the wakeup signals was permanently asserted.  This hadn't
> > > > happened before your last pull request was merged, so I suspect that one
> > > > of the irqdomain patches might introduce this behavior.
> > > > 
> > > Ok, I'll back off the irqdomain selection until we have a chance to test
> > > it more on the other platforms.
> > 
> > If you mean removing the select from drivers/sh/intc/Kconfig, that alone doesn't
> > help.  Reverting commit 1d6a21b0a672fb29b01ccf397d478e0541e17716
> > (sh: intc: initial irqdomain support.) helps, though.
> > 
> Yeah, I see what happened now. I inadvertently trampled the -EEXIST
> behaviour. I've taken care of it now, so hopefully you'll have better
> luck with -rc2!

I tested your "sh: intc: Handle domain association for sparseirq pre-allocated
vectors" patch in the meantime and it does fix the issue.

Thanks,
Rafael

      reply	other threads:[~2012-08-09 21:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <878vdze039.wl%kuninori.morimoto.gx@renesas.com>
2012-07-27 22:53 ` [Regression, post-3.5] System suspend broken on the Mackerel board Rafael J. Wysocki
2012-07-28  0:48   ` Paul Mundt
2012-08-01  7:30   ` Paul Mundt
2012-08-04 22:02     ` Rafael J. Wysocki
2012-08-07  1:55       ` Paul Mundt
2012-08-08  9:23         ` Rafael J. Wysocki
2012-08-09  4:40           ` Paul Mundt
2012-08-09 21:20             ` Rafael J. Wysocki [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=201208092320.23075.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=kuninori.morimoto.gx@gmail.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@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;
as well as URLs for NNTP newsgroup(s).