Christopher Covington wrote:

You might want to make this <= 1 and also change firmware to 0 so that new
firmware with old kernels, new kernels with old firmware, and new kernels
with new firmware all get the workaround applied.

I thought about that, but there is apparently no firmware that sets the value to 0.

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.