Hi,

Peter Chen [off-list ref] writes:

quoted

quoted

quoted

So far, I haven't seen anybody talking about real USB OTG (the spec)
when they say OTG. Usually they just mean "a method for swapping between
host and peripheral roles, but we really don't want all the extra cost
of the OTG specification".

That's what I thought before, but the request from the Marketing guy is
"To prove the SoC is OTG compliance, support HNP and SRP", don't you
see the SoC reference manual say "it supports HNP and SRP"?

If there is no request, who else wants to implement so complicated FSM
but seldom use cases, and go to pass OTG compliance test (tested by PET).

I stand corrected :-)

So there is one user for this layer. And this user has its own role
control registers. I'm not convinced we need this large generic layer
for one user.

You mean chipidea or dwc3? I have more comments below.

chipidea. From the point of OTG (or DRD) dwc3 is very
self-sufficient. HW itself tracks state machine, much like MUSB does.

quoted

quoted

quoted

quoted

For the real use case, some Carplay platforms need it.

Carplay does *NOT* rely on OTG. Apple has its own proprietary and closed
specification which is not OTG-compliant.

Yes, it is not OTG-compliant, but it can co-work with some standard OTG FSM
states to finish role swap.

What are you referring to as "finish role swap"? I don't get that.

Change current role from host to peripheral.

Okay, we have two scenarios here:

1. You need full OTG compliance

	For this, granted, you need the state machine if your HW doesn't
	track it. This is a given. With only one user, however, perhaps
	we don't need a generic layer. There are not enough different
	setups to design a good enough generic layer. We will end up
	with a pseudo-generic framework which is coupled with its only
	user.

2. Dual-role support, without OTG compliance

	In this case, you don't need a stack. All you need is a signal
	to tell you state of ID pin and another to tell you state of
	VBUS level. If you have those, you don't need to walk an OTG
	state machine at all. You don't need any of those quirky OTG
	timers, agreed?

	Given the above, why would you even want to use a subset of OTG
	state machine to implement something that's _usually_ as simple
	as:

8<----------------------------------------------------------------------
	vbus = read(VBUS_STATE); /* could be a gpio_get_value() */
        id = read(ID_STATE); /* could be a gpio_get_value() */

        set_role(id);
        set_vbus(vbus);
------------------------------------------------------------------------

quoted

quoted

Notice, it needs to swap role without disconnect cable.

right, I can swap role without changing cable, but that's not OTG. The
mechanism for that, AFAICT, is not HNP. I don't know details about
CarPlay because the spec isn't public, but my understanding is that
CarPlay doesn't rely on anything from OTG spec.

Since it is non-public, I can't say much. Some flows of its role-swap
refers to On-The-Go and Embedded Host Supplement to the USB Revision 2.0
Specification. 

But OTG FSM is not the only way, the platform which can do role-swap
without disconnection can support it too.

Right, all you need for CarPlay is what I wrote above. You don't need
full OTG compliance for that, right?

quoted

quoted

quoted

quoted

quoted

quoted

diff --git a/include/linux/usb/gadget.h b/include/linux/usb/gadget.h
index f4fc0aa..1d74fb8 100644
--- a/include/linux/usb/gadget.h
+++ b/include/linux/usb/gadget.h

@@ -328,6 +328,7 @@ struct usb_gadget_ops {
  * @in_epnum: last used in ep number
  * @mA: last set mA value
  * @otg_caps: OTG capabilities of this gadget.
+ * @otg_dev: OTG controller device, if needs to be used with OTG core.

do you really know of any platform which has a separate OTG controller?

It may not be a real separate OTG controller. It can be a hardware part
(external connector, external IC, SoC OTG register area, etc) to handle vbus
,id and other signals which are used for role swap.

That's already solved. EXTCON solved that years back and OMAP has been
using EXTCON to program its UTMI mailbox.

No, that's not the same thing, it does not include the swap role.

Read your original comment:

"handle vbus, id and other signals which are *used for* role swap"

You didn't include role swap in your original comment. Semantics aside...

quoted

Consider the use case the host driver is at host/ and udc driver is
at gadget/udc, how to finish to role swap?

... why does the source code placement matter? And what do you mean by
"finish role swap"?

Well, it depends on your driver design, do you want the host driver's
API is still be called when current role is peripheral? One typical
problem you can refer below:

That's a driver bug and those needs to be fixed. This has nothing to do
with an OTG FSM, or lack thereof.

Here's what I plan on doing for dwc3 (as soon as I get some time):

request_threaded_irq(dwc->otg_irq, ...);

irqreturn_t dwc3_otg_irq_thread(int irq, void *_dwc)
{
	struct dwc3 *dwc = _dwc;
        u32 reg;

        reg = readl(OSTS);
        if (reg & PERIPHERAL)
        	dwc3_gadget_init(dwc);

	if (reg & HOST)
        	dwc3_host_init(dwc);

	if (reg & SESSION_END)
        	dwc3_disable_host_and_peripheral(dwc);

	return IRQ_HANDLED;
}

Then, when building the driver with OTG support, we never start Host or
peripheral by default. Only the OTG IRQ handler, since that becomes the
entry point.

That's all we need for DRD support on DWC3. As for OTG, it won't be much
different because the HW tracks OTG state machine. The only difference
will be implemeting HNP (just another big in IRQ handler) and SRP
(already implemented as gadget_wakeup())

commit 11c011a5e777c83819078a18672543f04482b3ec
Author: Srinivas Kandagatla [off-list ref]
Date:   Thu May 19 11:12:56 2016 +0100

    usb: echi-hcd: Add ehci_setup check before echi_shutdown
        


In some cases, the USB code (gadget/hcd->start/stop) needs to be called
during the role swap. For example, if you have mux driver, you may
need to call usb_remove_hcd when ID from 0 to 1. Without Roger's framework,
how can we do that?

You don't really need to remove the gadget. Just mask its interrupts and
ignore any calls to any gadget_driver ops, right? Likewise for
XHCI. Just clear RUN/STOP and no events will ever reach XHCI. But, from
the point of view of dwc3, it's simpler to unregister the platform
device we create for xhci-plat.c. I need no changes in XHCI to do that
and driver model will make sure to call xhci-plat's ->remove() which
will handle everything for me correctly.

-- 
balbi