mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: Badhri Jagan Sridharan <badhri@google.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Guenter Roeck <linux@roeck-us.net>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: typec: Defer checking of valid power role swap to low level drivers
Date: Wed, 17 May 2017 09:34:32 +0200	[thread overview]
Message-ID: <1495006472.30577.6.camel@suse.com> (raw)
In-Reply-To: <20170517073219.8315-1-Badhri@google.com>

Am Mittwoch, den 17.05.2017, 00:32 -0700 schrieb Badhri Jagan
Sridharan:

Hi,

> "Two independent set of mechanisms are defined to allow a USB Type-C
> DRP to functionally swap power and data roles. When USB PD is
> supported, power and data role swapping is performed as a subsequent
> step following the initial connection process. For non-PD implementations,
> power/data role swapping can optionally be dealt with as part of the initial
> connection process."

Well, as I read it, without PD once a connection is established, you
are stuck with your role. So it seems to me that blocking a later
attempt to change it makes sense.

	Regards
		Oliver

  reply	other threads:[~2017-05-17  7:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17  7:32 Badhri Jagan Sridharan
2017-05-17  7:34 ` Oliver Neukum [this message]
2017-05-17  9:36   ` Guenter Roeck
2017-05-17 12:38     ` Heikki Krogerus
2017-05-17 13:02       ` Guenter Roeck
2017-05-17 13:51         ` Heikki Krogerus
2017-05-17 18:05           ` Badhri Jagan Sridharan
2017-05-18  9:13     ` Oliver Neukum
2017-05-18 16:51       ` Guenter Roeck
2017-05-18 21:08         ` Badhri Jagan Sridharan
2017-05-18 21:13           ` Badhri Jagan Sridharan
2017-05-19 10:35           ` Heikki Krogerus
2017-05-19 13:27             ` Guenter Roeck
2017-05-19 10:40           ` Oliver Neukum
2017-05-17  8:08 ` Greg Kroah-Hartman
2017-05-17  9:43   ` 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=1495006472.30577.6.camel@suse.com \
    --to=oneukum@suse.com \
    --cc=badhri@google.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
Powered by JetHome