[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <25ced79e8ea84908bf6110a613ed81a2@ex1.rt.l>
Date: Fri, 19 Jan 2018 09:01:24 +0000
From: shufan_lee(李書帆) <shufan_lee@...htek.com>
To: 'Heikki Krogerus' <heikki.krogerus@...ux.intel.com>
CC: 'Jun Li' <jun.li@....com>, ShuFanLee <leechu729@...il.com>,
cy_huang(黃啟原) <cy_huang@...htek.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
Guenter Roeck <linux@...ck-us.net>
Subject: RE: [PATCH] USB TYPEC: RT1711H Type-C Chip Driver
Hi Heikki,
For example, the flow of tcpci_init is a little bit different.
In tcpci_init, there are more parameters need to be set for RT1711H.
Best Regards,
*****************************
Shu-Fan Lee
Richtek Technology Corporation
TEL: +886-3-5526789 #2359
FAX: +886-3-5526612
*****************************
-----Original Message-----
From: Heikki Krogerus [mailto:heikki.krogerus@...ux.intel.com]
Sent: Friday, January 19, 2018 4:22 PM
To: shufan_lee(李書帆)
Cc: 'Jun Li'; ShuFanLee; cy_huang(黃啟原); linux-kernel@...r.kernel.org; linux-usb@...r.kernel.org; Guenter Roeck
Subject: Re: [PATCH] USB TYPEC: RT1711H Type-C Chip Driver
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,
--
heikki
************* Email Confidentiality Notice ********************
The information contained in this e-mail message (including any attachments) may be confidential, proprietary, privileged, or otherwise exempt from disclosure under applicable laws. It is intended to be conveyed only to the designated recipient(s). Any use, dissemination, distribution, printing, retaining or copying of this e-mail (including its attachments) by unintended recipient(s) is strictly prohibited and may be unlawful. If you are not an intended recipient of this e-mail, or believe that you have received this e-mail in error, please notify the sender immediately (by replying to this e-mail), delete any and all copies of this e-mail (including any attachments) from your system, and do not disclose the content of this e-mail to any other person. Thank you!
Powered by blists - more mailing lists