From: Oliver Neukum <oneukum@suse.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Felipe Balbi <felipe.balbi@linux.intel.com>,
Greg KH <gregkh@linuxfoundation.org>,
Guenter Roeck <linux@roeck-us.net>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCHv3 1/2] usb: USB Type-C connector class
Date: Wed, 22 Jun 2016 18:44:18 +0200 [thread overview]
Message-ID: <1466613858.1976.5.camel@suse.com> (raw)
In-Reply-To: <20160622143803.GG19856@kuha.fi.intel.com>
On Wed, 2016-06-22 at 17:38 +0300, Heikki Krogerus wrote:
> On Wed, Jun 22, 2016 at 03:47:03PM +0200, Oliver Neukum wrote:
> > On Wed, 2016-06-22 at 14:44 +0300, Heikki Krogerus wrote:
> > > If our port is DRD (which would be DRP in the port controller spec),
> > > the supported_power_roles will list:
> > >
> > > device, host
> > >
> > > And the power role, if the port is Source only, the
> > > supported_power_roles will list:
> > >
> > > source
> > >
> > > If the port is Sink only, the supported_power_roles will list:
> > >
> > > sink
> > >
> > > If our port is DRP, the supported_power_roles will list:
> > >
> > > source, sink
> > >
> > > What is there that is missing? We are able to express all the types of
> > > "Roles Supported" that the DEVICE_CAPABILITIES define, no?
> >
> > No, because these are distinct in time. Some ports are DRP so they
> > support
> >
> > device, host
> >
> > at the same time. Some ports can be switched between DFP and UFP
> > they then either support host or device. But you lose the information
> > that the ports can be switched.
>
> You can't ever be host and device at the same time. Just like you
> can't ever be source and sink at the same time.
True, but you can be able to become host and device at the same time.
That is the purpose of a DRP port.
And you can be able to become a host and be able to become a device.
But not at the same time. These ports are switchable.
The current API cannot express the difference.
> Are we now talking about how should a port be advertised to the
> partners? So basically, do you want to be able to program the port to
> be DFP only, UFP only or DRP from user space?
That would be cool, but according to the spec this is an unalterable
attribute. Please look at section 4.4.8.1
It clearly describes different types of ports. We cannot express
the differences between the types described there with the current API.
Regards
Oliver
next prev parent reply other threads:[~2016-06-22 17:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 14:51 [PATCHv3 0/2] USB Type-C Connector class Heikki Krogerus
2016-06-21 14:51 ` [PATCHv3 1/2] usb: USB Type-C connector class Heikki Krogerus
2016-06-21 20:25 ` Oliver Neukum
2016-06-22 9:50 ` Heikki Krogerus
2016-06-22 10:03 ` Heikki Krogerus
2016-06-22 10:21 ` Oliver Neukum
2016-06-22 10:14 ` Oliver Neukum
2016-06-22 11:44 ` Heikki Krogerus
2016-06-22 13:47 ` Oliver Neukum
2016-06-22 14:38 ` Heikki Krogerus
2016-06-22 16:44 ` Oliver Neukum [this message]
2016-06-23 8:23 ` Heikki Krogerus
2016-06-23 8:38 ` Oliver Neukum
2016-06-23 12:00 ` Heikki Krogerus
2016-06-23 12:25 ` Roger Quadros
2016-06-23 13:11 ` Heikki Krogerus
2016-06-23 13:29 ` Guenter Roeck
2016-06-22 21:54 ` Guenter Roeck
2016-06-23 8:25 ` Heikki Krogerus
2016-06-23 11:53 ` Roger Quadros
2016-06-23 13:08 ` Heikki Krogerus
[not found] ` <CAOiXhaKhPfY0Bz8TsZMFQsgLHZZ01DwZ=TPcXtH2nYvHx3PqVA@mail.gmail.com>
[not found] ` <20160627095120.GC20801@kuha.fi.intel.com>
[not found] ` <CAOiXhaJiche=jGbg_C2Jbmw1BnA5UYVNKOfhmy4CFiugoPV_+w@mail.gmail.com>
2016-06-27 12:13 ` Heikki Krogerus
2016-06-27 13:39 ` Guenter Roeck
2016-06-28 13:12 ` Heikki Krogerus
2016-06-28 13:28 ` Guenter Roeck
2016-06-29 8:51 ` Rajaram R
2016-06-29 10:30 ` Heikki Krogerus
2016-06-29 10:51 ` Rajaram R
2016-06-29 11:27 ` Heikki Krogerus
2016-07-04 8:55 ` Oliver Neukum
2016-06-21 14:51 ` [PATCHv3 2/2] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY Heikki Krogerus
2016-06-21 22:25 ` [PATCHv3 0/2] USB Type-C Connector class Guenter Roeck
2016-06-22 9:51 ` Heikki Krogerus
2016-06-22 13:24 ` Guenter Roeck
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=1466613858.1976.5.camel@suse.com \
--to=oneukum@suse.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
/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;
as well as URLs for NNTP newsgroup(s).