linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: t-kristo@ti.com (Tero Kristo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 0/9] ARM: OMAP3+: pwrdm changes for usecounting
Date: Thu, 31 May 2012 16:28:53 +0300	[thread overview]
Message-ID: <1338470942-20185-1-git-send-email-t-kristo@ti.com> (raw)

Hi,

Refreshed the patches against latest mainline kernel, and did some
updates mainly proposed by Nishanth Menon <nm@ti.com>. Changes compared
to previous version:

patch 1:
 - added check against null pointer

patch 2:
 - added BUG_ON in case clkdm / pwrdm usecount goes negative

patch 3:
 - added BUG_ON in case voltdm usecount goes negative
 - removed smartreflex enable / disable from voltdm code (this should
   be added in a separate patch once this is deemed safe)
 - changed target_state from int to u8

patch 4:
 - changed idle loop count initializations to happen synchronously with
   PM init, this avoids potential trouble in a case where a CPU would
   enter idle before usecount init for the idle has been done
 - added functions pwrdm_cpu_wakeup + pwrdm_cpu_idle to be called from idle
   cycle

patch 7:
 - changed flag name from CLKDM_NO_MANUAL_TRANS to CLKDM_SKIP_MANUAL_TRANS

patch 9:
 - added as new patch, would appreciate testing for this one!

Tested on omap3 beagle + boot tested on omap4460 panda es. Previous version
of this set had some issues with omap3430 devices (n900), which might have
been caused by improper clock handling or security on these devices. I can't
test these patches myself on n900, so if someone could do this that would
be extra nice.

git tree also available:
tree: git://gitorious.org/~kristo/omap-pm/omap-pm-work.git
branch: mainline-3.4-pwrdm-changes-v3

-Tero

             reply	other threads:[~2012-05-31 13:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31 13:28 Tero Kristo [this message]
2012-05-31 13:28 ` [PATCHv3 1/9] ARM: OMAP: clk: add support for omap_clk_for_each Tero Kristo
2012-05-31 13:28 ` [PATCHv3 2/9] ARM: OMAP3+: voltage/pwrdm/clkdm/clock add recursive usecount tracking Tero Kristo
2012-06-01 10:13   ` Menon, Nishanth
2012-06-01 10:27     ` Paul Walmsley
2012-06-04  9:38       ` Tero Kristo
2012-05-31 13:28 ` [PATCHv3 3/9] ARM: OMAP3+: voltage: add support for voltagedomain usecounts Tero Kristo
2012-05-31 13:28 ` [PATCHv3 4/9] ARM: OMAP3: add manual control for mpu / core pwrdm usecounting Tero Kristo
2012-05-31 13:28 ` [PATCHv3 5/9] ARM: OMAP3: set autoidle flags for a few clocks Tero Kristo
2012-07-12  9:13   ` Rajendra Nayak
2012-07-12 15:32     ` Tero Kristo
2012-05-31 13:28 ` [PATCHv3 6/9] ARM: OMAP: pm-debug: enhanced usecount debug support Tero Kristo
2012-05-31 13:29 ` [PATCHv3 7/9] ARM: OMAP: clockdomain: add support for preventing domain transitions Tero Kristo
2012-05-31 13:29 ` [PATCHv3 8/9] ARM: OMAP3: prevent per_clkdm from attempting manual " Tero Kristo
2012-05-31 23:40   ` Jon Hunter
2012-06-01  8:06     ` Tero Kristo
2012-07-12  9:41   ` Rajendra Nayak
2012-07-12 15:35     ` Tero Kristo
2012-05-31 13:29 ` [PATCHv3 9/9] TEMP: ARM: OMAP3: prevent dpll4 manual enable / disable + prevent core clkdm idle 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=1338470942-20185-1-git-send-email-t-kristo@ti.com \
    --to=t-kristo@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).