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: Sat, 04 Aug 2012 22:02:43 +0000 [thread overview]
Message-ID: <201208050002.43465.rjw@sisk.pl> (raw)
In-Reply-To: <20120801073004.GE15380@linux-sh.org>
On Wednesday, August 01, 2012, Paul Mundt wrote:
> On Sat, Jul 28, 2012 at 12:53:11AM +0200, Rafael J. Wysocki wrote:
> > Unfortunately, your commit
> >
> > commit ca5481c68e9fbcea62bb3c78ae6cccf99ca8fb73
> > Author: Paul Mundt <lethal@linux-sh.org>
> > Date: Tue Jul 10 12:08:14 2012 +0900
> >
> > sh: pfc: Rudimentary pinctrl-backed GPIO support.
> >
> > breaks system suspend on the Mackerel board (.config attached). The system
> > simply doesn't suspend and instead it hangs somewhere while suspending
> > devices (apparently before running the "late" callbacks).
> >
> > If the above commit is reverted, system suspend works normally.
>
> On Tue, Jul 31, 2012 at 08:57:02PM -0700, kuninori.morimoto.gx@renesas.com wrote:
> > gpio: sh7724_pfc handling gpio 0 -> 486
> > core: sh7724_pfc support registered
> > HW Breakpoints: SH-4A UBC support registered
> > autorequest GPIO-53
> > ------------[ cut here ]------------
> > WARNING: at /opt/usr/src/WORK/morimoto/gitlinux/linux-2.6/drivers/gpio/gpiolib.3
> > Modules linked in:
> >
> > Pid : 1, Comm: swapper
> > CPU : 0 Not tainted (3.5.0-rc6+ #1407)
> >
> > PC is at gpio_ensure_requested+0x30/0x78
> > PR is at gpio_ensure_requested+0x30/0x78
>
> Morimoto-san's logs off-list made it clear what happened. Both of these
> platforms are going gpio_request() calls at arch_initcall() time which
> completely screwed up the ordering of the pfc core. We seem to -ENODEV
> out in one place due to missing a pfc pointer initialization elsewhere
> resulting in -EPROBE_DEFER from gpiolib.
>
> 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.
Thanks,
Rafael
WARNING: multiple messages have this Message-ID (diff)
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: Sun, 5 Aug 2012 00:02:43 +0200 [thread overview]
Message-ID: <201208050002.43465.rjw@sisk.pl> (raw)
In-Reply-To: <20120801073004.GE15380@linux-sh.org>
On Wednesday, August 01, 2012, Paul Mundt wrote:
> On Sat, Jul 28, 2012 at 12:53:11AM +0200, Rafael J. Wysocki wrote:
> > Unfortunately, your commit
> >
> > commit ca5481c68e9fbcea62bb3c78ae6cccf99ca8fb73
> > Author: Paul Mundt <lethal@linux-sh.org>
> > Date: Tue Jul 10 12:08:14 2012 +0900
> >
> > sh: pfc: Rudimentary pinctrl-backed GPIO support.
> >
> > breaks system suspend on the Mackerel board (.config attached). The system
> > simply doesn't suspend and instead it hangs somewhere while suspending
> > devices (apparently before running the "late" callbacks).
> >
> > If the above commit is reverted, system suspend works normally.
>
> On Tue, Jul 31, 2012 at 08:57:02PM -0700, kuninori.morimoto.gx@renesas.com wrote:
> > gpio: sh7724_pfc handling gpio 0 -> 486
> > core: sh7724_pfc support registered
> > HW Breakpoints: SH-4A UBC support registered
> > autorequest GPIO-53
> > ------------[ cut here ]------------
> > WARNING: at /opt/usr/src/WORK/morimoto/gitlinux/linux-2.6/drivers/gpio/gpiolib.3
> > Modules linked in:
> >
> > Pid : 1, Comm: swapper
> > CPU : 0 Not tainted (3.5.0-rc6+ #1407)
> >
> > PC is at gpio_ensure_requested+0x30/0x78
> > PR is at gpio_ensure_requested+0x30/0x78
>
> Morimoto-san's logs off-list made it clear what happened. Both of these
> platforms are going gpio_request() calls at arch_initcall() time which
> completely screwed up the ordering of the pfc core. We seem to -ENODEV
> out in one place due to missing a pfc pointer initialization elsewhere
> resulting in -EPROBE_DEFER from gpiolib.
>
> 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.
Thanks,
Rafael
next prev parent reply other threads:[~2012-08-04 22:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 3:57 bug report: ecovec boot got WARNING kuninori.morimoto.gx
2012-07-27 22:53 ` [Regression, post-3.5] System suspend broken on the Mackerel board Rafael J. Wysocki
2012-07-27 22:53 ` Rafael J. Wysocki
2012-07-28 0:48 ` Paul Mundt
2012-07-28 0:48 ` Paul Mundt
2012-08-01 7:30 ` Paul Mundt
2012-08-01 7:30 ` Paul Mundt
2012-08-04 22:02 ` Rafael J. Wysocki [this message]
2012-08-04 22:02 ` Rafael J. Wysocki
2012-08-07 1:55 ` Paul Mundt
2012-08-07 1:55 ` Paul Mundt
2012-08-08 9:23 ` Rafael J. Wysocki
2012-08-08 9:23 ` Rafael J. Wysocki
2012-08-09 4:40 ` Paul Mundt
2012-08-09 4:40 ` Paul Mundt
2012-08-09 21:20 ` Rafael J. Wysocki
2012-08-09 21:20 ` Rafael J. Wysocki
2012-08-01 5:04 ` bug report: ecovec boot got WARNING Paul Mundt
2012-08-01 5:39 ` Kuninori Morimoto
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=201208050002.43465.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 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.