public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Brian Swetland <swetland@google.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] mux: simplify MUX_CFG_730 and add some usb client pins
Date: Mon, 28 Nov 2005 18:11:57 -0800	[thread overview]
Message-ID: <20051129021156.GF8319@atomide.com> (raw)
In-Reply-To: <20051126051858.GA22303@localhost.localdomain>

* Brian Swetland <swetland@google.com> [051125 21:20]:
> 
> As I continue to try to sort out USB gadget support on the 730, I find
> that I need to add some pin definitions.  
> 
> Since the 730 lacks PU_PD registers, and the pullup bit is always in
> the config register on the 730, I simplified the MUX_CFG_730() macro
> a little bit (to avoid typing a bunch of 0s and NAs on *every* line).
> 
> Does this make sense?

Yes, thanks. Pushing today.

Tony

      reply	other threads:[~2005-11-29  2:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-26  5:18 [PATCH] mux: simplify MUX_CFG_730 and add some usb client pins Brian Swetland
2005-11-29  2:11 ` 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=20051129021156.GF8319@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=swetland@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox