From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: mach-shmobile: fix Oops during system wake up
Date: Mon, 18 Apr 2011 09:09:21 +0000 [thread overview]
Message-ID: <20110418090921.GE32457@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1104152009080.18593@axis700.grange>
On Fri, Apr 15, 2011 at 08:37:55PM +0200, Guennadi Liakhovetski wrote:
> On Fri, 15 Apr 2011, Guennadi Liakhovetski wrote:
>
> > During system resume the clock subsystem is restoring all clock rates,
> > if sound has not been used before suspend, the rate remains 0 and
> > the wake up Oopses with division by zero.
>
> Right, I see now. Magnus had a more general solution for this problem,
> which I accidentally dropped in my tests, which caused this Oops. So,
> maybe his patch to check rate in clks_core_resume() is a better fix for
> this problem. Feel free to ignore this then.
>
Having a solution that doesn't exist in the list archives is effectively
the same as not having a solution at all.
From your description I imagine you mean something like checking if
clkp->rate is set prior to calling in to ->set_rate, however this
probably needs a bit more of a think. Your example stipulates that we're
resuming clocks that haven't been "used", which suggests that we're
probably better off simply not touching the clock at all in the resume
path. I expect if you were to set the rate via the recalc path instead it
also wouldn't have the desired effect for your case.
In any event, it's quite obvious that clks_core_resume() is going to need
to be reworked a bit.
next prev parent reply other threads:[~2011-04-18 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 18:10 [PATCH] ARM: mach-shmobile: fix Oops during system wake up Guennadi Liakhovetski
2011-04-15 18:37 ` Guennadi Liakhovetski
2011-04-16 10:38 ` Simon Horman
2011-04-18 9:09 ` Paul Mundt [this message]
2011-04-18 9:13 ` Magnus Damm
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=20110418090921.GE32457@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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.