@valpackett @WebKitGTK It should definitely help. We have not been very actively checking out things with Freedreno (due to lack of more hands/time/hardware), but we did notice improvements on some setups where we were aware scrolling was subpar.
Note that with the (also new!) async scrolling we are prioritizing responsiveness to user input, which may result in scrolling (and its animation) being applied always more promptly; but it can still happen that painting tiles cannot be done fast enough to always populate the “empty” canvas before it scrolls into the viewport. The heuristics of what to schedule for painting next depending on scroll speed, direction, etc. has not been changed, so it might still be possible to keep improving.
Last thing: if you notice that the situation has not improved with Freedreno in 2.52.x, would you be so kind to send me a note about what your setup is? I can't promise to take a look *soon*, but it would be good to know, specially if it's something that can affect more Freedreno users 
@aperezdc @WebKitGTK cool, can't wait for 2.52 to get packaged! yeah no what I'm seeing with 2.48 + touchscreen on my main phone is not a performance thing, but rather it's just not scheduling many frames at all while inertia is going and also for the first second or so of a touch scroll. If the async scrolling changes how all that works, it's gotta be good!
on an older (a5xx) device it barely renders anything at all though.. I'll have to retest that on the new version too