From: Hans de Goede <hdegoede@redhat.com>
To: Adam Thomson <Adam.Thomson.Opensource@diasemi.com>,
Kyle Tso <kyletso@google.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Guenter Roeck <linux@roeck-us.net>,
Greg KH <gregkh@linuxfoundation.org>,
Badhri Jagan Sridharan <badhri@google.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] usb: typec: tcpm: collision avoidance
Date: Wed, 10 Apr 2019 18:49:08 +0200 [thread overview]
Message-ID: <7dd7ce29-b4e5-02c1-6bdc-11d0e1f77a5f@redhat.com> (raw)
In-Reply-To: <76a3c6df-63c0-78e7-c1ca-c83a30e95d38@redhat.com>
> If I understand the datasheet correctly:
>
> "The FUSB302 has the capability to do autonomous
> DRP toggle. In autonomous toggle the FUSB302
> internally controls the PDWN1, PDWN2, PU_EN1 and
> PU_EN2, MEAS_CC1 and MEAS_CC2 and implements
> a fixed DRP toggle between presenting as a SRC and
> presenting as a SNK. Alternately, it can present as a
> SRC or SNK only and poll CC1 and CC2 continuously."
>
> It is still attaching Rp resp Rd to CC1 or CC2 one at a time
> to detect polarity, so it is still toggling, it just is not
> doing dual-role toggling. This is also expected behavior for
> a sink, a sink may not present Rd on both CC pins at the
> same time, otherwise the source cannot detect the polarity
> and the source also cannot detect if Vconn is necessary.
Erm the "a sink may not present Rd on both CC pins at the same time"
bit obviously is wrong, ignore that please.
next prev parent reply other threads:[~2019-04-10 16:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 12:17 Kyle Tso
2019-04-04 14:13 ` Heikki Krogerus
2019-04-05 13:42 ` Guenter Roeck
2019-04-08 14:17 ` Kyle Tso
2019-04-09 13:02 ` Heikki Krogerus
2019-04-09 13:06 ` Heikki Krogerus
2019-04-09 14:41 ` Hans de Goede
2019-04-10 10:32 ` Adam Thomson
2019-04-10 12:49 ` Kyle Tso
2019-04-10 15:45 ` Hans de Goede
2019-04-10 16:14 ` Adam Thomson
2019-04-10 16:38 ` Hans de Goede
2019-04-10 16:49 ` Hans de Goede [this message]
2019-04-11 9:06 ` Adam Thomson
2019-04-13 20:38 ` Hans de Goede
2019-04-15 10:03 ` Adam Thomson
2019-09-19 10:48 ` Kyle Tso
2019-09-19 11:00 ` Heikki Krogerus
2019-09-19 13:31 ` Guenter Roeck
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=7dd7ce29-b4e5-02c1-6bdc-11d0e1f77a5f@redhat.com \
--to=hdegoede@redhat.com \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=badhri@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kyletso@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
/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
all inboxes | Powered by JetHome®