From: Roger Quadros <rogerq@ti.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Oliver Neukum <oneukum@suse.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: Thu, 23 Jun 2016 15:25:46 +0300 [thread overview]
Message-ID: <576BD54A.8050800@ti.com> (raw)
In-Reply-To: <20160623120055.GC27263@kuha.fi.intel.com>
Hi,
On 23/06/16 15:00, Heikki Krogerus wrote:
> Hi Oliver,
>
> On Thu, Jun 23, 2016 at 10:38:58AM +0200, Oliver Neukum wrote:
>> On Thu, 2016-06-23 at 11:23 +0300, Heikki Krogerus wrote:
>>> On Wed, Jun 22, 2016 at 06:44:18PM +0200, Oliver Neukum wrote:
>>
>>> No it's not. DRP means a port that can operate as _either_ Source
>>> (host) or Sink (device), but not at the same time..
>>
>> Yes, but it is unclear what you will be after a connection
>> and that's the point.
>
> Which is a fact that we can do nothing about. The role after
> connection with DRP ports will be dictated by the partner or selected
> randomly in case the partner is also DRP. We can prefer a role, but
> that in the end guarantees nothing. So if the role that we end up with
> after connection (seen in current_data_role) does not satisfy us, all
> we can do is try to swap it.
>
> I'm not sure what is your point here.
What if the application wants to know exactly what role the device is
operating in at the current moment?
We need to have 2 distinct parameters.
1) supported_modes : host, device, host or device
2) current_mode: host, device, disconnected
--
cheers,
-roger
next prev parent reply other threads:[~2016-06-23 12:26 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
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 [this message]
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=576BD54A.8050800@ti.com \
--to=rogerq@ti.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 \
--cc=oneukum@suse.com \
/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
Powered by JetHome