All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Thomas Gleixner <tglx@linutronix.de>,
	Tony Lindgren <tony@atomide.com>,
	linus.walleij@linaro.org, Daniel Walker <dwalker@fifo99.com>,
	Lennert Buytenhek <kernel@wantstofly.org>,
	Kukjin Kim <kgene.kim@samsung.com>,
	Barry Song <21cnbao@gmail.com>,
	Bryan Huntsman <bryanh@codeaurora.org>,
	Russell King <rmk+kernel@arm.linux.org.uk>,
	David Brown <davidb@codeaurora.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Stephen Warren <swarren@wwwdotorg.org>,
	John Stultz <john.stultz@linaro.org>,
	Ben Dooks <ben-linux@fluff.org>,
	Alexander Schulz <alex@shark-linux.de>,
	Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
	Andrew Victor <linux@maxim.org.za>,
	Linux ARM Kernel Mailing List
	<linux-arm-kernel@lists.infradead.org>,
	Paul Walmsley <paul@pwsan.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Santosh
Subject: Re: [PATCH v2] arm: sched: stop sched_clock() during suspend
Date: Tue, 23 Oct 2012 07:14:48 -0700	[thread overview]
Message-ID: <87mwzdcm1z.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1350971854-9161-1-git-send-email-balbi@ti.com> (Felipe Balbi's message of "Tue, 23 Oct 2012 08:57:34 +0300")

Felipe Balbi <balbi@ti.com> writes:

> The scheduler imposes a requirement to sched_clock()
> which is to stop the clock during suspend, if we don't
> do that any RT thread will be rescheduled in the future
> which might cause any sort of problems.
>
> This became an issue on OMAP when we converted omap-i2c.c
> to use threaded IRQs, it turned out that depending on how
> much time we spent on suspend, the I2C IRQ thread would
> end up being rescheduled so far in the future that I2C
> transfers would timeout and, because omap_hsmmc depends
> on an I2C-connected device to detect if an MMC card is
> inserted in the slot, our rootfs would just vanish.
>
> arch/arm/kernel/sched_clock.c already had an optional
> implementation (sched_clock_needs_suspend()) which would
> handle scheduler's requirement properly, what this patch
> does is simply to make that implementation non-optional.
>
> Note that this has the side-effect that printk timings
> won't reflect the actual time spent on suspend so other
> methods to measure that will have to be used.
>
> This has been tested with beagleboard XM (OMAP3630) and
> pandaboard rev A3 (OMAP4430). Suspend to RAM is now working
> after this patch.
>
> Signed-off-by: Felipe Balbi <balbi@ti.com>

Acked-by: Kevin Hilman <khilman@ti.com>

WARNING: multiple messages have this Message-ID (diff)
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm: sched: stop sched_clock() during suspend
Date: Tue, 23 Oct 2012 07:14:48 -0700	[thread overview]
Message-ID: <87mwzdcm1z.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1350971854-9161-1-git-send-email-balbi@ti.com> (Felipe Balbi's message of "Tue, 23 Oct 2012 08:57:34 +0300")

Felipe Balbi <balbi@ti.com> writes:

> The scheduler imposes a requirement to sched_clock()
> which is to stop the clock during suspend, if we don't
> do that any RT thread will be rescheduled in the future
> which might cause any sort of problems.
>
> This became an issue on OMAP when we converted omap-i2c.c
> to use threaded IRQs, it turned out that depending on how
> much time we spent on suspend, the I2C IRQ thread would
> end up being rescheduled so far in the future that I2C
> transfers would timeout and, because omap_hsmmc depends
> on an I2C-connected device to detect if an MMC card is
> inserted in the slot, our rootfs would just vanish.
>
> arch/arm/kernel/sched_clock.c already had an optional
> implementation (sched_clock_needs_suspend()) which would
> handle scheduler's requirement properly, what this patch
> does is simply to make that implementation non-optional.
>
> Note that this has the side-effect that printk timings
> won't reflect the actual time spent on suspend so other
> methods to measure that will have to be used.
>
> This has been tested with beagleboard XM (OMAP3630) and
> pandaboard rev A3 (OMAP4430). Suspend to RAM is now working
> after this patch.
>
> Signed-off-by: Felipe Balbi <balbi@ti.com>

Acked-by: Kevin Hilman <khilman@ti.com>

  reply	other threads:[~2012-10-23 14:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 11:54 [PATCH] arm: sched: stop sched_clock() during suspend Felipe Balbi
2012-10-22 11:54 ` Felipe Balbi
2012-10-22 12:07 ` Felipe Balbi
2012-10-22 12:07   ` Felipe Balbi
2012-10-22 12:07   ` Felipe Balbi
2012-10-22 17:05 ` Kevin Hilman
2012-10-22 17:05   ` Kevin Hilman
2012-10-22 17:05   ` Kevin Hilman
2012-10-22 22:28   ` Linus Walleij
2012-10-22 22:28     ` Linus Walleij
2012-10-22 22:28     ` Linus Walleij
2012-10-23  9:22     ` Russell King - ARM Linux
2012-10-23  9:22       ` Russell King - ARM Linux
2012-10-23 14:17       ` Kevin Hilman
2012-10-23 14:17         ` Kevin Hilman
2012-10-23 16:03         ` Russell King - ARM Linux
2012-10-23 16:03           ` Russell King - ARM Linux
2012-10-23 17:24           ` Felipe Balbi
2012-10-23 17:24             ` Felipe Balbi
2012-10-23  5:57   ` [PATCH v2] " Felipe Balbi
2012-10-23  5:57     ` Felipe Balbi
2012-10-23 14:14     ` Kevin Hilman [this message]
2012-10-23 14:14       ` Kevin Hilman
2012-10-23 10:11 ` [PATCH] " Linus Walleij
2012-10-23 10:11   ` Linus Walleij

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=87mwzdcm1z.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=21cnbao@gmail.com \
    --cc=alex@shark-linux.de \
    --cc=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=balbi@ti.com \
    --cc=ben-linux@fluff.org \
    --cc=bryanh@codeaurora.org \
    --cc=davidb@codeaurora.org \
    --cc=dwalker@fifo99.com \
    --cc=john.stultz@linaro.org \
    --cc=kernel@wantstofly.org \
    --cc=kgene.kim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@maxim.org.za \
    --cc=paul@pwsan.com \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=swarren@wwwdotorg.org \
    --cc=tglx@linutronix.de \
    --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 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.