Hi Andre, Fair enough on both counts. I'll slow down and stop reposting every time sashiko replies, and I'll split this into a real series instead of one RFC blob.
On the overlap: found it, it's Parthiban Nallathambi's "Add support for A100/A133 display" series from dri-devel back in Dec 2024 ([email protected]). Looks like you already reviewed a couple of patches in it. It adds allwinner,sun50i-a100-de2-mixer-0, allwinner,sun50i-a100-tcon-top and allwinner,sun50i-a100-display-engine, which is the same DE2 mixer and TCON-TOP hardware my board's DSI path goes through. Compared my mixer0 config against his sun50i_a100_mixer0_cfg field by field. Everything matched except mod_rate: mine was 297000000, his was 300000000. Mine was wrong, just copy-pasted from the existing A64 config and never actually rechecked for A133. My own register dump off real hardware reads 300MHz for both de0 and de1, so his number was right and I've fixed mine to match. So that was a useful find, thanks for the push to go look. That series hasn't moved since Dec 2024 though, no v2 anywhere I could find and it's not in mainline, so I don't want to build directly on top of it. For now I've kept my own a133 compatibles, just with the numbers fixed and a comment pointing at his series for anyone else who runs into the same thing. You mentioned on that series that you'd rather see a fallback to an existing compatible than a new one unless there's a proven reason not to. Given his stuff isn't merged, what do you want me to do here - keep my own a133 compatibles as-is, try to get his series revived and build on that instead, or something else? Cc'ing Parthiban so he knows there's a second board sitting on the same hardware. leow149
