From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Kevin Hilman <khilman@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 3/3] ARM: OMAP: omap_device: idle devices with no driver bound
Date: Fri, 17 Aug 2012 00:52:41 -0700 [thread overview]
Message-ID: <20120817075240.GM11011@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1208101658130.29149@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [120810 15:59]:
> On Fri, 10 Aug 2012, Kevin Hilman wrote:
>
> > Under some circumstances, drivers may leave an omap_device enabled due
> > to driver programming errors, or due to a failure in the drivers
> > probe method.
> >
> > Using the recently added omap_device driver_status field, we can
> > detect conditions where an omap_device is enabled but has no driver
> > bound and then ensure that the device is properly idled until it can
> > be probed again.
> >
> > The goal of this feature is not only to detect and warn on these error
> > conditions, but also to ensure that devices are properly put in
> > low-power states so they do not prevent SoC-wide low-power states.
> >
> > Cc: Paul Walmsley <paul@pwsan.com>
> > Signed-off-by: Kevin Hilman <khilman@ti.com>
>
> Here's the queued version of this one.
Nice to see this happening :)
Tony
next prev parent reply other threads:[~2012-08-17 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 18:39 [PATCH v2 0/3] ARM: OMAP: omap_device: track driver bound status Kevin Hilman
2012-08-10 18:39 ` [PATCH v2 1/3] ARM: OMAP: omap_device: keep track of " Kevin Hilman
2012-08-10 18:39 ` [PATCH v2 2/3] ARM: OMAP: omap_device: don't attempt late suspend if no driver bound Kevin Hilman
2012-08-10 18:39 ` [PATCH v2 3/3] ARM: OMAP: omap_device: idle devices with " Kevin Hilman
2012-08-10 22:59 ` Paul Walmsley
2012-08-17 7:52 ` Tony Lindgren [this message]
2012-08-10 22:57 ` [PATCH v2 0/3] ARM: OMAP: omap_device: track driver bound status Paul Walmsley
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=20120817075240.GM11011@atomide.com \
--to=tony@atomide.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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;
as well as URLs for NNTP newsgroup(s).