From: Guenter Roeck <linux@roeck-us.net>
To: Mats Karrman <mats.dev.list@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: Felipe Balbi <felipe.balbi@linux.intel.com>,
Oliver Neukum <oneukum@suse.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v17 2/3] usb: USB Type-C connector class
Date: Fri, 3 Mar 2017 06:41:40 -0800 [thread overview]
Message-ID: <56a9ca99-b43c-3a6c-dc66-ed4887e5a5cd@roeck-us.net> (raw)
In-Reply-To: <07618170-d561-e7fe-08e0-91316c53d832@gmail.com>
On 03/02/2017 11:29 PM, Mats Karrman wrote:
> On 2017-03-03 04:13, Guenter Roeck wrote:
>
>> On 03/02/2017 07:22 AM, Mats Karrman wrote:
>>> ....
>>> Looking forward, one thing I have run into is how to connect the typec driver with a
>>> driver for an alternate mode. E.g. the DisplayPort Alternate Mode specification
>>> includes the HPD (hot plug) and HPD-INT (hot plug interrupt) signals as bits in the
>>> Attention message. These signals are needed by the DisplayPort driver to know when to
>>> start negotiation etc.
>>> Have you got any thoughts on how to standardize such interfaces?
>> That really depends on the lower level driver. For Chromebooks, where the Type-C
>> Protocol Manager runs on the EC, we have an extcon driver which reports the pin states
>> to the graphics drivers and connects to the Type-C class code using the Type-C class
>> API. I still need to update, re-test, and publish that code. The published code in
>> https://chromium.googlesource.com/chromiumos/third_party/kernel/, branch chromeos-4.4,
>> shows how it can be done, though that code currently still uses the Android Type-C
>> infrastructure.
>
> OK, thanks!
>
> My system is a bit different. It's an i.MX6 SoC with the typec phy and DP controller connected
>
> directly to the SoC and it's using DTB/OF.
>
Sounds quite similar to rk3399 (Samsung Chromebook Plus). I have not ported the Type-C class code
to that system yet, but it does use the extcon cros_ec driver, and DP connectivity is signaled
to the DP code through extcon events.
> Using extcon I would have a driver that is both typec class and extcon driver at the same time
>
> since I can't share the access to the typec phy. Is this done elsewhere in the kernel?
>
See above. The code is available in the repository mentioned above.
Guenter
> I don't know much about the wcove PMIC and what alternate modes it might support but I
>
> guess that driver would end up in the same place.
>
> Do we need to further standardize attributes under (each) specific alternate mode to
>
> include things such as HPD for the DP mode?
>
> BR // Mats
>
>
next prev parent reply other threads:[~2017-03-03 14:43 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 14:24 [PATCH v17 0/3] USB Type-C Connector class Heikki Krogerus
2017-02-21 14:24 ` [PATCH v17 1/3] lib/string: add sysfs_match_string helper Heikki Krogerus
2017-02-21 14:24 ` [PATCH v17 2/3] usb: USB Type-C connector class Heikki Krogerus
2017-03-02 15:22 ` Mats Karrman
2017-03-03 3:13 ` Guenter Roeck
2017-03-03 7:29 ` Mats Karrman
2017-03-03 9:48 ` Enric Balletbo Serra
2017-03-03 12:59 ` Heikki Krogerus
2017-03-03 14:49 ` Guenter Roeck
2017-03-03 19:27 ` Mats Karrman
2017-03-06 9:37 ` Oliver Neukum
2017-03-06 13:14 ` Heikki Krogerus
2017-03-07 22:30 ` Mats Karrman
2017-03-08 1:38 ` Guenter Roeck
2017-04-08 23:09 ` USB Type-C Port Manager API concern Mats Karrman
2017-04-09 15:16 ` Guenter Roeck
2017-04-09 21:05 ` Mats Karrman
2017-04-14 2:57 ` Guenter Roeck
2017-04-14 8:30 ` Mats Karrman
2017-03-08 13:58 ` [PATCH v17 2/3] usb: USB Type-C connector class Heikki Krogerus
2017-03-10 22:22 ` Mats Karrman
2017-03-10 23:41 ` Guenter Roeck
2017-04-18 18:52 ` Badhri Jagan Sridharan
2017-04-19 11:23 ` Heikki Krogerus
2017-04-19 14:45 ` Badhri Jagan Sridharan
2017-04-19 15:14 ` Guenter Roeck
2017-04-19 17:22 ` Badhri Jagan Sridharan
2017-04-19 19:29 ` Guenter Roeck
2017-04-20 12:24 ` Heikki Krogerus
2017-04-20 19:46 ` Badhri Jagan Sridharan
2017-04-21 12:12 ` Heikki Krogerus
2017-04-21 13:14 ` Guenter Roeck
2017-04-21 14:27 ` Rajaram R
2017-04-21 16:43 ` Guenter Roeck
2017-04-22 9:23 ` Rajaram R
2017-04-24 17:50 ` Badhri Jagan Sridharan
2017-04-25 8:26 ` Rajaram R
2017-04-25 14:10 ` Guenter Roeck
2017-04-27 6:20 ` Rajaram R
2017-04-27 18:10 ` Guenter Roeck
2017-04-28 10:52 ` Heikki Krogerus
2017-04-20 11:55 ` Heikki Krogerus
2017-03-03 14:41 ` Guenter Roeck [this message]
2017-03-03 3:35 ` Peter Chen
2017-03-03 4:29 ` Guenter Roeck
2017-03-03 4:52 ` Peter Chen
2017-03-03 14:36 ` Guenter Roeck
2017-03-06 1:24 ` Peter Chen
2017-03-03 14:31 ` Heikki Krogerus
2017-03-06 1:15 ` Peter Chen
2017-03-06 13:16 ` Heikki Krogerus
2017-03-07 1:36 ` Peter Chen
2017-03-07 8:57 ` Heikki Krogerus
2017-03-08 1:53 ` Guenter Roeck
2017-03-08 6:50 ` Peter Chen
2017-03-08 14:44 ` Guenter Roeck
2017-03-09 2:00 ` Peter Chen
2017-02-21 14:24 ` [PATCH v17 3/3] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY Heikki Krogerus
2017-02-21 15:42 ` [PATCH v17 0/3] USB Type-C Connector class Felipe Balbi
2017-03-21 11:14 ` Heikki Krogerus
2017-03-21 10:23 ` Greg KH
2017-03-21 10:37 ` Heikki Krogerus
2017-03-22 21:15 ` Mats Karrman
2017-03-23 8:16 ` Heikki Krogerus
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=56a9ca99-b43c-3a6c-dc66-ed4887e5a5cd@roeck-us.net \
--to=linux@roeck-us.net \
--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=mats.dev.list@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).