#asahi-dev · 2026-01-04 20:32
rosalyntg_(realizing what I said is pretty much the same as what you said. And that's what qualcomm tried and got NAK'd for?)#asahi-dev · 2026-01-04 20:30
rosalyntg_jannu: I'll look into what the qualcomm folks ended up doing...#asahi-dev · 2026-01-04 20:29
rosalyntg_I mean my thought was to have 2 connectors, have DT nodes for them, and then put references to those connector nodes in the displayport = property#asahi-dev · 2026-01-04 18:36
rosalyntg_sounds good, thanks!#asahi-dev · 2026-01-04 18:32
rosalyntg_unfortunately i can't see any device trees that actually use that fwiw--searching for `displayport =` only gives stuff in apple dts....#asahi-dev · 2026-01-04 18:31
rosalyntg_i see, hence direclty calling the oob hp. i wonder why jannau considered it a hack#asahi-dev · 2026-01-04 18:30
rosalyntg_gotcha. I was kinda working if the status_rx field of tps6598x_dp_sid_status_reg was the vdo considering the vdo is at the same offset for the tbt one, and the dp altmode driver takes that vdo and assings to a `status` field, but that was nothing more than blind conjectore....#asahi-dev · 2026-01-04 18:28
rosalyntg_interesting, ok makes sense#asahi-dev · 2026-01-04 18:27
rosalyntg_yep, hitting that on my TB dock :/#asahi-dev · 2026-01-04 18:27
rosalyntg_yeah saw that part, just wasn't familiar enough to know exactly what functionality the altmodes/dp.c implements. so that logic is...directly in the PD chip?#asahi-dev · 2026-01-04 18:27
rosalyntg_I see, that makes sense then#asahi-dev · 2026-01-04 18:26
rosalyntg_sven: thanks, interesting. drm_bridge makes sense for the DP->HDMI probably (need to read more about it, the DRM drive I've written doesn't use it). Not sure that it makes sense to me for the type-c ports--esp because the generic dp altmode driver (typec/altmodes/displayport.c) already has a way to send the hotplug events to DRM...but maybe there's some reason we can't use that#asahi-dev · 2026-01-04 18:15
rosalyntg_jannau: from my looking at what my x86 laptop does, I think we should probably have 2 drm_connector's for the DCPext. That way, the oob hotplug event can be fed to the right connector in DRM so that it gets wired correctly. Am I correct in thinking that its the dptx_phy argument of dptxport_connect that tells the DCP which ATC to send the signal to? Or do I have some wires crossed....#asahi-dev · 2026-01-04 18:06
rosalyntg_Sounds good, thx. I've taken a first pass (not functioning yet) and ideally would run that by someone to make sure I'm understanding all the interactions properly#asahi-dev · 2026-01-04 18:06
rosalyntg_yep, I understand#asahi-dev · 2026-01-04 18:05
rosalyntg_ok, thanks. what's best IRC ediquette here, send a DM?#asahi-dev · 2026-01-04 18:04
rosalyntg_no, talking about, for example M1 Macbook Air, so one dcpext shared between two USB-C ports#asahi-dev · 2026-01-04 18:02
rosalyntg_sven: curious if you sway my messages above about enabling both USB-C ports for DP alt mode (or maybe you can point me to someone who's better to talk to?)#asahi-dev · 2026-01-04 03:39
rosalyntg_(as well as similar treatment for the mux-controls)#asahi-dev · 2026-01-04 03:34
rosalyntg_Am I correct in thinking the correct way to get both USB-C ports working with DP-altmode is dropping the apple,dptx-phy, adding both phys to the dcpext, then calling dptxport_connect after a DP altmode has been negotiated on the correct phy? I'd be interested in taking that on if nobody is already working on it....