mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Juergen Beisert <jbe@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: lcd clock
Date: Mon, 11 Apr 2011 14:19:27 +0200	[thread overview]
Message-ID: <201104111419.27542.jbe@pengutronix.de> (raw)
In-Reply-To: <6EE7D1502C48E44E92DCADF9DD3E0DB90187A40D5121@SRV-VS06.TELEVIC.COM>

Vanalme Filip wrote:
> Is there any specific reason why the (i.MX27) LCDC clocks are disabled in
> imxfb_probe() (drivers\imx.c) ?
>
> #ifdef CONFIG_ARCH_IMX27
> PCCR0 &= ~PCCR0_LCDC_EN;
> PCCR1 &= ~PCCR1_HCLK_LCDC;
> #endif
>
> I would have expected the clocks to be enabled in that routine.
>
> I'm experimenting a little with Barebox's 'bmp' command. Although the
> command did not return any error, I did not have any output on my lcd. Then
> I noticed that the LCDC clocks were not enabled. If the clocks were not
> enabled by default in the probe function, I would expect the enabling in
> the bmp command code, e.g. with FBIO_ENABLE ioctl command. But, as far as I
> can see, FBIO_ENABLE is not executed in the bmp command code.

Try within barebox

fb0.enable=1

This should enable the LCD controller on demand.

jbe

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | Phone: +49-8766-939 228     |
Vertretung Sued/Muenchen, Germany             | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2011-04-11 12:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11 11:54 Vanalme Filip
2011-04-11 12:19 ` Juergen Beisert [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=201104111419.27542.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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