Missing and ambiguous information in DW3000 user manual

Hi! As observed in "Missing manual" for register-level access to DW3000 (without using API) - #6 by Nomad, it looks like neither BIAS_KICK or LDO_KICK actually do anything, and the code in the last driver for which source is available doesn’t entirely remedy it.

(Also, that code does some mysterious bit-shifting of the BIASTUNE_CAL OTP value before moving into BIAS_CTRL.)

Is there advice on what should actually be done here? (Other than “just use the official driver on the officially supported MCU chips”…?)