From: "Michael Büsch" <mb@bu3sch.de>
To: balbi@ti.com
Cc: linux-omap <linux-omap@vger.kernel.org>,
Varadarajan Charulatha <charu@ti.com>
Subject: Re: Nokia n810 LCD (MIPID/blizzard) on 2.6.38
Date: Tue, 01 Mar 2011 15:23:15 +0100 [thread overview]
Message-ID: <1298989395.6461.2.camel@maggie> (raw)
In-Reply-To: <20110301092057.GA2942@legolas.emea.dhcp.ti.com> (sfid-20110301_102108_023001_FFFFFFFFACB50B7A)
On Tue, 2011-03-01 at 11:20 +0200, Felipe Balbi wrote:
> On Mon, Feb 28, 2011 at 09:45:43PM +0100, Michael Buesch wrote:
> > 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:
>
> so that's the bug which needs to be fixed. Unfortunately I don't have
> any documentation available anymore. Maybe someone from Nokia would fix
> that ?
>
> > I'm wondering if a better fix suitable for the mainline
> > kernel inclusion could be found.
> > Any ideas?
>
> Don't depend on the bootloader :-)
Yeah that's the obvious fix, of course. However, it requires
deep knowledge of the device and/or hardware documentation. Both
of which I don't have.
The driver also doesn't seem to have a maintainer.
If someone can get me documentation, I'm willing to implement
the required bits to remove the bootloader dependency.
--
Greetings Michael.
next prev parent reply other threads:[~2011-03-01 14:23 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 [this message]
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=1298989395.6461.2.camel@maggie \
--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