From: Kevin Hilman <khilman@ti.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/6] arm: omap: clk/clkdm/pwrdm/voltdm changes to usecounting
Date: Tue, 14 Feb 2012 12:02:06 -0800 [thread overview]
Message-ID: <87ty2t5gld.fsf@ti.com> (raw)
In-Reply-To: <1329237402-26008-1-git-send-email-t-kristo@ti.com> (Tero Kristo's message of "Tue, 14 Feb 2012 18:36:36 +0200")
Tero Kristo <t-kristo@ti.com> writes:
> This set is split out from a larger set earlier circulated on linux-omap
> list. The main purpose of this set is to provide useful recursive
> usecounting support for clockdomains / powerdomains / voltagedomains
> which can be used for debugging purposes and also to control certain
> chip power features once a sleep condition is reached (voltdm usecount=0).
>
> This set provides only the baseline support for the usecounting, and also
> adds a pm-debug related patch that can be used to check out stuff (patch 6),
> and should later prove rather useful for debugging. Rest of the
> functionality will be posted in separate sets.
>
> This set has been tested on omap3 beagle board with suspend / resume /
> cpuidle. Also boot tested on omap4 panda (sleep is not functional yet
> on that platform.)
This is a great series, and results in pm_debug debugfs data that's
actually useful for real debug. Thanks!
I had a minor comment on the idle path changes, but all the other stuff
is
Acked-by: Kevin Hilman <khilman@ti.com>
Paul, this should probably merge via you (when it's ready) since the
important changes are clock and powerdomain core changes.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] arm: omap: clk/clkdm/pwrdm/voltdm changes to usecounting
Date: Tue, 14 Feb 2012 12:02:06 -0800 [thread overview]
Message-ID: <87ty2t5gld.fsf@ti.com> (raw)
In-Reply-To: <1329237402-26008-1-git-send-email-t-kristo@ti.com> (Tero Kristo's message of "Tue, 14 Feb 2012 18:36:36 +0200")
Tero Kristo <t-kristo@ti.com> writes:
> This set is split out from a larger set earlier circulated on linux-omap
> list. The main purpose of this set is to provide useful recursive
> usecounting support for clockdomains / powerdomains / voltagedomains
> which can be used for debugging purposes and also to control certain
> chip power features once a sleep condition is reached (voltdm usecount=0).
>
> This set provides only the baseline support for the usecounting, and also
> adds a pm-debug related patch that can be used to check out stuff (patch 6),
> and should later prove rather useful for debugging. Rest of the
> functionality will be posted in separate sets.
>
> This set has been tested on omap3 beagle board with suspend / resume /
> cpuidle. Also boot tested on omap4 panda (sleep is not functional yet
> on that platform.)
This is a great series, and results in pm_debug debugfs data that's
actually useful for real debug. Thanks!
I had a minor comment on the idle path changes, but all the other stuff
is
Acked-by: Kevin Hilman <khilman@ti.com>
Paul, this should probably merge via you (when it's ready) since the
important changes are clock and powerdomain core changes.
Kevin
next prev parent reply other threads:[~2012-02-14 20:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 16:36 [PATCH 0/6] arm: omap: clk/clkdm/pwrdm/voltdm changes to usecounting Tero Kristo
2012-02-14 16:36 ` Tero Kristo
2012-02-14 16:36 ` [PATCH 1/6] arm: omap: clk: add support for omap_clk_for_each Tero Kristo
2012-02-14 16:36 ` Tero Kristo
2012-02-14 16:36 ` [PATCH 2/6] arm: omap3+: voltage/pwrdm/clkdm/clock add recursive usecount tracking Tero Kristo
2012-02-14 16:36 ` Tero Kristo
2012-02-14 16:36 ` [PATCH 3/6] arm: omap3+: voltage: add support for voltagedomain usecounts Tero Kristo
2012-02-14 16:36 ` Tero Kristo
2012-02-14 16:36 ` [PATCH 4/6] arm: omap3: add manual control for mpu_iva voltdm usecounting Tero Kristo
2012-02-14 16:36 ` Tero Kristo
2012-02-14 19:35 ` Kevin Hilman
2012-02-14 19:35 ` Kevin Hilman
2012-02-15 8:16 ` Tero Kristo
2012-02-15 8:16 ` Tero Kristo
2012-02-15 19:29 ` Kevin Hilman
2012-02-15 19:29 ` Kevin Hilman
2012-02-14 16:36 ` [PATCH 5/6] arm: omap3: set autoidle flags for a few clocks Tero Kristo
2012-02-14 16:36 ` Tero Kristo
2012-02-14 16:36 ` [PATCH 6/6] arm: omap: pm-debug: enhanced usecount debug support Tero Kristo
2012-02-14 16:36 ` Tero Kristo
2012-02-14 20:27 ` Tony Lindgren
2012-02-14 20:27 ` Tony Lindgren
2012-02-14 22:59 ` Kevin Hilman
2012-02-14 22:59 ` Kevin Hilman
2012-02-14 23:52 ` Tony Lindgren
2012-02-14 23:52 ` Tony Lindgren
2012-02-15 8:34 ` Tero Kristo
2012-02-15 8:34 ` Tero Kristo
2012-02-15 15:20 ` Kevin Hilman
2012-02-15 15:20 ` Kevin Hilman
2012-02-16 17:06 ` Menon, Nishanth
2012-02-16 17:06 ` Menon, Nishanth
2012-02-16 17:35 ` Kevin Hilman
2012-02-16 17:35 ` Kevin Hilman
2012-02-16 18:14 ` Menon, Nishanth
2012-02-16 18:14 ` Menon, Nishanth
2012-02-14 20:02 ` Kevin Hilman [this message]
2012-02-14 20:02 ` [PATCH 0/6] arm: omap: clk/clkdm/pwrdm/voltdm changes to usecounting Kevin Hilman
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=87ty2t5gld.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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.