From: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
To: "Gupta, Ajay Kumar" <ajay.gupta-l0cyMroinI0@public.gmane.org>
Cc: "felipe.balbi-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org"
<felipe.balbi-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>,
"linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org"
<tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH] musb: refresh nop transceiver support for musb
Date: Mon, 6 Apr 2009 11:30:37 -0700 [thread overview]
Message-ID: <200904061130.38325.david-b@pacbell.net> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E73940427EE8F27-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
On Monday 06 April 2009, Gupta, Ajay Kumar wrote:
> David, what's your comment on this?
It was wrong to try registering the transceiver in
the mach-map2/usb2.c file in any case. That's a
board-specific issue for OMAP3; and TUSB60x0 chips
have an integrated one. See
http://marc.info/?l=linux-usb&m=123852898920405&w=2
So for example the RX51 board support (nyet in mainline)
needs to register the NOP transceiver; and I think one
more board, maybe the OMAP3 EVM, does too.
- Dave
p.s. This issue is *only* for the OMAP tree.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-04-06 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 13:34 [PATCH] musb: refresh nop transceiver support for musb Ajay Kumar Gupta
2009-04-06 13:44 ` Felipe Balbi
2009-04-06 14:08 ` Gupta, Ajay Kumar
2009-04-06 14:16 ` Felipe Balbi
[not found] ` <19F8576C6E063C45BE387C64729E73940427EE8F27-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2009-04-06 18:30 ` David Brownell [this message]
2009-04-07 4:38 ` Gupta, Ajay Kumar
2009-04-06 19:36 ` David Brownell
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=200904061130.38325.david-b@pacbell.net \
--to=david-b-ybekhbn/0ldr7s880joybq@public.gmane.org \
--cc=ajay.gupta-l0cyMroinI0@public.gmane.org \
--cc=felipe.balbi-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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