All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: Steve Sakoman <sakoman@gmail.com>,
	Enric Balletbo Serra <eballetbo@gmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	Javier Martinez Canillas <javier@dowhile0.org>
Subject: Re: omap DSS fails with tft410 driver panel?
Date: Wed, 19 Dec 2012 10:33:19 +0200	[thread overview]
Message-ID: <50D17BCF.1080108@ti.com> (raw)
In-Reply-To: <CAAwP0s2ksE1wbb4Y3k3+_XeR5DLTgOsOAo63arh4f9F942nGdQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1850 bytes --]

On 2012-12-18 15:45, Javier Martinez Canillas wrote:
> Hi,
> 
> I've tested with the latest stable kernel (Linux 3.7.1) and the video
> output is working correctly with the same user-space components.
> The complete dmesg is here: http://fpaste.org/1Kv4/
> 
> Looking at the logs for both kernels I realized that there are two
> differences main between the working (3.7.1) and non-working
> (mainline) kernel (besides the versions of course):
> 
> a) The number of framebuffers created (working 1, non working 3)
> b) The omapfb now uses dma_alloc_attrs to allocate memory instead of
> the now removed OMAP-specific omap_vram_alloc
> 
> For a) I built mainline with CONFIG_FB_OMAP2_NUM_FBS=1 and that made
> the error about the overlay paddr being zero disappear (OVERLAY error:
> check_overlay: paddr cannot be 0) but still no video on the screen.

Ok. I think the reason for that is that the paddr errors come from X
trying to setup the video overlays with paddr 0. The video overlays are
by default on fb1 and fb2, so they are not present if you set the
NUM_FBS to 1.

> Conversely I build 3.7.1 with CONFIG_FB_OMAP2_NUM_FBS=3 and even
> though I had the paddr can't be zero error, video is working
> correctly. So it seems that error shouldn't affect the video display.

Hmm, so do you get any display with 3.8, before X is started, using
plain fb? For example, break the boot before X is started, and do

cat /dev/urandom > /dev/fb0

Do you have an userspace image I could download to reproduce this?

> For b) I tried to built mainline with CONFIG_CMA=y but it didn't work either.

I don't think the vram change affects this, except if you see errors
about mem alloc. But yes, I think you should enable CMA with 3.8,
although allocation may work fine for smaller displays even without CMA.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]

  reply	other threads:[~2012-12-19  8:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-11 15:58 omap DSS fails with tft410 driver panel? Enric Balletbo Serra
2012-10-12 10:56 ` Tomi Valkeinen
2012-10-15 16:08   ` Enric Balletbo Serra
2012-10-16  7:30     ` Tomi Valkeinen
2012-11-22  0:08 ` Steve Sakoman
2012-11-22  8:47   ` Tomi Valkeinen
2012-11-23  6:14     ` Steve Sakoman
2012-11-23  8:46       ` Tomi Valkeinen
2012-11-23 15:20         ` Steve Sakoman
2012-11-27 11:32           ` Tomi Valkeinen
2012-11-27 19:15             ` Steve Sakoman
2012-11-29 11:22               ` Tomi Valkeinen
2012-11-29 11:33                 ` Enric Balletbo Serra
2012-11-29 14:24                   ` Steve Sakoman
2012-11-29 14:30                     ` Enric Balletbo Serra
2012-11-29 14:18                 ` Steve Sakoman
2012-11-29 14:31                   ` Tomi Valkeinen
2012-11-29 14:53                     ` Steve Sakoman
2012-11-29 14:56                       ` Tomi Valkeinen
2012-12-18  8:31                         ` Javier Martinez Canillas
2012-12-18 11:23                           ` Javier Martinez Canillas
2012-12-18 13:45                             ` Javier Martinez Canillas
2012-12-19  8:33                               ` Tomi Valkeinen [this message]
2012-12-19 11:27                                 ` Javier Martinez Canillas
2012-12-19  8:24                           ` Tomi Valkeinen
2012-12-21  8:30   ` Laurent Pinchart
2012-12-21 10:19     ` Javier Martinez Canillas
2013-09-12 11:12       ` pawel cern

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=50D17BCF.1080108@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=eballetbo@gmail.com \
    --cc=javier@dowhile0.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=martinez.javier@gmail.com \
    --cc=sakoman@gmail.com \
    --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.