From: "Michael Büsch" <mb@bu3sch.de>
To: "Varadarajan, Charulatha" <charu@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>, Felipe Balbi <balbi@ti.com>
Subject: Re: Nokia n810 LCD (MIPID/blizzard) on 2.6.38
Date: Tue, 01 Mar 2011 17:29:41 +0100 [thread overview]
Message-ID: <1298996981.6461.5.camel@maggie> (raw)
In-Reply-To: <AANLkTikmwLoUPJrFZ2o7qsO8MbxBLe2hMbetwxeToW-Z@mail.gmail.com> (sfid-20110301_172419_032506_64300D9A)
On Tue, 2011-03-01 at 11:23 -0500, Varadarajan, Charulatha wrote:
> > 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 */
>
> NACK.
>
> As the problem is specific to the board settings, this shall be handled
> in the board file itself.
Yeah, sure. But how can I handle this in the board file? Is
there a hwmod API for this?
> > I'm wondering if a better fix suitable for the mainline
> > kernel inclusion could be found.
> > Any ideas?
>
> Re-initialize the "nreset" line of the Blizzard in the
> corresponding board file.
That is not sufficient. The blizzard chip has to be reinitialized
completely.
Code for that doesn't exist in the current driver. It currently depends
on the bootloader doing the lowlevel init. As long as I don't have
documentation for that chip, I'm stuck with that.
--
Greetings Michael.
next prev parent reply other threads:[~2011-03-01 16:29 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 [this message]
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=1298996981.6461.5.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