From: Felipe Balbi <felipe.balbi@nokia.com>
To: ext Grazvydas Ignotas <notasas@gmail.com>
Cc: David Brownell <david-b@pacbell.net>,
Steve Sakoman <sakoman@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Maulik Mankad <x0082077@ti.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH] ARM: OMAP: Fix board data to support device only, host only and OTG roles.
Date: Mon, 31 May 2010 12:56:37 +0300 [thread overview]
Message-ID: <20100531095637.GF16504@nokia.com> (raw)
In-Reply-To: <AANLkTin-Ud-BdQ3lcydqZx7Tb1YoBq05XCONeYqxWhZm@mail.gmail.com>
On Mon, May 31, 2010 at 11:44:05AM +0200, ext Grazvydas Ignotas wrote:
>If a board is configured as host and driver is set to only support
>peripheral it is perfectly fine for the driver not to allow that. But
>why is the driver refusing OTG board setting if it's compiled to only
>support host/peripheral? If I apply [1], it works perfectly fine for
>me. What's wrong with degrading OTG to host/peripheral, did you really
>mean to NAK [1], David? Why can't I compile musb in a
>periperal/host-only mode if I have OTG connector?
otg depends on usb suspend, which depends on runtime pm (I guess),
without suspend, host negotiation protocol will never work which is
required on OTG.
I believe that was Dave's reasoning.
--
balbi
DefectiveByDesign.org
next prev parent reply other threads:[~2010-05-31 9:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 13:09 [PATCH] ARM: OMAP: Fix board data to support device only, host only and OTG roles Maulik Mankad
2010-05-20 14:00 ` Gupta, Ajay Kumar
2010-05-20 15:15 ` David Brownell
[not found] ` <304844.15257.qm-4JhmkcZgSkkHBU+L9ui1Svu2YVrzzGjVVpNB7YpNyf8@public.gmane.org>
2010-05-20 15:16 ` Felipe Balbi
2010-05-20 15:40 ` David Brownell
[not found] ` <1274360966-9974-1-git-send-email-x0082077-l0cyMroinI0@public.gmane.org>
2010-05-20 15:48 ` David Brownell
2010-05-21 5:15 ` Gupta, Ajay Kumar
2010-05-21 6:52 ` Felipe Balbi
[not found] ` <20100521065218.GG925-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2010-05-21 7:43 ` Gupta, Ajay Kumar
[not found] ` <19F8576C6E063C45BE387C64729E7394044E535F3E-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2010-05-21 8:48 ` Felipe Balbi
2010-05-23 16:21 ` David Brownell
2010-05-23 16:33 ` David Brownell
[not found] ` <420791.3389.qm-g47maUHHHF8HBU+L9ui1Svu2YVrzzGjVVpNB7YpNyf8@public.gmane.org>
2010-05-28 15:36 ` Gadiyar, Anand
2010-05-28 15:48 ` Ming Lei
2010-05-28 15:55 ` Ming Lei
2010-05-28 18:27 ` Steve Sakoman
2010-05-28 18:32 ` David Brownell
[not found] ` <987022.25256.qm-g47maUHHHF/6X00i2u5GFvu2YVrzzGjVVpNB7YpNyf8@public.gmane.org>
2010-05-31 9:44 ` Grazvydas Ignotas
2010-05-31 9:56 ` Felipe Balbi [this message]
[not found] ` <AANLkTin-Ud-BdQ3lcydqZx7Tb1YoBq05XCONeYqxWhZm-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-31 12:53 ` 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=20100531095637.GF16504@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=notasas@gmail.com \
--cc=sakoman@gmail.com \
--cc=tony@atomide.com \
--cc=x0082077@ti.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;
as well as URLs for NNTP newsgroup(s).