From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Peter Chen <Peter.Chen@freescale.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Cc: "linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: hcd: add OTG ID signal sensing
Date: Wed, 17 Dec 2014 14:35:30 +0300 [thread overview]
Message-ID: <54916A82.4010105@cogentembedded.com> (raw)
In-Reply-To: <BN3PR0301MB08495DD76B65E14BDE460E42816D0@BN3PR0301MB0849.namprd03.prod.outlook.com>
Hello.
On 12/17/2014 5:08 AM, Peter Chen wrote:
>> On the Renesas R8A7791 SoC based boards there's MAX3355 USB OTG chip and
>> mini-AB USB connector corresponding to USB port 0 driven either by EHCI/OHCI
>> or Renesas USBHS gadget controller. And we'd like the host/gadget drivers to
>> work based on the cable type connected. An 'extcon' driver for MAX3355 has
>> been written, so we only need to bind to it via device tree which I'm doing in
>> this patch.
>> I wasn't able to find a solution better than checking the cable type at the host
>> driver probe time and refusing to drive a host if B-cable is connected.
> You may need a dual-role/otg driver to do it, which can enable host/device function
> according to ID pin.
It would have been too good if I had a dual-role controller. :-)
But I have what I have. IIUC, such configuration (OHCI and UDC sharing a
USB port) has been used on OMAP1.
WBR, Sergei
prev parent reply other threads:[~2014-12-17 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 23:16 [PATCH] usb: hcd: add OTG ID signal sensing Sergei Shtylyov
2014-12-17 2:08 ` Peter Chen
2014-12-17 11:35 ` Sergei Shtylyov [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=54916A82.4010105@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=Peter.Chen@freescale.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@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