From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Badhri Jagan Sridharan <badhri@google.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Oliver Neukum <oneukum@suse.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
USB <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] usb: typec: Defer checking of valid power role swap to low level drivers
Date: Fri, 19 May 2017 13:35:51 +0300 [thread overview]
Message-ID: <20170519103551.GD14626@kuha.fi.intel.com> (raw)
In-Reply-To: <CAPTae5JS+cNFEkzjT6uQPCiNpc56NUTFAQQovWnQFN9H3RhwUA@mail.gmail.com>
On Thu, May 18, 2017 at 02:08:53PM -0700, Badhri Jagan Sridharan wrote:
> On Thu, May 18, 2017 at 9:51 AM, Guenter Roeck <linux@roeck-us.net> wrote:
> > On Thu, May 18, 2017 at 11:13:51AM +0200, Oliver Neukum wrote:
> >> Am Mittwoch, den 17.05.2017, 02:36 -0700 schrieb Guenter Roeck:
> >> > On 05/17/2017 12:34 AM, Oliver Neukum wrote:
> >> > >
> >> > > 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.
> >> > >
> >> >
> >> > That seems to be a harsh and not very user friendly reading of the specification.
> >> >
> >> > I would argue that the user doesn't care if the partner supports PD or not
> >> > when selecting a role, and I would prefer to provide an implementation which is
> >> > as user friendly as possible.
> >>
> >> Data role, no question, you are right.
> >> Power role is a different question. A switch of power role with PD should
> >> not lead to a disconnect. Any other method might. So equating them does
> >> not look like a good idea.
> >>
> >
> > Not really sure I can follow. If a partner does not support PD, there is no
> > real distinction between data role and power role, or am I missing something ?
> >
> > Are you saying that, if a partner does not support PD, user space should
> > request a data role swap instead, and that this would be acceptable for you ?
> >
> > I don't really understand the difference - a data role swap doesn't cause
> > a disconnect either if the partner supports PD, and it would still result
> > in a disconnect/reconnect sequence if the partner does not support PD -
> > but if it works for you, fine with me.
> >
> > Badhri, would that work for us ?
>
> Yes Geunter that should work as well. Requesting non-pd role swap either through
> current_power_role or current_data_role is virtually the same.
So if I understood this correctly, we'll skip this change, right?
Thanks,
--
heikki
next prev parent reply other threads:[~2017-05-19 10:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 7:32 [PATCH] usb: typec: Defer checking of valid power role swap to low level drivers Badhri Jagan Sridharan
2017-05-17 7:34 ` Oliver Neukum
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 [this message]
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=20170519103551.GD14626@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=badhri@google.com \
--cc=gregkh@linuxfoundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.