mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Rajaram R <rajaram.officemail@gmail.com>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	Oliver Neukum <oneukum@suse.com>
Subject: Re: [PATCHv3 1/2] usb: USB Type-C connector class
Date: Tue, 28 Jun 2016 16:12:41 +0300	[thread overview]
Message-ID: <20160628131241.GB3378@kuha.fi.intel.com> (raw)
In-Reply-To: <57712CA2.1020408@roeck-us.net>

On Mon, Jun 27, 2016 at 06:39:46AM -0700, Guenter Roeck wrote:
> On 06/27/2016 05:13 AM, Heikki Krogerus wrote:
> > Hi,
> > 
> > On Mon, Jun 27, 2016 at 03:51:08PM +0530, Rajaram R wrote:
> > > May be I am missing user or usage of the driver.. I see this driver is
> > > providing limited information of the Type-C connectors or the port
> > > partner
> > 
> > Yes, this interface can't provide directly information received from
> > PD commands like Discover Identity. We will have to present the
> > partners even when USB PD is not supported and in a consistent
> > fashion. Some details will be available in any case indirectly. Like
> > if there are modes, there will be devices presenting them, and the
> > product type in case of partners will be the partner type.
> > 
> > But there are a couple of attributes I have been thinking about adding
> > for the partners:
> > 
> >          supported_data_roles
> >          supports_usb_power_delivery
> > 
> > The supported data roles would respond bits 30 and 31 of the ID Header
> > VDO. But when the partner does not support USB PD, we will have to
> > report "unknown" in it.
> > 
> 
> Or make the attribute invisible in that case.

Well, why not. I did not like the idea of hiding an attribute
previously. I preferred to have an attribute always available, unless
there was a single and clear way to determine the cases where any of
the attributes for example with our partners would be visible or not..
But who cares.

> > Oliver, Guenter! How do you guys feel about those? Is there any use
> > for them?
> > 
> Definitely good for debugging and informational. On the top of my head,
> I don't immediately see what a user would do with it, though, but then
> it would not hurt either to have the information.
> 
> I keep wondering if it would make sense to directly expose the ID header
> VDO, similar to the alternate mode VDOs, in the partner node.

Yes, it makes sense. I'll add an attribute for that.

But since you proposed hiding the attributes, I'll add an attribute
"supports_usb_power_deliver" in any case, and make the vdo attribute
visible only if it returs 1. I'll also make the "accessory" attribute
visible only in case the partner type is accessory.


Thanks Guenter,

-- 
heikki

  reply	other threads:[~2016-06-28 13:13 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
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 [this message]
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=20160628131241.GB3378@kuha.fi.intel.com \
    --to=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 \
    --cc=rajaram.officemail@gmail.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

all inboxes | Powered by JetHome®