specification: inconsisten names for timestamp in the frame buffer
TIMESTAMP_L_W has field TIME_STAMP_31_0
TIMESTAMP_U_W has field TIMESTAMP_L_W
Why? I was drenched in shame when I have read "This is crazy" in review referencing to automatically generated structures. Yes, it is possible to argue that the tool generates consistent constructs for all registers even that it has not significant meaning when it is full 32-single value one. But when you have no explanation for mismatch of names of the fields then it is a worse.
Please, consider what can be done with this. It can be marked as issue WontFix for 2.0 version, but should stay open and considered for some resolution.