linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: DSS errors in linux next when booted with DTB append
Date: Tue, 5 Feb 2013 11:06:19 -0800	[thread overview]
Message-ID: <20130205190619.GN25185@atomide.com> (raw)
In-Reply-To: <5110FD01.7010605@ti.com>

* Tomi Valkeinen <tomi.valkeinen@ti.com> [130205 04:40]:
> Hi,
> 
> On 2013-01-16 21:08, Tony Lindgren wrote:
> > Hi Tomi,
> > 
> > Looks like omap_dss_init() goes crazy on panda es when booted with 
> > PANEL_TAAL and DTB append enabled, see below. Does not seem to happen when
> > booted on blaze. Noticed this after enabling all the panels, my modified
> > omap2plus_defconfig attached.
> 
> Hmm, looks odd. The log shows it's trying to use Taal panel, even if
> Panda doesn't have such a panel. Who's adding the Taal device? Are you
> booting Panda with Blaze's dtb?

Hmm yeah I might have had Blaze's dtb there, need to check. That
certainly would explain it.
 
> That said, I have seen similar circular locking warnings related to
> omapfb/omapdss, but I haven't been able to resolve them, or even to
> really find out why the warning happens. I haven't seen any problems
> though, it's just a warning.
> 
> So my guess is that you're seeing two unrelated problems, one related to
> dtbs or such, and the other related to locks.

Yeah the locks related one could be caused by spurious interrupts
by some other device if I had Blaze's .dtb in use.

Regards,

Tony

      reply	other threads:[~2013-02-05 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 19:08 DSS errors in linux next when booted with DTB append Tony Lindgren
2013-02-05 12:37 ` Tomi Valkeinen
2013-02-05 19:06   ` Tony Lindgren [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=20130205190619.GN25185@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tomi.valkeinen@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;
as well as URLs for NNTP newsgroup(s).