rx51: "omapfb: no driver for display"

rx51: "omapfb: no driver for display"

[Sebastian Reichel]

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

Hi,

I've got problems getting a working tty with the mainline 2.6.38
kernel on my Nokia N900. Here is the related output from dmesg:

$ grep -E "(omapdss|omapfb|acx565akm)" dmesg
[    0.890899] omapdss CORE: clk ick, rate 83000000
[    0.890930] omapdss CORE: clk dss1_fck, rate 96000000
[    0.890991] omapdss CORE: clk dss2_fck, rate 19200000
[    0.891021] omapdss CORE: clk tv_fck, rate 54000000
[    0.891052] omapdss CORE: clk video_fck, rate 96000000
[    0.891143] omapdss CORE: initial ctx id 0
[    0.950469] omapdss CORE: save context
[    0.950714] omapdss CORE: bus_match. dev display0/panel-acx565akm, drv panel-acx565akm
[    0.950775] omapdss CORE: driver_probe: dev display0/panel-acx565akm, drv panel-acx565akm
[    0.950805] omapdss SDI: SDI init
[    1.004455] omapdss CORE: save context
[    1.059173] omapdss CORE: save context
[    1.113830] omapdss CORE: save context
[    1.129608] acx565akm spi1.2: omapfb: acx565akm rev 8b LCD detected
[    1.130065] omapdss CORE: probe done for device display0
[    1.130096] omapdss CORE: bus_match. dev display1/venc, drv panel-acx565akm
[    1.303741] OMAPFB: omapfb_init
[    1.303894] OMAPFB: omapfb_probe
[    1.303924] omapfb omapfb: no driver for display
[    1.304016] omapfb omapfb: failed to setup omapfb

You can find the full dmesg and the full kernel config at [0] and
[1]. Can you tell me the reason for the "no driver for display"
message? I thought acx565akm has been registered as display driver
directly before.

[0] http://pkg-n900.alioth.debian.org/kernel/2.6.38/config-2.6.38-1-omap
[1] http://pkg-n900.alioth.debian.org/kernel/2.6.38/dmesg

-- Sebastian

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

RE: rx51: "omapfb: no driver for display"

[Hiremath, Vaibhav]

> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of Sebastian Reichel
> Sent: Sunday, March 27, 2011 8:09 AM
> To: linux-omap@vger.kernel.org
> Subject: rx51: "omapfb: no driver for display"
> 
> Hi,
> 
> I've got problems getting a working tty with the mainline 2.6.38
> kernel on my Nokia N900. Here is the related output from dmesg:
> 
> $ grep -E "(omapdss|omapfb|acx565akm)" dmesg
> [    0.890899] omapdss CORE: clk ick, rate 83000000
> [    0.890930] omapdss CORE: clk dss1_fck, rate 96000000
> [    0.890991] omapdss CORE: clk dss2_fck, rate 19200000
> [    0.891021] omapdss CORE: clk tv_fck, rate 54000000
> [    0.891052] omapdss CORE: clk video_fck, rate 96000000
> [    0.891143] omapdss CORE: initial ctx id 0
> [    0.950469] omapdss CORE: save context
> [    0.950714] omapdss CORE: bus_match. dev display0/panel-acx565akm, drv
> panel-acx565akm
> [    0.950775] omapdss CORE: driver_probe: dev display0/panel-acx565akm,
> drv panel-acx565akm
> [    0.950805] omapdss SDI: SDI init
> [    1.004455] omapdss CORE: save context
> [    1.059173] omapdss CORE: save context
> [    1.113830] omapdss CORE: save context
> [    1.129608] acx565akm spi1.2: omapfb: acx565akm rev 8b LCD detected
> [    1.130065] omapdss CORE: probe done for device display0
> [    1.130096] omapdss CORE: bus_match. dev display1/venc, drv panel-
> acx565akm
> [    1.303741] OMAPFB: omapfb_init
> [    1.303894] OMAPFB: omapfb_probe
> [    1.303924] omapfb omapfb: no driver for display
> [    1.304016] omapfb omapfb: failed to setup omapfb
> 
[Hiremath, Vaibhav] it looks like you do not have all display's connected/selected in you board hook up file.

Please refer to the file board-rx51-video.c, where you can find number of displays registered for rx51 platform.

In case of rx51, you have 2 registered displays, lcd and TV.

Thanks,
Vaibhav

> You can find the full dmesg and the full kernel config at [0] and
> [1]. Can you tell me the reason for the "no driver for display"
> message? I thought acx565akm has been registered as display driver
> directly before.
> 
> [0] http://pkg-n900.alioth.debian.org/kernel/2.6.38/config-2.6.38-1-omap
> [1] http://pkg-n900.alioth.debian.org/kernel/2.6.38/dmesg
> 
> -- Sebastian

