From: Tony Lindgren <tony@atomide.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: linux-omap <linux-omap@vger.kernel.org>,
Felipe Balbi <balbi@ti.com>,
Varadarajan Charulatha <charu@ti.com>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: Nokia n810 LCD (MIPID/blizzard) on 2.6.38
Date: Wed, 2 Mar 2011 10:30:33 -0800 [thread overview]
Message-ID: <20110302183033.GD20560@atomide.com> (raw)
In-Reply-To: <1298925943.16391.19.camel@marge>
* Michael Buesch <mb@bu3sch.de> [110228 12:43]:
>
> 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:
The long term solution is to allow passing options to the
hwmod framework to not reset pins from both board-*.c
files and from cmdline.
For this case it would be nice to pass info from the board-*.c
file to hwmod so it knows to skip reset only for this GPIO.
For booting Linux from other OS, something like
hwmod.reset_disable=all is needed to keep the LCD on.
Regrads,
Tony
next prev parent reply other threads:[~2011-03-02 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 20:45 Nokia n810 LCD (MIPID/blizzard) on 2.6.38 Michael Buesch
2011-03-01 9:20 ` 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 [this message]
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=20110302183033.GD20560@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=charu@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=paul@pwsan.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.