From: Vishwanath Sripathy <vishwanath.bs@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>, linux-omap@vger.kernel.org
Subject: RE: [PATCH/RFC 2/2] OMAP: PM: implement context loss count APIs
Date: Mon, 13 Dec 2010 19:18:35 +0530 [thread overview]
Message-ID: <940a49d978e2d610b2349f42d56614cc@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1012130331570.15971@utopia.booyaka.com>
Paul,
> -----Original Message-----
> From: Paul Walmsley [mailto:paul@pwsan.com]
> Sent: Monday, December 13, 2010 4:13 PM
> To: Vishwanath Sripathy
> Cc: Kevin Hilman; linux-omap@vger.kernel.org
> Subject: RE: [PATCH/RFC 2/2] OMAP: PM: implement context loss count
> APIs
>
> Hello Vishwa,
>
> On Fri, 10 Dec 2010, Vishwanath Sripathy wrote:
>
> > > + count = omap_device_get_context_loss_count(pdev);
> > > + pr_debug("OMAP PM: context loss count for dev %s = %d\n",
> > > + dev_name(dev), count);
> > Shouldn't this implementation be part of omap-pm.c where all the
> OMAP PM
> > functions are to be implemented? I thought omap-pm-noop.c should
> have
> > dummy implementation.
>
> In general, yes. But we also want the code in omap-pm-noop.c not to
> cause
> additional breakage. Unlike most of the other functions in this file,
if
> the context loss count function doesn't do something minimally useful,
> then
> the system is going to break badly. You've probably seen this thread:
>
> http://www.mail-archive.com/linux-
> omap@vger.kernel.org/msg40079.html
>
> (By the way, the reason why I think we shouldn't use the approach
> described in
>
> http://www.mail-archive.com/linux-
> omap@vger.kernel.org/msg40101.html
>
> is because I suspect it is going to seriously damage retention idle
> performance. For example, the HSMMC driver resets its entire IP block
in
> its context restore function...)
>
> But to confirm your general point, yes, in general, further functional
> development of the OMAP PM code should take place outside the no-op
> file.
> Hopefully, at some point, we'll be able to drop the no-op file. Once
> there is a useful replacement, we should be able to switch to it as a
> default.
I have no issues with the implementation and I agree. All I am saying is
that why can't this implementation be added in omap-pm.c and compile this
file instead of omap-pm-noop.c when OMAP_PM is enabled. I believe this
function is useful when off mode is enabled which means OMAP_PM is
enabled.
Vishwa
>
>
> - Paul
next prev parent reply other threads:[~2010-12-13 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 0:08 [PATCH/RFC 1/2] OMAP2+: powerdomain: add API to get context loss count Kevin Hilman
2010-12-10 0:08 ` [PATCH/RFC 2/2] OMAP: PM: implement context loss count APIs Kevin Hilman
2010-12-10 11:28 ` Vishwanath Sripathy
2010-12-11 0:43 ` Kevin Hilman
2010-12-11 7:13 ` Vishwanath Sripathy
2010-12-13 10:43 ` Paul Walmsley
2010-12-13 13:48 ` Vishwanath Sripathy [this message]
2010-12-13 19:39 ` Paul Walmsley
2010-12-15 3:35 ` Paul Walmsley
2010-12-10 1:32 ` [PATCH/RFC 3/2] OMAP: PM noop: implement context loss count for non-omap_devices Kevin Hilman
2010-12-15 3:39 ` Paul Walmsley
2010-12-15 3:23 ` [PATCH/RFC 1/2] OMAP2+: powerdomain: add API to get context loss count Paul Walmsley
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=940a49d978e2d610b2349f42d56614cc@mail.gmail.com \
--to=vishwanath.bs@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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