linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ilya Yanok <yanok@emcraft.com>
To: Archit Taneja <a0393947@ti.com>
Cc: linux-omap@vger.kernel.org, "paul@pwsan.com" <paul@pwsan.com>
Subject: Re: Interesting L3 driver panic on v3.2-rc5 on 3530
Date: Thu, 22 Dec 2011 05:05:24 +0400	[thread overview]
Message-ID: <4EF28254.3080009@emcraft.com> (raw)
In-Reply-To: <4EF07E2A.7030201@ti.com>

Hi Archit, Paul,

On 20.12.2011 16:23, Archit Taneja wrote:
> There was a patch which got into the kernel in 3.2-rc4:
> 
> b923d40dd4211c4ef7d4efa2bd81b7ca1d8744c1
> ARM: OMAP2PLUS: DSS: Ensure DSS works correctly if display is enabled in
> bootloader
> 
> This tries to disable any display outputs if enabled in bootloader. If
> this issue didn't happen before, we might want to look into this code.
> 
> Could you share what debug prints you get from the function
> omap_dss_reset() (its in arch/arm/mach-omap2/display.c)

In my case the bottom part of dispc_disable_outputs() is never executed
as dss_dispc is reset but omap_hwmod_setup_all function and when
dispc_disable_outputs is executed it sees that the display is disabled
already.

I've just posted a patch to fix this.

Regards, Ilya.

      parent reply	other threads:[~2011-12-22  1:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17  2:02 Interesting L3 driver panic on v3.2-rc5 on 3530 Paul Walmsley
2011-12-17  5:14 ` Shilimkar, Santosh
2011-12-20  0:39 ` Ilya Yanok
2011-12-20 12:23   ` Archit Taneja
2011-12-20 19:15     ` Ilya Yanok
2011-12-22  1:05     ` Ilya Yanok [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=4EF28254.3080009@emcraft.com \
    --to=yanok@emcraft.com \
    --cc=a0393947@ti.com \
    --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).