public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: linux-omap <linux-omap@vger.kernel.org>
Cc: Felipe Balbi <balbi@ti.com>, Varadarajan Charulatha <charu@ti.com>
Subject: Nokia n810 LCD (MIPID/blizzard) on 2.6.38
Date: Mon, 28 Feb 2011 21:45:43 +0100	[thread overview]
Message-ID: <1298925943.16391.19.camel@marge> (raw)

The n810 LCD does not work on the 2.6.38(-rc6) kernel
due to changes in the OMAP GPIO-hwmod code.

The hwmod code performs a soft-reset on the GPIO
module. The first GPIO module carries the MIPID
"nreset" line, which is toggled due to the hwmod soft reset.
This resets Blizzard and breaks it, because
it assumes the LCD was left in the state that the
bootloader initialized it to:

	if (!(blizzard_read_reg(BLIZZARD_PLL_DIV) & 0x80)) {
		dev_err(fbdev->dev,
			  "controller not initialized by the bootloader\n");
		r = -ENODEV;
		goto err3;
	}

My temporary workaround to this issue is to disable
soft reset for the first GPIO module:

	static struct omap_hwmod omap2420_gpio1_hwmod = {
		.name           = "gpio1",
		.flags          = HWMOD_INIT_NO_RESET, /* Workaround: Don't reset the n810 MIPID */

I'm wondering if a better fix suitable for the mainline
kernel inclusion could be found.
Any ideas?

-- 
Greetings, Michael.





             reply	other threads:[~2011-02-28 20:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 20:45 Michael Buesch [this message]
2011-03-01  9:20 ` Nokia n810 LCD (MIPID/blizzard) on 2.6.38 Felipe Balbi
2011-03-01 14:23   ` Michael Büsch
2011-03-01 14:39     ` Felipe Balbi
2011-03-01 16:23 ` Varadarajan, Charulatha
2011-03-01 16:29   ` Michael Büsch
2011-03-02  4:41     ` Varadarajan, Charulatha
2011-03-02 18:30 ` Tony Lindgren
2011-03-10  1:18 ` Paul Walmsley
2011-03-10  5:49   ` Michael Büsch

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=1298925943.16391.19.camel@marge \
    --to=mb@bu3sch.de \
    --cc=balbi@ti.com \
    --cc=charu@ti.com \
    --cc=linux-omap@vger.kernel.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