All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zain Wang <wzz@rock-chips.com>
To: Guenter Roeck <groeck@google.com>
Cc: Guenter Roeck <groeck@chromium.org>,
	Yueyao Zhu <yueyao@google.com>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Some ideas about tcpm driver
Date: Fri, 4 Aug 2017 18:25:59 +0800	[thread overview]
Message-ID: <e42944b0-aeb7-2eff-ba1e-957bb73e02dc@rock-chips.com> (raw)
In-Reply-To: <CABXOdTf1661zJDnQf1ddqTWYozMMH=vAHbQUVM5LxKZ=vX5Qgg@mail.gmail.com>



在 2017/8/3 21:02, Guenter Roeck 写道:
> On Thu, Aug 3, 2017 at 12:28 AM, Zain Wang <wzz@rock-chips.com> wrote:
>> Hi all,
>>
>> In recent days, I tested the fusb302 driver with tcpm. (RK3399 evb board)
>> But I found an issues:
>>      There is not a regulator for type-c vbus power-supply in my board.
>>      The vbus is just controlled by a gpio-pin, and unable to support other
>> voltage except 5V.
> gpio-regulator does not work ?
Thanks for you idea， it works well with regulator-gpio.

Zain
>
>>      But now, I can't use fusb302 driver without workaround fix.
>>      Could you fix it in next version? @Yueyao
>>
>> The altmode looks not complete. I can't enter DP Alt Mode now.
> Yes, I know. Patches welcome.
>
>> And we'd like to used extcon function (used in Chrome) to link usb, dp and
>> type-c together.
> Plan is to use the extcon driver (from cros-ec) to register with the
> type-c infrastructure. I have not thought about how to tie low level
> drivers (fusb/tcpm) with extcon. Ideas welcome.
>
> Guenter
>
>> How do you think about it? @Guenter
>>
>> Thanks
>> Zain
>>
>
>

      reply	other threads:[~2017-08-04 10:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03  7:28 Some ideas about tcpm driver Zain Wang
2017-08-03 13:02 ` Guenter Roeck
2017-08-04 10:25   ` Zain Wang [this message]

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=e42944b0-aeb7-2eff-ba1e-957bb73e02dc@rock-chips.com \
    --to=wzz@rock-chips.com \
    --cc=groeck@chromium.org \
    --cc=groeck@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=yueyao@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.