From: Stephen Boyd <stephen.boyd@linaro.org>
To: Peter Chen <hzpeterchen@gmail.com>
Cc: devicetree@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Chanwoo Choi <cw00.choi@samsung.com>,
robh+dt@kernel.org, MyungJoo Ham <myungjoo.ham@samsung.com>,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC/PATCH] usb: misc: Add a driver for TC7USB40MU
Date: Tue, 13 Sep 2016 22:58:26 -0700 [thread overview]
Message-ID: <147383270635.1464.10706917860873291816@sboyd-linaro> (raw)
In-Reply-To: <20160914033200.GE30760@b29397-desktop>
Quoting Peter Chen (2016-09-13 20:32:00)
> On Tue, Sep 13, 2016 at 06:42:46PM -0700, Stephen Boyd wrote:
> > On the db410c 96boards platform we have a TC7USB40MU[1] on the
> > board to mux the D+/D- lines from the SoC between a micro usb
> > "device" port and a USB hub for "host" roles. Upon a role switch,
> > we need to change this mux to forward the D+/D- lines to either
> > the port or the hub. Therefore, introduce a driver for this
> > device that intercepts extcon USB_HOST events and logically
> > asserts a gpio to mux the "host" D+/D- lines when a host cable is
> > attached. When the cable goes away, it will logically deassert
> > the gpio and mux the "device" lines.
>
> Would you please draw the design? It can also help me review your
> chipidea patch well.
>
> 1. How many ports on the board?
> 2. How the lines are connected on the board?
>
The schematic for the db410c is publically available here[2][3].
There's also the 96boards spec[4] which talks about this switch based
design a little bit. See the section titled "Single USB port Example".
[2] https://github.com/96boards/documentation/blob/master/ConsumerEdition/DragonBoard-410c/HardwareDocs/Schematics_DragonBoard.pdf
[3] https://github.com/96boards/documentation/raw/master/ConsumerEdition/DragonBoard-410c/HardwareDocs/Schematics_DragonBoard.pdf
[4] https://www.96boards.org/wp-content/uploads/2015/02/96BoardsCESpecificationv1.0-EA1.pdf
WARNING: multiple messages have this Message-ID (diff)
From: stephen.boyd@linaro.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC/PATCH] usb: misc: Add a driver for TC7USB40MU
Date: Tue, 13 Sep 2016 22:58:26 -0700 [thread overview]
Message-ID: <147383270635.1464.10706917860873291816@sboyd-linaro> (raw)
In-Reply-To: <20160914033200.GE30760@b29397-desktop>
Quoting Peter Chen (2016-09-13 20:32:00)
> On Tue, Sep 13, 2016 at 06:42:46PM -0700, Stephen Boyd wrote:
> > On the db410c 96boards platform we have a TC7USB40MU[1] on the
> > board to mux the D+/D- lines from the SoC between a micro usb
> > "device" port and a USB hub for "host" roles. Upon a role switch,
> > we need to change this mux to forward the D+/D- lines to either
> > the port or the hub. Therefore, introduce a driver for this
> > device that intercepts extcon USB_HOST events and logically
> > asserts a gpio to mux the "host" D+/D- lines when a host cable is
> > attached. When the cable goes away, it will logically deassert
> > the gpio and mux the "device" lines.
>
> Would you please draw the design? It can also help me review your
> chipidea patch well.
>
> 1. How many ports on the board?
> 2. How the lines are connected on the board?
>
The schematic for the db410c is publically available here[2][3].
There's also the 96boards spec[4] which talks about this switch based
design a little bit. See the section titled "Single USB port Example".
[2] https://github.com/96boards/documentation/blob/master/ConsumerEdition/DragonBoard-410c/HardwareDocs/Schematics_DragonBoard.pdf
[3] https://github.com/96boards/documentation/raw/master/ConsumerEdition/DragonBoard-410c/HardwareDocs/Schematics_DragonBoard.pdf
[4] https://www.96boards.org/wp-content/uploads/2015/02/96BoardsCESpecificationv1.0-EA1.pdf
next prev parent reply other threads:[~2016-09-14 5:58 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 1:42 [RFC/PATCH] usb: misc: Add a driver for TC7USB40MU Stephen Boyd
2016-09-14 1:42 ` Stephen Boyd
2016-09-14 3:32 ` Peter Chen
2016-09-14 3:32 ` Peter Chen
2016-09-14 5:58 ` Stephen Boyd [this message]
2016-09-14 5:58 ` Stephen Boyd
2016-09-14 8:03 ` Peter Chen
2016-09-14 8:03 ` Peter Chen
2016-09-14 8:45 ` Stephen Boyd
2016-09-14 8:45 ` Stephen Boyd
2016-09-15 9:01 ` Peter Chen
2016-09-15 9:01 ` Peter Chen
2016-09-16 1:16 ` Stephen Boyd
2016-09-16 1:16 ` Stephen Boyd
2016-09-17 0:20 ` Peter Chen
2016-09-17 0:20 ` Peter Chen
2016-09-14 8:55 ` Stephen Boyd
2016-09-14 8:55 ` Stephen Boyd
2016-09-17 1:16 ` Peter Chen
2016-09-17 1:16 ` Peter Chen
2016-09-22 18:51 ` Stephen Boyd
2016-09-22 18:51 ` Stephen Boyd
2016-09-26 3:29 ` Peter Chen
2016-09-26 3:29 ` Peter Chen
2016-09-26 18:44 ` Stephen Boyd
2016-09-26 18:44 ` Stephen Boyd
2016-09-27 4:53 ` Peter Chen
2016-09-27 4:53 ` Peter Chen
2016-09-27 4:53 ` Peter Chen
2016-09-27 21:25 ` Stephen Boyd
2016-09-27 21:25 ` Stephen Boyd
2016-09-23 14:35 ` Rob Herring
2016-09-23 14:35 ` Rob Herring
2016-09-26 18:59 ` Stephen Boyd
2016-09-26 18:59 ` Stephen Boyd
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=147383270635.1464.10706917860873291816@sboyd-linaro \
--to=stephen.boyd@linaro.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hzpeterchen@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.