From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2] ARM: mach-shmobile: sh7372 A4R suspend/resume order fix
Date: Thu, 10 Nov 2011 03:47:05 +0000 [thread overview]
Message-ID: <20111110034704.GB7271@linux-sh.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1111091914120.4188@axis700.grange>
On Thu, Nov 10, 2011 at 11:14:42AM +0900, Magnus Damm wrote:
> On Thu, Nov 10, 2011 at 8:30 AM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Wednesday, November 09, 2011, Guennadi Liakhovetski wrote:
> >> I took the liberty to reimplement the original fix by Magnus in a
> >> different way. I didn't quite like the idea of rewriting platform data,
> >> which could and, probably, should actually be const, on each
> >> domain-suspend. Instead, checking in resume, whether a valid state
> >> snapshot is available seemed a bit prettier to me:-) The maintainer is, of
> >> course, free to choose whichever version he prefers, they both
> >>
> >> "Fix issue in v3.2-rc1 on the sh7372 Mackerel board."
> >
> > Magnus, Paul, which one do you want me to take?
>
> I prefer leaving the INTCS code as-is - unaware of calling order and
> putting the workaround in the Runtime PM code. In the end the ordering
> issue is related to Runtime PM and not INTCS. If someone knows a
> better way to fix the Runtime PM code then I'd be happy to accept
> that. But I don't like putting the workaround in INTCS.
>
Agreed. While I don't much care for the approach taken by this patch
either, keeping it insular at the framework level until the need for it
can be resolved in the runtime PM code seems like a reasonable stop-gap.
I would rather not paper over this in the platform code since it'll
invariably lead to more instances that need to be audited and cleaned up
later on, in addition to being more error prone.
next prev parent reply other threads:[~2011-11-10 3:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 18:23 [PATCH v2] ARM: mach-shmobile: sh7372 A4R suspend/resume order fix Guennadi Liakhovetski
2011-11-09 23:30 ` Rafael J. Wysocki
2011-11-10 2:14 ` Magnus Damm
2011-11-10 3:47 ` Paul Mundt [this message]
2011-11-10 9:06 ` Rafael J. Wysocki
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=20111110034704.GB7271@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.