linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: Fix DEBUG_LL for omap zoom2/3
Date: Mon, 22 Mar 2010 18:25:18 -0700	[thread overview]
Message-ID: <20100323012518.GZ11448@atomide.com> (raw)
In-Reply-To: <20100322212025.GW11448@atomide.com>

* Tony Lindgren <tony@atomide.com> [100322 14:15]:
> 
> BTW, I'm still seeing mux errors on zoom3, have not yet
> looked into those.

Looks like we're currently missing these pins. Still need
to be checked for GPIO values and modes though, posting just
for reference as this fixes the "mux: Unknown ball offset"
on 3630.

Regards,

Tony

  reply	other threads:[~2010-03-23  1:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-20  0:36 [PATCH] arm: Fix DEBUG_LL for omap zoom2/3 Tony Lindgren
2010-03-20  0:47 ` Tony Lindgren
2010-03-20  2:48   ` Tony Lindgren
2010-03-20  3:02     ` Tony Lindgren
2010-03-20 23:00       ` Pandita, Vikram
2010-03-23  0:09         ` Tony Lindgren
2010-03-22  7:18     ` Pais, Allen
2010-03-22 21:20       ` Tony Lindgren
2010-03-23  1:25         ` Tony Lindgren [this message]
2010-03-23  5:46         ` Pais, Allen
2010-03-23 15:27           ` Tony Lindgren
2010-03-23 22:49             ` mmc errors (was Re: [PATCH] arm: Fix DEBUG_LL for omap zoom2/3) Nishanth Menon
2010-03-24 15:31               ` Madhusudhan
2010-03-24 15:32               ` Madhusudhan
2010-03-24 15:35               ` Madhusudhan
2010-03-24 15:52                 ` Laurent Epinat
2010-03-30 23:35             ` [PATCH] arm: Fix DEBUG_LL for omap zoom2/3 Madhusudhan
2010-03-31  6:11               ` G, Manjunath Kondaiah
2010-03-31 16:46                 ` Madhusudhan
2010-04-06 16:51             ` Aguirre, Sergio
  -- strict thread matches above, loose matches on Subject: below --
2010-03-20  0:18 Tony Lindgren
2010-03-20  0:18 Tony Lindgren
2010-03-20  0:18 Tony Lindgren
2010-03-20  0:18 Tony Lindgren

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=20100323012518.GZ11448@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).