Since this is Google making the SoC, surely we have Linux drivers within a month for it? Already upstreamed? Some register documentation? I didn't check, but I suppose the answer is "no". Can't keep pointing at Qualcomm anymore, I guess.
That's not how open source works in SoC design. In fact it doesn't work at all an here's why: Google hasn't made the SoC and doesn't own the IP, it most likely bought a bunch of IP blocks from established vendors like Cadence, Synopys, Samsung, etc and fused them together to create a SoC. All those IPs come with their own license terms and NDAs that limit what you can do with it. You can use it in your final product…
This driver code is often very self contained and does not use many or any Linux frameworks, it should be easy to integrate it into any operating system in any way. Normally you have to rewrite the driver code you get from Cadence and Synopsys to get it integrated in upstream Linux, because it does not meet the upstream Linux guidelines. This is a general problem with the out of tree drivers you get from the semiconductor industry.
There are also big players in the semiconductor industry which demand that every code inside the Linux kernel they ship has to be under GPL for legal compliance.
There is also not a single bad guy in the semiconductor industry which prevents upstream Linux support. Every player could do it, Google probably got most of the drivers in source for their Pixel phones and could have upstreamed them, but most of them probably need a rewrite. They could have offered Qualcomm some money to port support for the SoC used in a Pixel phone to a more recent major kernel version, I am pretty sure Qualcomm would have done it for the right amount of money.