Re: [PATCH v2] drm/msm/adreno: Assign revn to A635

2023-07-02 Thread Rob Clark
On Sun, Jul 2, 2023 at 7:34 AM Dmitry Baryshkov wrote: > > On 02/07/2023 17:31, Rob Clark wrote: > > On Sat, Jul 1, 2023 at 5:24 PM Dmitry Baryshkov > > wrote: > >> > >> On Sat, 1 Jul 2023 at 18:50, Rob Clark wrote: > >>> > >>> On Fri, Jun 30, 2023 at 4:12 PM Konrad Dybcio > >>> wrote: >

Re: [PATCH v2] drm/msm/adreno: Assign revn to A635

2023-07-02 Thread Dmitry Baryshkov
On 02/07/2023 17:31, Rob Clark wrote: On Sat, Jul 1, 2023 at 5:24 PM Dmitry Baryshkov wrote: On Sat, 1 Jul 2023 at 18:50, Rob Clark wrote: On Fri, Jun 30, 2023 at 4:12 PM Konrad Dybcio wrote: Recently, a WARN_ON() was introduced to ensure that revn is filled before adreno_is_aXYZ is call

Re: [PATCH v2] drm/msm/adreno: Assign revn to A635

2023-07-02 Thread Rob Clark
On Sat, Jul 1, 2023 at 5:24 PM Dmitry Baryshkov wrote: > > On Sat, 1 Jul 2023 at 18:50, Rob Clark wrote: > > > > On Fri, Jun 30, 2023 at 4:12 PM Konrad Dybcio > > wrote: > > > > > > Recently, a WARN_ON() was introduced to ensure that revn is filled before > > > adreno_is_aXYZ is called. This ho

Re: [PATCH v2] drm/msm/adreno: Assign revn to A635

2023-07-01 Thread Dmitry Baryshkov
On Sat, 1 Jul 2023 at 18:50, Rob Clark wrote: > > On Fri, Jun 30, 2023 at 4:12 PM Konrad Dybcio > wrote: > > > > Recently, a WARN_ON() was introduced to ensure that revn is filled before > > adreno_is_aXYZ is called. This however doesn't work very well when revn is > > 0 by design (such as for A

Re: [PATCH v2] drm/msm/adreno: Assign revn to A635

2023-07-01 Thread Rob Clark
On Sat, Jul 1, 2023 at 8:49 AM Rob Clark wrote: > > On Fri, Jun 30, 2023 at 4:12 PM Konrad Dybcio > wrote: > > > > Recently, a WARN_ON() was introduced to ensure that revn is filled before > > adreno_is_aXYZ is called. This however doesn't work very well when revn is > > 0 by design (such as for

Re: [PATCH v2] drm/msm/adreno: Assign revn to A635

2023-07-01 Thread Rob Clark
On Fri, Jun 30, 2023 at 4:12 PM Konrad Dybcio wrote: > > Recently, a WARN_ON() was introduced to ensure that revn is filled before > adreno_is_aXYZ is called. This however doesn't work very well when revn is > 0 by design (such as for A635). Fill it in as a stopgap solution for > -fixes. > > Fixes

Re: [PATCH v2] drm/msm/adreno: Assign revn to A635

2023-06-30 Thread Dmitry Baryshkov
On Sat, 1 Jul 2023 at 02:12, Konrad Dybcio wrote: > > Recently, a WARN_ON() was introduced to ensure that revn is filled before > adreno_is_aXYZ is called. This however doesn't work very well when revn is > 0 by design (such as for A635). Fill it in as a stopgap solution for > -fixes. > > Fixes: c

[PATCH v2] drm/msm/adreno: Assign revn to A635

2023-06-30 Thread Konrad Dybcio
Recently, a WARN_ON() was introduced to ensure that revn is filled before adreno_is_aXYZ is called. This however doesn't work very well when revn is 0 by design (such as for A635). Fill it in as a stopgap solution for -fixes. Fixes: cc943f43ece7 ("drm/msm/adreno: warn if chip revn is verified befo