public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Artem.Bityutskiy@nokia.com
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Richard Woodruff <r-woodruff2@ti.com>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-omap@vger.kernel.org,
	Jouni Hogander <jouni.hogander@nokia.com>,
	Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 01/11] OMAP2/3: PM: push core PM code from linux-omap
Date: Tue, 19 May 2009 07:57:26 -0700	[thread overview]
Message-ID: <87fxf187jd.fsf@deeprootsystems.com> (raw)
In-Reply-To: <4A124875.1080503@nokia.com> (Artem Bityutskiy's message of "Tue\, 19 May 2009 08\:49\:41 +0300")

Artem Bityutskiy <Artem.Bityutskiy@nokia.com> writes:

> Kevin Hilman wrote:
>>> The problem here is that such an interface is extremely fragile.  Consider
>>> what happens if a program disables HLT, and then gets killed off for some
>>> reason.  How does this reference get balanced again?
>>>
>>> I think a better solution would be a char device driver which has to be
>>> kept open as long as a reference is held.  When userspace closes it (be
>>> that because the program has exited, been killed, etc) you can drop any
>>> pending references.
>>
>> OK, this interface is not intended for users/applications. It is
>> intended only for OMAP PM developers who are developing the PM code
>> and want to prevent idle for various reasons during development.  It
>> is not intended for productions systems.
>>
>> What about leaving /sys/power/sleep_while_idle but only if
>> CONFIG_PM_DEBUG=y?
>
> Sounds like debugfs is the good place for this then.
>

Sound OK to me.

Kevin

  reply	other threads:[~2009-05-19 14:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15 18:40 [PATCH 00/11] OMAP2/3: PM sync-up Kevin Hilman
2009-05-15 18:40 ` [PATCH 01/11] OMAP2/3: PM: push core PM code from linux-omap Kevin Hilman
2009-05-15 18:40   ` [PATCH 02/11] OMAP: Add new function to check wether there is irq pending Kevin Hilman
2009-05-15 18:40     ` [PATCH 03/11] OMAP3: PM: Force IVA2 into idle during bootup Kevin Hilman
2009-05-15 18:40       ` [PATCH 04/11] OMAP3: PM: Add wake-up bit defintiions for CONTROL_PADCONF_X Kevin Hilman
2009-05-15 18:40         ` [PATCH 05/11] OMAP3: PM: UART: disable clocks when idle and off-mode support Kevin Hilman
2009-05-15 18:40           ` [PATCH 06/11] OMAP3: PM: Add D2D clocks and auto-idle setup to PRCM init Kevin Hilman
2009-05-15 18:40             ` [PATCH 07/11] OMAP3: PM: D2D clockdomain supports SW supervised transitions Kevin Hilman
2009-05-15 18:40               ` [PATCH 08/11] OMAP3: PM: Ensure MUSB block can idle when driver not loaded Kevin Hilman
2009-05-15 18:40                 ` [PATCH 09/11] OMAP3: PM: Ensure PRCM interrupts are cleared at boot Kevin Hilman
2009-05-15 18:40                   ` [PATCH 10/11] OMAP3: PM: Clear pending PRCM reset flags on init Kevin Hilman
2009-05-15 18:40                     ` [PATCH 11/11] OMAP3: PM: prevent module wakeups from waking IVA2 Kevin Hilman
2009-05-18 13:16                 ` [PATCH 08/11] OMAP3: PM: Ensure MUSB block can idle when driver not loaded Russell King - ARM Linux
2009-05-18 14:50                   ` Kevin Hilman
2009-05-18 15:04                     ` Tony Lindgren
2009-05-18 13:32   ` [PATCH 01/11] OMAP2/3: PM: push core PM code from linux-omap Russell King - ARM Linux
2009-05-18 17:00     ` Kevin Hilman
2009-05-18 17:06       ` Russell King - ARM Linux
2009-05-18 17:28         ` Kevin Hilman
2009-05-19  5:49           ` Artem Bityutskiy
2009-05-19 14:57             ` Kevin Hilman [this message]
2009-05-19 18:55         ` Kevin Hilman
2009-05-28 13:43           ` Russell King - ARM Linux
2009-05-18 17:08     ` Kevin Hilman
2009-05-18 18:30       ` Russell King - ARM Linux
2009-05-18 19:04       ` Woodruff, Richard
2009-05-18 20:24         ` Russell King - ARM Linux
2009-05-18 20:47           ` Woodruff, Richard
2009-05-18 21:11             ` Russell King - ARM Linux
2009-05-18 21:19               ` Woodruff, Richard
2009-05-19  0:23           ` 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=87fxf187jd.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=Artem.Bityutskiy@nokia.com \
    --cc=jouni.hogander@nokia.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=paul@pwsan.com \
    --cc=r-woodruff2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox