> > index b8865fc9efce..1a0dc7f7f857 100644
> > --- a/drivers/gpu/drm/panfrost/panfrost_issues.h
> > +++ b/drivers/gpu/drm/panfrost/panfrost_issues.h
> > @@ -258,6 +258,11 @@ enum panfrost_hw_issue {
> >
> > #define hw_issues_g76 0
> >
> > +#define hw_issues_g57 (\
> > + BIT_ULL(HW_ISSUE_TTRX_2968_TTRX_3162) | \
> > + BIT_ULL(HW_ISSUE_TTRX_3076) | \
> > + BIT_ULL(HW_ISSUE_TTRX_3485))
>
> Do you know whether you have an r0p0 or an r0p1 Natt? Only the r0p0 has
> the 3485 issue, and we might be lucky and it's the r0p1 that's "in the
> wild".
Sadly, I believe I have an r0p0. I don't know if future spins of the
same SoC would be bumped up, but I'm skeptical.
> It would be good to annotate these lists with the hardware revisions
> when there is a difference.
Sure.
