Mark Rutland wrote:

quoted

No, only Kryo and Falkor V1 based SOCs have this problem.  Falkor V2
will have this fixed.  We intend to revert these fixes after Falkor
V1 SOCs are no longer supported.

Supported by whom?

Qualcomm.

Generally, once something's upstreamed we expect it to remain supported.

The V1 SOCs are technically pre-production, but still in wide use and it will be 
a while before they are all replaced by V2 SOCs.  It's only because of the 
"ugliness" of the erratum and its work-around that we want to git rid of it when 
we can.

Cov is better equipped to answer your other questions.

-- 
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.