This is production hardware?
Have you already checked whether a BIOS upgrade for the device could help this issue?
Just to clarify did you guys co-work on this patch, or are you submitting on behalf of wenlunpeng? It right now shows up as you submitting on behalf of wenlunpeng. If you co-worked on it you should also use a Co-Developed-by tag.
Unfortunately again. There's not much we as kernel developers can do when devices behave unpredictably.
As this is suspected to be a BIOS issue, I would like to better understand if the BIOS upgrade fixes it. If it does but you would still like a quirk for the system it should include the BIOS version here.