From: Eduardo Valentin <eduardo.valentin@ti.com>
To: "Menon, Nishanth" <nm@ti.com>
Cc: Kevin Hilman <khilman@ti.com>, Tony Lindgren <tony@atomide.com>,
eduardo.valentin@ti.com, Wenbiao Wang <wwang@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2] ARM: OMAP3+: PM: VP: ensure VP is idle before disable
Date: Mon, 21 May 2012 17:51:57 +0300 [thread overview]
Message-ID: <20120521145157.GA7923@besouro> (raw)
In-Reply-To: <CAOMWX4f2N1dS8RcwYAyUpmWVKPkEHGuhMGGZ3__D-DwipsjzFQ@mail.gmail.com>
Hello,
On Mon, May 21, 2012 at 08:36:35AM -0500, ext Nishanth Menon wrote:
> Sat, May 19, 2012 at 4:52 AM, Eduardo Valentin <eduardo.valentin@ti.com>
> wrote:
> >
> >
> > I guess it is time to properly document this increasing busy loop delay..
> > As it is getting closer to ms scale..
> Does the following sound good?
> /* Maximum time for Voltage Processor to enter or exit idle */
Sounds way better :-). If you have an estimation of how long it takes
in the average case, it might help. But I am OK already with the above,
in case you don't have the estimation.
>
> Regards,
> Nishanth Menon
Cheers,
--
Eduardo Valentin
WARNING: multiple messages have this Message-ID (diff)
From: eduardo.valentin@ti.com (Eduardo Valentin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] ARM: OMAP3+: PM: VP: ensure VP is idle before disable
Date: Mon, 21 May 2012 17:51:57 +0300 [thread overview]
Message-ID: <20120521145157.GA7923@besouro> (raw)
In-Reply-To: <CAOMWX4f2N1dS8RcwYAyUpmWVKPkEHGuhMGGZ3__D-DwipsjzFQ@mail.gmail.com>
Hello,
On Mon, May 21, 2012 at 08:36:35AM -0500, ext Nishanth Menon wrote:
> Sat, May 19, 2012 at 4:52 AM, Eduardo Valentin <eduardo.valentin@ti.com>
> wrote:
> >
> >
> > I guess it is time to properly document this increasing busy loop delay..
> > As it is getting closer to ms scale..
> Does the following sound good?
> /* Maximum time for Voltage Processor to enter or exit idle */
Sounds way better :-). If you have an estimation of how long it takes
in the average case, it might help. But I am OK already with the above,
in case you don't have the estimation.
>
> Regards,
> Nishanth Menon
Cheers,
--
Eduardo Valentin
next prev parent reply other threads:[~2012-05-21 14:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH] ARM: OMAP3+: PM: VP: ensure VP is idle before disable>
2012-05-18 18:18 ` [PATCH V2] ARM: OMAP3+: PM: VP: ensure VP is idle before disable Nishanth Menon
2012-05-18 18:18 ` Nishanth Menon
2012-05-19 9:52 ` Eduardo Valentin
2012-05-19 9:52 ` Eduardo Valentin
2012-05-21 13:36 ` Menon, Nishanth
2012-05-21 13:36 ` Menon, Nishanth
2012-05-21 14:51 ` Eduardo Valentin [this message]
2012-05-21 14:51 ` Eduardo Valentin
2012-05-21 15:14 ` Menon, Nishanth
2012-05-21 15:14 ` Menon, Nishanth
2012-05-22 7:02 ` Valentin, Eduardo
2012-05-22 7:02 ` Valentin, Eduardo
2012-05-18 19:33 ` [PATCH 0/3] ARM: OMAP3+: VP: collate fixes Nishanth Menon
2012-05-18 19:33 ` Nishanth Menon
2012-05-18 19:33 ` [PATCH 1/3] ARM: OMAP3+: PM: VP: ensure VP is idle before disable Nishanth Menon
2012-05-18 19:33 ` Nishanth Menon
2012-05-31 23:21 ` Kevin Hilman
2012-05-31 23:21 ` Kevin Hilman
2012-05-31 23:28 ` Kevin Hilman
2012-05-31 23:28 ` Kevin Hilman
2012-05-31 23:35 ` Nishanth Menon
2012-05-31 23:35 ` Nishanth Menon
2012-05-18 19:33 ` [PATCH 2/3] ARM: OMAP3+: PM: VP: check to ensure VP is idle before forceupdate Nishanth Menon
2012-05-18 19:33 ` Nishanth Menon
2012-05-31 23:23 ` Kevin Hilman
2012-05-31 23:23 ` Kevin Hilman
2012-05-31 23:37 ` Nishanth Menon
2012-05-31 23:37 ` Nishanth Menon
2012-05-18 19:33 ` [PATCH 3/3] ARM: OMAP3+: PM: VP: check only the VPINIDLE status bit Nishanth Menon
2012-05-18 19:33 ` Nishanth Menon
2012-05-31 23:27 ` Kevin Hilman
2012-05-31 23:27 ` Kevin Hilman
2012-05-31 23:39 ` Nishanth Menon
2012-05-31 23:39 ` Nishanth Menon
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=20120521145157.GA7923@besouro \
--to=eduardo.valentin@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=tony@atomide.com \
--cc=wwang@ti.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.