On 06/01/2016 02:04 AM, Oliver Neukum wrote:
On Wed, 2016-06-01 at 11:23 +0300, Heikki Krogerus wrote:
I think we can still add them later if they are still seen as
necessity later on, tough I seriously doubt it. It would not be
ideal, but adding an attribute should not really break anything,
right? Removing would.
However, how do we learn that the other side has triggered a reset?
USB PD specification, section 6.8.2.2 (Modal Operation and Hard Reset):
A Hard Reset shall cause all Active Modes to be exited by both Port Partners
and any Cable Plugs (see Section 6.4.4.3.4).
Section 6.4.4.3.4 (Enter Mode Command):
The following events shall also cause the Port Partners and Cable Plug(s) to exit all Active Modes:
- A PD Hard Reset
- The Port Partners or Cable Plug(s) are Detached
- A Cable Reset (only exits the Cable Plug’s Active Modes)
The class code would not explicitly learn about the reset,
but it would be informed about the exited modes.
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
