From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh_tmu / PM: Prevent power from being removed from TMU devices
Date: Mon, 05 Mar 2012 17:29:49 +0000 [thread overview]
Message-ID: <20120305172948.GA20226@linux-sh.org> (raw)
In-Reply-To: <201203030041.30244.rjw@sisk.pl>
On Mon, Mar 05, 2012 at 05:01:20PM +0900, Magnus Damm wrote:
> On Mon, Mar 5, 2012 at 2:47 PM, Paul Mundt <lethal@linux-sh.org> wrote:
> > On Sun, Mar 04, 2012 at 10:50:53PM +0100, Rafael J. Wysocki wrote:
> >> On Sunday, March 04, 2012, Paul Mundt wrote:
> >> > Presumably we also need the same for the MTU2 and CMT drivers?
> >>
> >> Yes, we do in principle, although this isn't strictly necessary for things to
> >> work at the moment.
> >>
> >> I can post analogous patches for the other drivers if you want me to.
> >>
> > It would be nice to ensure that we don't run in to the same problems on
> > the other drivers in the interim at least. I'll take a look at getting
> > proper PM support taken care of for them afterwards.
>
> I agree, but I wonder how much of an actual issue it is at this point.
> In the long run of course the drivers should be fixed up, but this
> patch more looks like a workaround for 3.3-rc.
>
> As for actual hardware timers, MTU2 is not used on any platform with
> power domain support today and the CMT is located in a always-on power
> domain. So they should not cause any issues for 3.3-rc.
>
It doesn't matter. If we're going to band-aid around the TMU case for a
PM incompatability then the same fix needs to be applied to the other
relevant drivers, barring a proper fix. We aren't going to be making
random band-aid fixes that in turn bring the drivers behaviourly out of
sync simply because of some imagined timeline issue with 3.3-rc. Again,
none of this thread would have even been necessary had the job been done
right from the beginning.
next prev parent reply other threads:[~2012-03-05 17:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 23:41 [PATCH] sh_tmu / PM: Prevent power from being removed from TMU devices Rafael J. Wysocki
2012-03-04 21:03 ` Paul Mundt
2012-03-04 21:50 ` Rafael J. Wysocki
2012-03-05 5:47 ` Paul Mundt
2012-03-05 8:01 ` Magnus Damm
2012-03-05 17:29 ` Paul Mundt [this message]
2012-03-05 20:32 ` Rafael J. Wysocki
2012-03-05 22:46 ` Rafael J. Wysocki
2012-03-06 2:07 ` Paul Mundt
2012-03-06 22:13 ` Rafael J. Wysocki
2012-03-12 5:18 ` Simon Horman
2012-03-12 5:23 ` Paul Mundt
2012-03-12 8:06 ` Simon Horman
2012-03-12 21:37 ` Rafael J. Wysocki
2012-03-12 21:54 ` 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=20120305172948.GA20226@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox