From: Guenter Roeck <linux@roeck-us.net>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Vincent Palatin <vpalatin@chromium.org>,
Greg KH <gregkh@linuxfoundation.org>,
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: Tue, 30 Aug 2016 08:28:46 -0700 [thread overview]
Message-ID: <20160830152846.GA26785@roeck-us.net> (raw)
In-Reply-To: <20160830082227.GB10151@kuha.fi.intel.com>
Hello Heikki,
On Tue, Aug 30, 2016 at 11:22:27AM +0300, Heikki Krogerus wrote:
> >
> > If you are only interested in accessory mode support, maybe we don't need
> > the 'type' attribute at all. We could make the 'accessory' attribute always
> > visible and display one of "none", "Audio", "Debug", or "Digital Audio".
> > It might also make sense to rename the attribute to "accessory_mode".
>
> That works for me.
>
> How about if I add the "supports_usb_power_delivery" attribute for the
> partners instead to give some details about them. Any objections?
>
At first glance, the attribute name looks a bit awkward. Let me look
into the specification to see what might make sense to report. On top of my
head, I don't recall if we are able to report this for a dock which isn't
currently connected to power.
> > On a side note, while looking into this, I noticed the following:
> >
> > + if (port->cap->accessory)
> > + for (accessory = port->cap->accessory, i = 0;
> > + i < port->cap->num_accessory; accessory++, i++)
> > + ret += sprintf(buf, "%s\n",
> > + typec_accessory_modes[*accessory]);
> >
> > This means the list of supported accessories always starts with ", ".
>
> Where does it print ", "?
>
> I'm not sure what is wrong here, but I'll update this code in any
Nothing. Looks like I lost my ability to read code. Somehow the ',' above made
it into the string. There is some inconsistency in the output when compared to
the other "supported" attributes, though. Here the supported modes are printed
in consecutive lines; elsewhere they are printed in a single line with ',' as
separator.
Thanks,
Guenter
next prev parent reply other threads:[~2016-08-30 15:29 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
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 [this message]
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
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=20160830152846.GA26785@roeck-us.net \
--to=linux@roeck-us.net \
--cc=bin.gao@linux.intel.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome