All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: OMAP display subsystem - does it work?
Date: Thu, 19 Dec 2013 08:56:07 -0800	[thread overview]
Message-ID: <20131219165607.GN27438@atomide.com> (raw)
In-Reply-To: <52B282BE.9050705@ti.com>

* Tomi Valkeinen <tomi.valkeinen@ti.com> [131218 21:24]:
> On 2013-12-18 20:23, Tony Lindgren wrote:
> 
> > Hmm I had the framebuffer working with DT on LDP after fixing the twl4030
> > gpio regression with 0b2aa8bed3e1 (gpio: twl4030: Fix regression for twl
> > gpio output) using this pdata quirks patch:
> > 
> > [PATCH 3/5] ARM: OMAP2+: Add DT init code for DPI displays and make omap3 LDP to use it
> > 
> > AFAIK the pdata hack above should not be needed now, but I have not tried
> > with Tomi's DSS DT patches yet.
> > 
> > Tomi do you have some sample panel dpi .dts entry somewhere for the LDP I
> > could try at some point?
> 
> Hmm, I thought this was about legacy booting on v3.14-rc4. That still
> uses the board files for omap3.

AFAIK 0b2aa8bed3e1 was the only thing needed for legacy booting and it's
in -rc4.
 
> > Russell, maybe all you're missing is just omapfb.vram=0:2M,1:5M or similar
> > from your kernel cmdline?
> 
> Nothing like that should be required for normal operation.

Hmm maybe these instructions need some updating then:

http://omappedia.org/wiki/Bootargs_for_enabling_display

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP display subsystem - does it work?
Date: Thu, 19 Dec 2013 08:56:07 -0800	[thread overview]
Message-ID: <20131219165607.GN27438@atomide.com> (raw)
In-Reply-To: <52B282BE.9050705@ti.com>

* Tomi Valkeinen <tomi.valkeinen@ti.com> [131218 21:24]:
> On 2013-12-18 20:23, Tony Lindgren wrote:
> 
> > Hmm I had the framebuffer working with DT on LDP after fixing the twl4030
> > gpio regression with 0b2aa8bed3e1 (gpio: twl4030: Fix regression for twl
> > gpio output) using this pdata quirks patch:
> > 
> > [PATCH 3/5] ARM: OMAP2+: Add DT init code for DPI displays and make omap3 LDP to use it
> > 
> > AFAIK the pdata hack above should not be needed now, but I have not tried
> > with Tomi's DSS DT patches yet.
> > 
> > Tomi do you have some sample panel dpi .dts entry somewhere for the LDP I
> > could try at some point?
> 
> Hmm, I thought this was about legacy booting on v3.14-rc4. That still
> uses the board files for omap3.

AFAIK 0b2aa8bed3e1 was the only thing needed for legacy booting and it's
in -rc4.
 
> > Russell, maybe all you're missing is just omapfb.vram=0:2M,1:5M or similar
> > from your kernel cmdline?
> 
> Nothing like that should be required for normal operation.

Hmm maybe these instructions need some updating then:

http://omappedia.org/wiki/Bootargs_for_enabling_display

Regards,

Tony

  reply	other threads:[~2013-12-19 16:56 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 12:00 OMAP display subsystem - does it work? Russell King - ARM Linux
2013-12-18 12:00 ` Russell King - ARM Linux
2013-12-18 13:54 ` Tomi Valkeinen
2013-12-18 13:54   ` Tomi Valkeinen
2013-12-18 15:29   ` Russell King - ARM Linux
2013-12-18 15:29     ` Russell King - ARM Linux
2013-12-18 16:03     ` Tomi Valkeinen
2013-12-18 16:03       ` Tomi Valkeinen
2013-12-18 18:23   ` Tony Lindgren
2013-12-18 18:23     ` Tony Lindgren
2013-12-19  5:23     ` Tomi Valkeinen
2013-12-19  5:23       ` Tomi Valkeinen
2013-12-19 16:56       ` Tony Lindgren [this message]
2013-12-19 16:56         ` Tony Lindgren
2013-12-20  7:45         ` Tomi Valkeinen
2013-12-20  7:45           ` Tomi Valkeinen
2013-12-19 17:56     ` Russell King - ARM Linux
2013-12-19 17:56       ` Russell King - ARM Linux
2013-12-19 18:22       ` Tony Lindgren
2013-12-19 18:22         ` Tony Lindgren
2013-12-20 11:27         ` Russell King - ARM Linux
2013-12-20 11:27           ` Russell King - ARM Linux
2013-12-20 11:48           ` Russell King - ARM Linux
2013-12-20 11:48             ` Russell King - ARM Linux
2013-12-20 13:43             ` Tomi Valkeinen
2013-12-20 13:43               ` Tomi Valkeinen
2013-12-20 16:04               ` Tony Lindgren
2013-12-20 16:04                 ` Tony Lindgren
2013-12-20 16:55                 ` Tony Lindgren
2013-12-20 16:55                   ` Tony Lindgren
2013-12-21  0:59                   ` Russell King - ARM Linux
2013-12-21  0:59                     ` Russell King - ARM Linux
2013-12-28 23:30                     ` Russell King - ARM Linux
2013-12-28 23:30                       ` Russell King - ARM Linux
2013-12-23  7:53                   ` Tomi Valkeinen
2013-12-23  7:53                     ` Tomi Valkeinen
2013-12-27 18:11                     ` Tony Lindgren
2013-12-27 18:11                       ` Tony Lindgren
2013-12-23  7:49                 ` Tomi Valkeinen
2013-12-23  7:49                   ` Tomi Valkeinen
2013-12-20 16:10           ` Tony Lindgren
2013-12-20 16:10             ` Tony Lindgren
2013-12-19 17:53   ` Russell King - ARM Linux
2013-12-19 17:53     ` Russell King - ARM Linux

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=20131219165607.GN27438@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --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 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.