linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tomi Valkeinen <tomi.valkeinen@nokia.com>
Cc: ext Grazvydas Ignotas <notasas@gmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] OMAP: DSS: ensure clocks are disabled on failed init
Date: Tue, 27 Apr 2010 08:13:34 -0700	[thread overview]
Message-ID: <87mxwpq675.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1272364829.2529.109.camel@tubuntu.research.nokia.com> (Tomi Valkeinen's message of "Tue\, 27 Apr 2010 13\:40\:29 +0300")

Tomi Valkeinen <tomi.valkeinen@nokia.com> writes:

> Hi,
>
> On Tue, 2010-04-27 at 11:14 +0200, ext Grazvydas Ignotas wrote:
>> CC Tomi in case he missed this.
>
> Thanks =)
>
>> 
>> On Mon, Apr 26, 2010 at 10:12 PM, Kevin Hilman
>> <khilman@deeprootsystems.com> wrote:
>> > Currently, if init fails for whatever reason, various DSS related
>> > clocks will be left enabled and prevent the chip from hitting
>> > retention or off-mode.
>> >
>> > This patch ensures the clocks are disabled on a failed init.
>> >
>> > For this to work, a check had to be added to dispc_save_context()
>> > to not save context if it has not yet been initialized.
>
> The code in omap_dss_probe() is actually quite broken, as the /* XXX
> fail correctly */ hints... At least clocks should be put(), debugfs
> should be uninitialized etc. So this patch is ok quick fix, but I'll try
> to find time to fix the fail path properly.

Thanks.  My main concern of course is that any failed init will ensure
clocks are disabled and the modules are able to idle.

Kevin

      reply	other threads:[~2010-04-27 15:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 19:12 [PATCH] OMAP: DSS: ensure clocks are disabled on failed init Kevin Hilman
2010-04-27  9:14 ` Grazvydas Ignotas
2010-04-27 10:40   ` Tomi Valkeinen
2010-04-27 15:13     ` Kevin Hilman [this message]

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=87mxwpq675.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=notasas@gmail.com \
    --cc=tomi.valkeinen@nokia.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).