From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "shufan_lee\(?????????\)" <shufan_lee@richtek.com>
Cc: 'Jun Li' <jun.li@nxp.com>, ShuFanLee <leechu729@gmail.com>,
"cy_huang\(?????????\)" <cy_huang@richtek.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: USB TYPEC: RT1711H Type-C Chip Driver
Date: Fri, 19 Jan 2018 10:22:18 +0200 [thread overview]
Message-ID: <20180119082218.GA22976@kuha.fi.intel.com> (raw)
Hi Shu-Fan,
On Fri, Jan 19, 2018 at 05:48:02AM +0000, shufan_lee(?????????) wrote:
> Hi Jun,
>
> For now, RT1711H is not fully compatible with TCPCI. So the existing tcpci.c
> may not work for it.
The datasheet for RT1711H does talk about TCPCi and TCPM+TCPC [1].
What are the differences that justify a separate driver?
[1] http://www.richtek.com/assets/product_file/RT1711H/DS1711H-02.pdf
Br,
next reply other threads:[~2018-01-19 8:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 8:22 Heikki Krogerus [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-30 23:25 USB TYPEC: RT1711H Type-C Chip Driver Guenter Roeck
2018-01-30 13:21 shufan_lee(李書帆)
2018-01-29 19:57 Guenter Roeck
2018-01-29 7:19 shufan_lee(李書帆)
2018-01-22 18:50 Guenter Roeck
2018-01-22 2:01 shufan_lee(李書帆)
2018-01-19 16:02 Guenter Roeck
2018-01-19 9:24 Heikki Krogerus
2018-01-19 9:01 shufan_lee(李書帆)
2018-01-19 8:03 Greg KH
2018-01-19 5:48 shufan_lee(李書帆)
2018-01-19 3:09 Jun Li
2018-01-18 13:13 shufan_lee(李書帆)
2018-01-17 13:42 Greg KH
2018-01-17 13:33 Greg KH
2018-01-17 13:33 Greg KH
2018-01-17 13:31 Greg Kroah-Hartman
2018-01-17 12:00 Heikki Krogerus
2018-01-17 11:14 Greg Kroah-Hartman
2018-01-17 11:08 Heikki Krogerus
2018-01-17 9:30 shufan_lee(李書帆)
2018-01-10 6:59 ShuFanLee
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=20180119082218.GA22976@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=cy_huang@richtek.com \
--cc=jun.li@nxp.com \
--cc=leechu729@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--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).