From: Oliver Neukum <oneukum@suse.com>
To: Li Jun <jun.li@nxp.com>,
robh+dt@kernel.org, heikki.krogerus@linux.intel.com,
gregkh@linuxfoundation.org, linux@roeck-us.net
Cc: gsomlo@gmail.com, linux-imx@nxp.com, peter.chen@nxp.com,
shufan_lee@richtek.com, a.hajda@samsung.com,
cw00.choi@samsung.com, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: [v5,01/14] dt-bindings: connector: add properties for typec
Date: Thu, 03 May 2018 09:27:11 +0200 [thread overview]
Message-ID: <1525332431.12348.1.camel@suse.com> (raw)
Am Donnerstag, den 03.05.2018, 08:24 +0800 schrieb Li Jun:
> +Optional properties for usb-c-connector:
> +- power-role: should be one of "source", "sink" or "dual"(DRP) if typec
> + connector has power support.
> +- try-power-role: preferred power role if "dual"(DRP) can support Try.SNK
> + or Try.SRC, should be "sink" for Try.SNK or "source" for Try.SRC.
> +- data-role: should be one of "host", "device", "dual"(DRD) if typec
> + connector supports USB data.
Hi,
is this really correct?
Can one implement a device that can operate as either DFP or UFP,
but not implements the dynamic role switch that a DRP must support?
Regards
Oliver
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-05-03 7:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 7:27 Oliver Neukum [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-17 13:16 [v5,01/14] dt-bindings: connector: add properties for typec Jun Li
2018-05-16 7:21 Peter Chen
2018-05-14 9:06 Jun Li
2018-05-11 19:49 Mats Karrman
2018-05-10 0:43 Jun Li
2018-05-08 10:03 Oliver Neukum
2018-05-08 5:36 Jun Li
2018-05-07 15:58 Rob Herring
2018-05-04 8:59 Jun Li
2018-05-03 9:17 Oliver Neukum
2018-05-03 8:35 Jun Li
2018-05-03 0:24 Jun Li
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=1525332431.12348.1.camel@suse.com \
--to=oneukum@suse.com \
--cc=a.hajda@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=gsomlo@gmail.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=jun.li@nxp.com \
--cc=linux-imx@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=peter.chen@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shufan_lee@richtek.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).