linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Menon, Nishanth" <nm@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: kevin <khilman@ti.com>, linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PM-WIP/voltdm_c][PATCH 02/11] OMAP3+: PM: voltage: add required debugfs interfaces
Date: Wed, 18 May 2011 03:06:39 -0500	[thread overview]
Message-ID: <BANLkTinH8Rs8Tn8A8gf++UuM2zAxd1e54Q@mail.gmail.com> (raw)
In-Reply-To: <20110518075948.GD6815@atomide.com>

On Wed, May 18, 2011 at 02:59, Tony Lindgren <tony@atomide.com> wrote:
> * Nishanth Menon <nm@ti.com> [110518 08:13]:
>> Kevin's patch:
>> OMAP3+: voltage: remove unneeded debugfs interface
>>
>> removed ability to check the voltages in the domains.
>> This puts a crunch on validation we can do, hence we
>> re-introduce them back in
>
>> Signed-off-by: Nishanth Menon <nm@ti.com>
>> ---
>>  arch/arm/mach-omap2/voltage.c |   66 +++++++++++++++++++++++++++++++++++++++++
>>  arch/arm/mach-omap2/voltage.h |    1 +
>>  2 files changed, 67 insertions(+), 0 deletions(-)
>
> Hmm, this seems to be adding the debug code instead?

Yes, we need some interface to know what the current voltages are for
each of the domain when verifying if dvfs is actually scaling voltage
or not. the other option is to use omapconf (not yet public and only
supports OMAP4) to see what the voltages are. Though omapconf is an
option, it shows what it's computation of voltage from vsel is, not
what the kernel internally thinks (vsel_uv functions) it is.

Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-05-18  8:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18  5:17 [PM-WIP/voltdm_c][PATCH 00/11] OMAP4: Fixes for voltage scale Nishanth Menon
2011-05-18  5:17 ` [PM-WIP/voltdm_c][PATCH 01/11] OMAP3+: PM: SR: fix debugfs Nishanth Menon
2011-05-18  8:55   ` Kevin Hilman
2011-05-18  5:17 ` [PM-WIP/voltdm_c][PATCH 02/11] OMAP3+: PM: voltage: add required debugfs interfaces Nishanth Menon
2011-05-18  7:59   ` Tony Lindgren
2011-05-18  8:06     ` Menon, Nishanth [this message]
2011-05-18  8:34       ` Tony Lindgren
2011-05-18  8:41         ` Menon, Nishanth
2011-05-18  8:44   ` Kevin Hilman
2011-05-18  8:50     ` Menon, Nishanth
2011-05-18  5:17 ` [PM-WIP/voltdm_c][PATCH 03/11] OMAP3+: PM: VP: fix vstepmax Nishanth Menon
2011-05-18  8:58   ` Kevin Hilman
2011-05-18  5:17 ` [PM-WIP/voltdm_c][PATCH 04/11] OMAP4: PM: VC: support configuration of i2c clks Nishanth Menon
2011-05-18  8:53   ` Kevin Hilman
2011-05-18  8:57     ` Menon, Nishanth
2011-05-25 18:17       ` Kevin Hilman
2011-05-25 18:32         ` Menon, Nishanth
2011-05-18  5:17 ` [PM-WIP/voltdm_c][PATCH 05/11] OMAP4: PM: VC: fix highspeed i2c for SR Nishanth Menon
2011-05-18  8:59   ` Kevin Hilman
2011-05-18  5:17 ` [PM-WIP/voltdm_c][PATCH 06/11] OMAP4: PM: VC: fix channel bit offset for MPU Nishanth Menon
2011-05-18  9:34   ` Kevin Hilman
2011-05-18  9:47     ` Menon, Nishanth
2011-05-18 11:06       ` Kevin Hilman
2011-05-18 11:22         ` Menon, Nishanth
2011-05-18  5:17 ` [PM-WIP/voltdm_c][PATCH 07/11] OMAP4: PM: TWL6030: fix voltage conversion formula Nishanth Menon
2011-05-18  9:38   ` Kevin Hilman
2011-05-18  5:17 ` [PM-WIP/voltdm_c][PATCH 08/11] OMAP4: PM: TWL6030: fix uv to voltage for >0x39 Nishanth Menon
2011-05-18  9:41   ` Kevin Hilman
2011-05-18  5:17 ` [PM-WIP/voltdm_c][PATCH 09/11] OMAP4: PM: TWL6030: address 0V conversions Nishanth Menon
2011-05-18  5:17 ` [PM-WIP/voltdm_c][PATCH 10/11] OMAP4: PM: TWL6030: fix ON/RET/OFF voltages Nishanth Menon
2011-05-18 10:44   ` Kevin Hilman
2011-05-18  5:17 ` [PM-WIP/voltdm_c][PATCH 11/11] OMAP4: PM: TWL6030: add cmd register 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=BANLkTinH8Rs8Tn8A8gf++UuM2zAxd1e54Q@mail.gmail.com \
    --to=nm@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).