public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Marc Murphy <marcmltd@marcm.co.uk>
Cc: "'linux-omap@vger.kernel.org'" <linux-omap@vger.kernel.org>
Subject: Re: Initialising omapfb on AM3517 issues
Date: Wed, 19 Sep 2012 10:23:41 +0300	[thread overview]
Message-ID: <1348039421.2565.6.camel@deskari> (raw)
In-Reply-To: <F690310232FDDF4AB457E8B3EF90DDE05D7B4BDE@MARCM-SBS2011.marcmltd.local>

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

Hi,

On Tue, 2012-09-18 at 16:41 +0000, Marc Murphy wrote:
> Hello all,
> I have been moving from the ti 2.6.37 BSP to the 3.x kernel with quite a bit of success, the main issue I have at the moment is trying to get the frame buffer and any displays I have initialised.
> 
> [    2.805358] omapfb omapfb: no driver for display: lcd
> [    2.810729] omapfb omapfb: no displays
> [    2.814666] omapfb omapfb: failed to setup omapfb
> 
> I have tried a few versions of release and none of them will initialise;
> 
> Currently on
> [    0.000000] Linux version 3.6.0-rc3
> 
> I have started with board-am3517evm display config and even that doesn't initialise.  Is there something I am missing with the configs or is there a patch required to get the feature to work.
> 
> My current config options use;
> #
> # Graphics support
> #
> CONFIG_DRM=y

omapdrm and omapfb cannot be used at the same time. That said, you don't
seem to enable omapdrm, only the core drm support, so it shouldn't
matter. But you don't need CONFIG_DRM if you use omapfb.

> CONFIG_FB=y
> CONFIG_FB_CFB_FILLRECT=y
> CONFIG_FB_CFB_COPYAREA=y
> CONFIG_FB_CFB_IMAGEBLIT=y
> 
> #
> # Frame buffer hardware drivers
> #
> CONFIG_OMAP2_VRAM=y
> CONFIG_OMAP2_VRFB=y
> CONFIG_OMAP2_DSS=y
> CONFIG_OMAP2_VRAM_SIZE=12
> CONFIG_OMAP2_DSS_DPI=y
> CONFIG_OMAP2_DSS_VENC=y
> CONFIG_OMAP2_DSS_DSI=y
> CONFIG_OMAP2_DSS_MIN_FCK_PER_PCK=1
> CONFIG_OMAP2_DSS_SLEEP_AFTER_VENC_RESET=y
> CONFIG_FB_OMAP2=y
> CONFIG_FB_OMAP2_NUM_FBS=3
> 
> #
> # OMAP2/3 Display Device Drivers
> #
> CONFIG_PANEL_GENERIC_DPI=y
> CONFIG_PANEL_SHARP_LS037V7DW01=y
> CONFIG_BACKLIGHT_LCD_SUPPORT=y
> CONFIG_LCD_CLASS_DEVICE=y
> CONFIG_BACKLIGHT_CLASS_DEVICE=y
> CONFIG_BACKLIGHT_GENERIC=y
> 
> And the init structs are
> static int am3517_evm_panel_enable_lcd(struct omap_dss_device *dssdev)
> {
>     gpio_set_value(TAM3517_DVI_PON_GPIO, 0);
>     gpio_set_value(TAM3517_LCD_ENVDD_GPIO, 0);
>     gpio_set_value(TAM3517_LCD_PON_GPIO, 1);
>         printk("LCD voltage on\n");
> 	return 0;
> }
> 
> static void am3517_evm_panel_disable_lcd(struct omap_dss_device *dssdev)
> {
>     gpio_set_value(TAM3517_LCD_ENVDD_GPIO, 1);
>     gpio_set_value(TAM3517_LCD_PON_GPIO, 0);
> }
> 
> static struct panel_generic_dpi_data lcd_panel = {
> //    .name			= "generic_dpi_panel",

You need to define name for the panel you have. You can see the list of
supported panels in drivers/video/omap2/displays/panel-generic-dpi.c. If
you don't give a name, the panel driver doesn't start.

There's also a problem with the vdds_dsi regulator. Search the list for
"[PATCH] OMAPDSS: Do not require a VDDS_DSI regulator on am35xx". The
patch to fix it hasn't been merged yet.

 Tomi


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-09-19  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18 16:41 Initialising omapfb on AM3517 issues Marc Murphy
2012-09-19  7:23 ` Tomi Valkeinen [this message]
2012-09-22 20:35   ` Marc Murphy

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=1348039421.2565.6.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=marcmltd@marcm.co.uk \
    /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