As it turns out it certainly is a firmware regression issue and the AMD(?) FW team is working on the fix which is expected to be available soon. See also: https://gitlab.freedesktop.org/drm/amd/-/issues/2139#note_1530287