All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-omap@vger.kernel.org, nm@ti.com
Subject: Re: [PATCHv4 00/15] voltdm cleanup + auto-ret / auto-off support
Date: Fri, 09 Dec 2011 12:23:55 -0800	[thread overview]
Message-ID: <87sjktbijo.fsf@ti.com> (raw)
In-Reply-To: <1322236188-19456-1-git-send-email-t-kristo@ti.com> (Tero Kristo's message of "Fri, 25 Nov 2011 17:49:33 +0200")

Hi Tero,

Tero Kristo <t-kristo@ti.com> writes:

> Changes compared to previous version:
>
> - merged most of the voltagedomain cleanup fixes to patch 2
> - moved pmic latencies to omap_voltdm_pmic struct
> - renamed omap_lp_params to omap2_oscillator as it only contains
>   osc info now
> - major changes to usecount support (patch 11+, needed for auto-ret)
>   * added usecounts to voltagedomain / powerdomain
>   * fixed usecount tracking so that the numbers are sane now
>   * changed behavior of some usecounting sources that they do not
>     update the counts (autoidle support)
> - added auto-ret / auto-off support, based on fixed usecounting
>   * smartreflex disabled / enabled
>   * auto-ret / auto-off enabled based on target state
> - some other minor tweaks I have probably forgotten to mention

This series is looking really good.  Thanks!

One thing I'd like to see is a bit more comments.  Particularily, the
new functions in the VC core need kerneldoc comments and verbose
descriptions.

The differences in timing setups between retention and off are not
obvious when reading the code (and are easily forgotten).  They also
equire a bit of TRM (re)reading to understand what's going on.  Some
summary comments in the code, along with TRM references would be most
helpful so when coming back to this code in a few months or more, we can
easily remember what's going on (or at least where to look.)  Thanks.

> Tested on omap3 beagle:
> - voltages for vdd1 and vdd2 change when entering idle
> - both suspend and dynamic idle tested
> - tested that voltages reach target levels for both ret / off
>
> Tested on omap4 blaze with custom kernel
> - this requires a few additional patches missing from this set as
>   omap4 PM support is still not merged

MPUSS support is now queued (in Tony's tree), but CORE PM is still
missing.

> - will post missing patches once possible from upstream point of view
> - voltages for vdd1 and vdd3 change when entering idle
>
> Applies on top of Kevin's for_3.2/voltage-cleanup branch.

You can use mainline now as that branch is merged.

Also, please Cc linux-arm-kernel on future versions of this series.

Thanks,

Kevin

  parent reply	other threads:[~2011-12-09 20:23 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-25 15:49 [PATCHv4 00/15] voltdm cleanup + auto-ret / auto-off support Tero Kristo
2011-11-25 15:49 ` [PATCHv4 01/15] OMAP3+: PM: VP: use uV for max and min voltage limits Tero Kristo
2011-12-09 18:07   ` Kevin Hilman
2011-12-12  9:39     ` Tero Kristo
2011-11-25 15:49 ` [PATCHv4 02/15] omap3+: voltage: parameter segregation Tero Kristo
2011-11-29 18:26   ` Menon, Nishanth
2011-11-30 10:07     ` Tero Kristo
2011-11-30 12:31       ` Menon, Nishanth
2011-11-30 13:04         ` Tero Kristo
2011-11-30 10:11   ` Jean Pihet
2011-11-25 15:49 ` [PATCHv4 03/15] omap: voltage: add definition for pmic startup / shutdown times Tero Kristo
2011-11-25 15:49 ` [PATCHv4 04/15] omap4: add " Tero Kristo
2011-11-29 18:30   ` Menon, Nishanth
2011-11-30  9:45     ` Tero Kristo
2011-11-30 12:20       ` Menon, Nishanth
2011-11-30 13:08         ` Tero Kristo
2011-11-25 15:49 ` [PATCHv4 05/15] omap: add support for oscillator setup Tero Kristo
2011-12-09 18:27   ` Kevin Hilman
2011-12-12  9:40     ` Tero Kristo
2011-11-25 15:49 ` [PATCHv4 06/15] omap3+: vp: use new vp_params for calculating vddmin and vddmax Tero Kristo
2011-11-29 18:34   ` Menon, Nishanth
2011-11-25 15:49 ` [PATCHv4 07/15] omap3+: voltage: use oscillator data to calculate setup times Tero Kristo
2011-11-25 15:49 ` [PATCHv4 08/15] omap4: use pmic params for calculating pmic " Tero Kristo
2011-11-25 15:49 ` [PATCHv4 09/15] TEMP: OMAP3: beagle rev-c4: enable OPP6 Tero Kristo
2011-11-25 15:49 ` [PATCHv4 10/15] omap: beagle: set oscillator startup time to 10ms for rev c4 Tero Kristo
2011-12-09 19:11   ` Kevin Hilman
2011-12-12  9:42     ` Tero Kristo
2011-11-25 15:49 ` [PATCHv4 11/15] omap3+: voltage/pwrdm/clkdm/clock add recursive usecount tracking Tero Kristo
2011-11-30  9:52   ` Jean Pihet
2011-11-30 10:11     ` Tero Kristo
2011-12-09 19:37   ` Kevin Hilman
2011-12-12  9:45     ` Tero Kristo
2011-11-25 15:49 ` [PATCHv4 12/15] vc: omap3: auto_ret / auto_off support Tero Kristo
2011-12-09 20:13   ` Kevin Hilman
2011-12-12  9:53     ` Tero Kristo
2011-12-12 15:05       ` Kevin Hilman
2011-11-25 15:49 ` [PATCHv4 13/15] omap3: fix usecount tracking Tero Kristo
2011-11-25 15:49 ` [PATCHv4 14/15] omap3: voltage: fix channel configuration Tero Kristo
2011-11-25 15:49 ` [PATCHv4 15/15] omap: pm: wait for domain wakeup if changing state of idle domain Tero Kristo
2011-11-30 10:06 ` [PATCHv4 00/15] voltdm cleanup + auto-ret / auto-off support Jean Pihet
2011-11-30 10:19   ` Tero Kristo
2011-12-09 20:23 ` Kevin Hilman [this message]
2011-12-12  9:38   ` Tero Kristo

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=87sjktbijo.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=t-kristo@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.