Re: rx51: "omapfb: no driver for display"

[Tomi Valkeinen]

On Sun, 2011-03-27 at 04:39 +0200, Sebastian Reichel wrote:
> Hi,
> 
> I've got problems getting a working tty with the mainline 2.6.38
> kernel on my Nokia N900. Here is the related output from dmesg:
> 
> $ grep -E "(omapdss|omapfb|acx565akm)" dmesg
> [    0.890899] omapdss CORE: clk ick, rate 83000000
> [    0.890930] omapdss CORE: clk dss1_fck, rate 96000000
> [    0.890991] omapdss CORE: clk dss2_fck, rate 19200000
> [    0.891021] omapdss CORE: clk tv_fck, rate 54000000
> [    0.891052] omapdss CORE: clk video_fck, rate 96000000
> [    0.891143] omapdss CORE: initial ctx id 0
> [    0.950469] omapdss CORE: save context
> [    0.950714] omapdss CORE: bus_match. dev display0/panel-acx565akm, drv panel-acx565akm
> [    0.950775] omapdss CORE: driver_probe: dev display0/panel-acx565akm, drv panel-acx565akm
> [    0.950805] omapdss SDI: SDI init
> [    1.004455] omapdss CORE: save context
> [    1.059173] omapdss CORE: save context
> [    1.113830] omapdss CORE: save context
> [    1.129608] acx565akm spi1.2: omapfb: acx565akm rev 8b LCD detected
> [    1.130065] omapdss CORE: probe done for device display0
> [    1.130096] omapdss CORE: bus_match. dev display1/venc, drv panel-acx565akm
> [    1.303741] OMAPFB: omapfb_init
> [    1.303894] OMAPFB: omapfb_probe
> [    1.303924] omapfb omapfb: no driver for display
> [    1.304016] omapfb omapfb: failed to setup omapfb
> 
> You can find the full dmesg and the full kernel config at [0] and
> [1]. Can you tell me the reason for the "no driver for display"
> message? I thought acx565akm has been registered as display driver
> directly before.

You also need VENC driver for the tv-out: CONFIG_OMAP2_DSS_VENC

Granted, DSS could handle this case a bit better, by continuing but
refusing to let the user enable the tv-out...

 Tomi

Re: rx51: "omapfb: no driver for display"

[Sebastian Reichel]

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

On Mon, Mar 28, 2011 at 09:01:29AM +0300, Tomi Valkeinen wrote:
> On Sun, 2011-03-27 at 04:39 +0200, Sebastian Reichel wrote:
> > Hi,
> > 
> > I've got problems getting a working tty with the mainline 2.6.38
> > kernel on my Nokia N900. Here is the related output from dmesg:
> > 
> > $ grep -E "(omapdss|omapfb|acx565akm)" dmesg
> > [    0.890899] omapdss CORE: clk ick, rate 83000000
> > [    0.890930] omapdss CORE: clk dss1_fck, rate 96000000
> > [    0.890991] omapdss CORE: clk dss2_fck, rate 19200000
> > [    0.891021] omapdss CORE: clk tv_fck, rate 54000000
> > [    0.891052] omapdss CORE: clk video_fck, rate 96000000
> > [    0.891143] omapdss CORE: initial ctx id 0
> > [    0.950469] omapdss CORE: save context
> > [    0.950714] omapdss CORE: bus_match. dev display0/panel-acx565akm, drv panel-acx565akm
> > [    0.950775] omapdss CORE: driver_probe: dev display0/panel-acx565akm, drv panel-acx565akm
> > [    0.950805] omapdss SDI: SDI init
> > [    1.004455] omapdss CORE: save context
> > [    1.059173] omapdss CORE: save context
> > [    1.113830] omapdss CORE: save context
> > [    1.129608] acx565akm spi1.2: omapfb: acx565akm rev 8b LCD detected
> > [    1.130065] omapdss CORE: probe done for device display0
> > [    1.130096] omapdss CORE: bus_match. dev display1/venc, drv panel-acx565akm
> > [    1.303741] OMAPFB: omapfb_init
> > [    1.303894] OMAPFB: omapfb_probe
> > [    1.303924] omapfb omapfb: no driver for display
> > [    1.304016] omapfb omapfb: failed to setup omapfb
> > 
> > You can find the full dmesg and the full kernel config at [0] and
> > [1]. Can you tell me the reason for the "no driver for display"
> > message? I thought acx565akm has been registered as display driver
> > directly before.
> 
> You also need VENC driver for the tv-out: CONFIG_OMAP2_DSS_VENC

thanks, that fixes the problem.

> Granted, DSS could handle this case a bit better, by continuing but
> refusing to let the user enable the tv-out...

uhm yes :) But first of all it would help to know which driver is
missing. Perhaps something like "no driver for display1/venc".

-- Sebastian

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]