> -----Original Message----- > From: Ondřej Jirman <megi@xxxxxx> > > On Mon, Feb 26, 2024 at 02:44:21AM +0000, Xu Yang wrote: > > [...] > > > > > > > > But there is no change. Your log has: > > > > > > CC1: 0 -> 0, CC2: 2 -> 2 [state SRC_TRYWAIT, polarity 0, connected] > > > > > > How to interpret this? This is with fusb302 driver. The driver has bunch of > > > > When try sink fails (note: cc:=2 in this period), the tcpm will change to SRC_TRYWAIT > > state and it will pull up CC to Rp-default (cc:=3). Since the partner is a sink-only port, > > I think the type-c chip will sense a connection is established. Therefore, a CC change > > event is reported by type-c chip. I'm not sure the behaviors of fusb302 chip when set > > cc:=3. If it does not generate interrupt for this change, then tcpm may think the partner > > has been disconnected and move the state to SRC_TRYWAIT_UNATTACHED. Maybe it's a > > real hw issue or the event is masked by sw. > > > > Is this dock also failed to connect other sink-only devices? > > The hub is sink-only. It is connected to a DRP phone Type-C port (which is using > fusb302), which is where my log is from. > > I also have a board with husb311 Type-C chip and DRP port, which I can use for > comparison (with/without your patch), I guess. It's TCPCI based (husb311), so > that should eliminate bug in fusb302 driver as a possibility, I think. Yeah, it's a good idea. Looking forward to your results. Thanks, Xu Yang > > Kind regards, > o. >
