From: Tony Lindgren <tony@atomide.com>
To: Manjunatha GK <manjugk@ti.com>
Cc: linux-omap@vger.kernel.org, Allen Pais <allen.pais@ti.com>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH] omap3: Fix 3630 mux errors
Date: Thu, 29 Apr 2010 14:10:20 -0700 [thread overview]
Message-ID: <20100429211020.GA29604@atomide.com> (raw)
In-Reply-To: <20100429182512.GN7225@atomide.com>
* Tony Lindgren <tony@atomide.com> [100429 11:20]:
> * Manjunatha GK <manjugk@ti.com> [100429 00:23]:
> > From: Allen Pais <allen.pais@ti.com>
> >
> > The omap3630 has more mux signals than 34xx. The additional
> > pins exist in omap36xx_cbp_subset, but are not initialized
> > as the superset is missing these offsets. This causes the
> > following errors during the boot:
>
> I have an earlier version of this queued up, will take a look
> and see if they're the same:
>
> https://patchwork.kernel.org/patch/87555/
Turns out these are all non-muxable pins. So the right fix
is to remove them from the 3630 ball table. Will post a patch
shortly for this along with my other fixes.
Regards,
Tony
prev parent reply other threads:[~2010-04-30 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 7:27 [PATCH] omap3: Fix 3630 mux errors Manjunatha GK
2010-04-29 18:25 ` Tony Lindgren
2010-04-29 21:10 ` Tony Lindgren [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=20100429211020.GA29604@atomide.com \
--to=tony@atomide.com \
--cc=allen.pais@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@ti.com \
--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.