From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Vincent Palatin <vpalatin@chromium.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Guenter Roeck <linux@roeck-us.net>,
Oliver Neukum <oneukum@suse.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Bin Gao <bin.gao@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCHv6 1/3] usb: USB Type-C connector class
Date: Fri, 26 Aug 2016 17:07:10 +0300 [thread overview]
Message-ID: <20160826140710.GG12117@kuha.fi.intel.com> (raw)
In-Reply-To: <CANVmJFm9m0u3ACw9HeOKSxC5TbVJt+vyAGhiCk2JH87wrfyHrg@mail.gmail.com>
Hi Vincent,
On Fri, Aug 26, 2016 at 03:16:16PM +0200, Vincent Palatin wrote:
> >> > +What: /sys/class/typec/<port>/current_vconn_role
> >> > +Date: June 2016
> >> > +Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> >> > +Description:
> >> > + Shows the current VCONN role of the port. This attribute can be
> >> > + used to request VCONN role swap on the port when the port
> >> > + supports USB Power Delivery.
> >> > +
> >> > + Valid values are:
> >> > + - source
> >> > + - sink
> >>
> >>
> >> either we are currently sourcing vconn or not, but even if you are
> >> not, you are probably not a vconn sink either (ie only vconn-powered
> >> accessory are, your usual linux-powered laptop/phone is probably not)
> >
> > It's not relevant to know whether the vconn is being actually used or
> > not here. I'm not sure what's your point?
>
>
> My point was: saying we are a VCONN "sink" just because we are not
> currently sourcing vconn is usually not true.
OK, I understand your point now. You are correct. I think we need to
change this attribute and call it "vconn_source" that reports "1" or
"0".
I'll change that and send one more version of these on Monday
(hopefully the last one) unless somebody disagrees.
> >> > +What: /sys/class/typec/<port>-partner/type
> >> > +Date: June 2016
> >> > +Contact: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> >> > +Description:
> >> > + Shows the type of the partner. Can be one of the following:
> >> > + - USB - When the partner is normal USB host/peripheral.
> >> > + - Charger - When the partner has been identified as dedicated
> >> > + charger.
> >> > + - Alternate Mode - When the partner supports Alternate Modes.
> >> > + - Accessory - When the partner is one of the accessories with
> >> > + specific Accessory Mode defined in USB Type-C
> >> > + specification.
> >>
> >>
> >> where a dock would be classified ?
> >
> > A dock is just USB PD capable device with a bunch of alternate modes
> > that is attached to the port. There is no specific identifier for a
> > "dock".
>
> My remark was a bit too stern,
> I meant a dock might be 'USB' 'Charger' 'Alternate Mode' , all at the
> same time or alternately depending what you plug in.
> I don't really see those types as mutually exclusive.
So USB type means the partner does not have alternate modes (I'll
clear that in the documentation), Charger is a dedicated charger and
therefore can not be anything else (no USB, no alternate modes).
To answer your original question, a dock would be reported as
Alternate Mode.
Thanks,
--
heikki
next prev parent reply other threads:[~2016-08-26 14:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 12:05 [PATCHv6 0/3] USB Type-C Connector class Heikki Krogerus
2016-08-22 12:05 ` [PATCHv6 1/3] usb: USB Type-C connector class Heikki Krogerus
2016-08-24 14:08 ` Vincent Palatin
2016-08-25 11:59 ` Heikki Krogerus
2016-08-26 13:16 ` Vincent Palatin
2016-08-26 14:07 ` Heikki Krogerus [this message]
2016-08-29 13:04 ` Guenter Roeck
2016-08-29 13:43 ` Heikki Krogerus
2016-08-29 14:07 ` Heikki Krogerus
2016-08-29 18:50 ` Guenter Roeck
2016-08-30 8:22 ` Heikki Krogerus
2016-08-30 15:28 ` Guenter Roeck
2016-08-30 17:00 ` Guenter Roeck
2016-08-22 12:05 ` [PATCHv6 2/3] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY Heikki Krogerus
2016-08-22 12:06 ` [PATCHv6 3/3] mfd: intel_soc_pmic_bxtwc: add support for USB Type-C PHY on WhiskeyCove Heikki Krogerus
-- strict thread matches above, loose matches on Subject: below --
2016-08-29 12:36 [PATCHv6 0/3] USB Type-C Connector class Heikki Krogerus
2016-08-29 12:36 ` [PATCHv6 1/3] usb: USB Type-C connector class Heikki Krogerus
2016-08-29 13:06 ` Vincent Palatin
2016-08-30 9:32 ` Oliver Neukum
2016-08-30 10:04 ` Heikki Krogerus
2016-08-30 11:16 ` Oliver Neukum
2016-08-30 11:49 ` Heikki Krogerus
2016-08-30 13:11 ` Heikki Krogerus
2016-08-30 13:47 ` Guenter Roeck
2016-08-31 11:09 ` Heikki Krogerus
2016-08-31 13:18 ` Guenter Roeck
2016-08-30 13:46 ` Guenter Roeck
2016-08-30 14:13 ` Heikki Krogerus
2016-08-30 15:40 ` 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=20160826140710.GG12117@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=bin.gao@linux.intel.com \
--cc=felipe.balbi@linux.intel.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 \
--cc=vpalatin@chromium.org \
/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.