public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Mike Rapoport <mike@compulab.co.il>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] omap3: cm-t35: add mux initialization
Date: Mon, 7 Dec 2009 08:22:09 -0800	[thread overview]
Message-ID: <20091207162209.GV24013@atomide.com> (raw)
In-Reply-To: <4B1BCE62.1050005@compulab.co.il>

* Mike Rapoport <mike@compulab.co.il> [091206 07:30]:
> Tony,
> Any chance this can go to 2.6.33?

Sure, I was just waiting to hear back if the OUTPUT_PULLUP is
needed for sure? Or is just OUTPUT enough for musb to work?

Tony


 
> Mike Rapoport wrote:
> > Tony,
> > 
> > These patches are follow-ups to your mux rework series.
> > The first one is pretty trivial and adds OUTPUT_PULL{UP,DOWN} to shorten
> > the lines in omap_board_mux arrays. 
> > The second patch adds the mux configuration for CM-T35. This is actually
> > the most compact subset of 'cat /sys/kernel/debug/omap_mux/board' that makes
> > CM-T35 functional :)
> > 
> > The following changes since commit d8bfa71e2e9d794f9c7e5b019f316804f7f50582:
> >   Tony Lindgren (1):
> >           omap: mux: Add data for 2430
> > 
> > Mike Rapoport (2):
> >   omap3: mux: add shorthands for OUTPUT_PULL{UP,DOWN}
> >   omap3: cm-t35: add mux initialization
> > 
> >  arch/arm/mach-omap2/Kconfig        |    1 +
> >  arch/arm/mach-omap2/board-cm-t35.c |   95 +++++++++++++++++++++++++++++++++--
> >  arch/arm/mach-omap2/mux.h          |    2 +
> >  3 files changed, 92 insertions(+), 6 deletions(-)
> > 
> > 
> 
> -- 
> Sincerely yours,
> Mike.
> 

  reply	other threads:[~2009-12-07 16:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-29  8:07 [PATCH] omap3: cm-t35: add mux initialization Mike Rapoport
2009-11-29  8:07 ` [PATCH] omap3: mux: add shorthands for OUTPUT_PULL{UP,DOWN} Mike Rapoport
2009-11-30 21:12   ` Tony Lindgren
2009-11-30 21:58     ` Mike Rapoport
2009-11-30 23:10       ` Tony Lindgren
2009-12-01  7:57         ` Mike Rapoport
2009-11-29  8:07 ` [PATCH] omap3: cm-t35: add mux initialization Mike Rapoport
2009-12-06 15:31 ` Mike Rapoport
2009-12-07 16:22   ` Tony Lindgren [this message]
2009-12-07 16:35     ` Gadiyar, Anand
2009-12-07 17:44       ` Tony Lindgren
2009-12-08 10:40         ` Mike Rapoport
2009-12-09  6:49         ` [PATCH v2] " Mike Rapoport
2009-12-09 13:27         ` [PATCH] omap3: cm-t35: add mux initialization (was: Re: [PATCH] omap3: cm-t35: add mux initialization) Mike Rapoport
2009-12-09 16:36           ` Tony Lindgren
2009-12-11 22:00           ` [APPLIED] [PATCH] omap3: cm-t35: add mux initialization 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=20091207162209.GV24013@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mike@compulab.co.il \
    /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