On Mon, Oct 27, 2025 at 8:56 AM Fabio Estevam <[email protected]> wrote: > > From: Ye Li <[email protected]> > > The change in commit c1af358cf51a ("imx: mx6ull: fix REFTOP_VBGADJ > setting") is not correct. According to latest i.MX6ULL fuse table, > the REFTOP_TRIM[2:0] fuse is defined as below. So the previous codes > are correct, only need to fix the comments. > > Set the REFTOP_VBGADJ field in PMU_MISC0 register based on the > REFTOP_TRIM fuse: > '000" - set REFTOP_VBGADJ[2:0] to 3'b000 > '001" - set REFTOP_VBGADJ[2:0] to 3'b001 > '010" - set REFTOP_VBGADJ[2:0] to 3'b010 > '011" - set REFTOP_VBGADJ[2:0] to 3'b011 > '100" - set REFTOP_VBGADJ[2:0] to 3'b100 > '101" - set REFTOP_VBGADJ[2:0] to 3'b101 > '110" - set REFTOP_VBGADJ[2:0] to 3'b110 > '111" - set REFTOP_VBGADJ[2:0] to 3'b111 > > Sven Schwermer reported: > > "These are the symptoms: Very few of the thousands of devices that we > manufacture (< 1%) fail to decompress a large XZ archive once in Linux > userspace. We have not found any form of memory testing or other load > that reproduces this issue. Reverting the offending patch fixes this > behavior on the affected devices." > > Revert the offending commit to fix the regression. > > Reported-by: Sven Schwermer <[email protected]> > Signed-off-by: Ye Li <[email protected]> > [fabio: Fixed checkpatch warning and added Sven's report] > Signed-off-by: Fabio Estevam <[email protected]>
Applied, thanks.
