From: Mark Jackson <mpfj-list@newflow.co.uk>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-usb@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
Felipe Balbi <balbi@ti.com>, Greg KH <gregkh@linuxfoundation.org>,
jkosina@suse.cz, anatol.pomozov@gmail.com,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Bin Liu <binmlist@gmail.com>
Subject: Re: [PATCH] Allow MUSB DSPS to use "force host" mode
Date: Fri, 22 Nov 2013 16:49:57 +0000 [thread overview]
Message-ID: <528F8B35.8070408@newflow.co.uk> (raw)
In-Reply-To: <528F8741.1060406@linutronix.de>
On 22/11/13 16:33, Sebastian Andrzej Siewior wrote:
> On 11/22/2013 04:55 PM, Mark Jackson wrote:
>> The IDDIG input pin is normally used to determine the USB mode
>> (i.e. HOST or DEVICE).
>>
>> On some systems (e.g. AM335x) leaving this pin floating allows
>> the USB mode to be set via software.
>
> So you have a board where musb is used only as host or only as device
> and the ID pin not on ground or 3.3V?
> What are the side effects? I remember correctly Bin wanted to avoid
> settings this if it could be avoided.
Yes ... we have a host only USB port and an unconnected ID pin.
AFAIK it defaults to device mode so I can't see any devices that get
plugged into the USB port.
If I tweak the s/w to "force" host mode on, then everything appears to
work okay.
I guess it's more of a hardware oversight that we left the pin floating
but in the real world, I guess someone may want this feature to they
can change the usb port type ?
Either way, I need to fix the current h/w (which can be done via s/w)
hence the patch.
Mark J.
next prev parent reply other threads:[~2013-11-22 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 15:55 [PATCH] Allow MUSB DSPS to use "force host" mode Mark Jackson
2013-11-22 16:33 ` Sebastian Andrzej Siewior
2013-11-22 16:49 ` Mark Jackson [this message]
2013-11-22 17:01 ` Sebastian Andrzej Siewior
2013-11-22 17:07 ` Mark Jackson
2013-11-22 17:22 ` Sebastian Andrzej Siewior
2013-11-22 16:38 ` Michael Grzeschik
2013-11-22 16:45 ` Mark Jackson
2013-11-25 21:24 ` Felipe Balbi
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=528F8B35.8070408@newflow.co.uk \
--to=mpfj-list@newflow.co.uk \
--cc=anatol.pomozov@gmail.com \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=binmlist@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.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