#asahi-gpu · 2022-10-04 06:12
svenbut I don’t think that has any dt bindings yet#asahi-gpu · 2022-10-04 06:12
sventhere’s a oob notifier for altmode hotplug inside drm #asahi-gpu · 2022-10-04 05:57
marcandefinitely nothing for thunderbolt, but at least DP alt mode should already be a thing on various systems#asahi-gpu · 2022-10-04 05:57
marcansven: I think we need to come up with our own for that, hopefully stuff that can be reused by other platforms too... I think there may be some things in downstream trees already?#asahi-gpu · 2022-10-04 05:55
linaThere will be a demo tonight ^^#asahi-gpu · 2022-10-04 03:12
danielsDcow[m]: it’ll take some time, but lina is forging the path :)#asahi-gpu · 2022-10-04 01:04
Dcow[m]Good timing for demo first drm driver written with Rust on XDC#asahi-gpu · 2022-10-04 01:04
Dcow[m]Yay#asahi-gpu · 2022-10-04 01:03
Dcow[m]Rust is merged into 6.1-rc1#asahi-gpu · 2022-10-03 19:58
jannauI gave up modeling the display pipeline after DCP, everything assumes components behave like normal hardware. best solution seems to be indeed to stuff the information as property or subnodes into dcp#asahi-gpu · 2022-10-03 18:34
sven*of#asahi-gpu · 2022-10-03 18:34
sventhere’s just some if the type-c-connector stuff we can reuse #asahi-gpu · 2022-10-03 18:34
svenI haven’t found anything that’s even close to the flexibility apple has with the entire typec/thunderbolt/phy/crossbar stuff either #asahi-gpu · 2022-10-03 18:22
marcanif we need to drive them it'll be over i2c via the DCP i2c interface, most likely, if not a higher level abstraction, but that doesn't *necessarily* need to go through the i2c subsystem at this point (not the first DRM driver to not do that for bridges)#asahi-gpu · 2022-10-03 17:52
jannauyes, I have now "apple,mcdp2920" as compatible. if we need to drive them it probably isn't via spi or i2c#asahi-gpu · 2022-10-03 17:46
marcanor something like that#asahi-gpu · 2022-10-03 17:46
marcanI think the DP-HDMI bridges should be just child nodes of dcp or wherever they make sense, and just have a compatible (in case we need to start driving them) and say what the right connector type is on the other end#asahi-gpu · 2022-10-03 17:44
marcanwe're going to have to cook our own#asahi-gpu · 2022-10-03 17:44
marcanI don't expect existing DT bindings to be very useful for this, since they're mostly intended for real hardware, not a giant firmware abstraction#asahi-gpu · 2022-10-03 17:08
jannauthe dp to hdmi bridge is strange as well. it should be modeled to explain hown an (e)dp port can end in an hdmi connector but we do not need to control it#asahi-gpu · 2022-10-03 17:03
svenI‘m not looking forward to model the entire atcphy/crossbar/tps6598x stuff either #asahi-gpu · 2022-10-03 17:02
jannaurequires a power supply which I would have to invent out of dcp#asahi-gpu · 2022-10-03 17:01
jannauhmm, even simple-panel is too complex to model dcp attached display panels in DT#asahi-gpu · 2022-10-03 16:49
svenbrain?#asahi-gpu · 2022-10-03 16:46
alyssasven: brain#asahi-gpu · 2022-10-03 15:07
svenxnu first just connects dcpdptx-port-epic0, then dcp calls setTiledDisplayHints and then xnu connects dcpdptx-port-epic1#asahi-gpu · 2022-10-03 15:07
svenyup, that's also how it detects if the display is tiled apparently#asahi-gpu · 2022-10-03 14:40
marcanI think that happens over the aux channel#asahi-gpu · 2022-10-03 14:40
marcanthe link rate would be determined dynamically by the DP negotiation stuff, so that makes sense#asahi-gpu · 2022-10-03 13:57
svenohh... i think i know what happens. it first just brings up atcphy but doesn't setup the tunables yet, then it routes atcphy to some dcpext and then dcpext calls setLinkRate and only then does it finish setting up atcphy#asahi-gpu · 2022-10-03 13:44
svencan't find anything in that tps6598x datasheet#asahi-gpu · 2022-10-03 13:44
svenhrm, i wonder how it gets the link rate. it needs to know that before setting up ATCPHY#asahi-gpu · 2022-10-03 10:01
svenyes, they always exist #asahi-gpu · 2022-10-03 10:00
marcanbut you still have separate EPICs for the underlying dptx right?#asahi-gpu · 2022-10-03 10:00
marcanah, so that's like some shared one that is special for split mode#asahi-gpu · 2022-10-03 09:59
svenLet me check again, but I think only that appears #asahi-gpu · 2022-10-03 09:59
svenDCPAVSplitDisplayVideoInterface#asahi-gpu · 2022-10-03 09:58
marcanhm, I expected more EPIC instances to show up#asahi-gpu · 2022-10-03 09:58
svenafaict that dpav thing is also shared, it’s just called split interface now#asahi-gpu · 2022-10-03 09:57
marcanand IOMFB needs to know about the tiling config to set up two outputs#asahi-gpu · 2022-10-03 09:56
marcanmy understanding from strings and such is that IOMFB is shared and the EPICs get split#asahi-gpu · 2022-10-03 09:56
marcanI didn't see any obvious place for that other than some unused bits in the EP messages#asahi-gpu · 2022-10-03 09:56
marcanthen there has to be some field somewhere for the index though#asahi-gpu · 2022-10-03 09:56
marcanif IOMFB really splits in half then that would be interesting#asahi-gpu · 2022-10-03 09:55
marcanif there is only one IOMFB then that needs a tiling config from EDID to make sense of both outputs#asahi-gpu · 2022-10-03 09:55
marcanwell, I mean, "just work" in what sense?#asahi-gpu · 2022-10-03 09:55
svenyes, but it seems to be connected to iomfb so I kinda expect everything to either explode or just work when I connect two separate screens #asahi-gpu · 2022-10-03 09:54
marcanI do expect split EPICs for both sides (so you could poke i2c separately etc) but I don't expect the main IOMFB to be split#asahi-gpu · 2022-10-03 09:53
marcansven: isn't the AV interface one of the EPICs? I doubt the main IOMFB is split#asahi-gpu · 2022-10-03 08:59
svenand at least at one point we need to send a message to dptx and then react to the dpav init messages before we get the dptx reply