Re: [PATCH 5/7] drm/msm/a5xx: Fix VPC protect value in gpu_write()

2020-09-28 Thread AngeloGioacchino Del Regno
Il giorno lun 28 set 2020 alle ore 18:16 Jordan Crouse ha scritto: > > On Sat, Sep 26, 2020 at 02:51:44PM +0200, khol...@gmail.com wrote: > > From: Konrad Dybcio > > > > The upstream API for some reason uses logbase2 instead of > > just passing the argument as-is, whereas downstream CAF > >

Re: [PATCH 5/7] drm/msm/a5xx: Fix VPC protect value in gpu_write()

2020-09-28 Thread Jordan Crouse
On Sat, Sep 26, 2020 at 02:51:44PM +0200, khol...@gmail.com wrote: > From: Konrad Dybcio > > The upstream API for some reason uses logbase2 instead of > just passing the argument as-is, whereas downstream CAF > kernel does the latter. > > Hence, a mistake has been made when porting: > 4 is the

[PATCH 5/7] drm/msm/a5xx: Fix VPC protect value in gpu_write()

2020-09-26 Thread kholk11
From: Konrad Dybcio The upstream API for some reason uses logbase2 instead of just passing the argument as-is, whereas downstream CAF kernel does the latter. Hence, a mistake has been made when porting: 4 is the value that's supposed to be passed, but log2(4) = 2. Changing the value to 16 (=