Re: [PATCH 2/3] drm/komeda - At init write GCU control block to handle already on DPU

2022-07-16 Thread Carsten Haitzler
On 7/8/22 17:07, Liviu Dudau wrote: On Mon, Jun 06, 2022 at 12:47:13PM +0100, carsten.haitz...@foss.arm.com wrote: From: Carsten Haitzler If something has already set up the DPU before the komeda driver comes up, it will fail to init because it was just writing to the SRST bit in the GCU co

Re: [PATCH 2/3] drm/komeda - At init write GCU control block to handle already on DPU

2022-07-08 Thread Carsten Haitzler
On 7/8/22 17:07, Liviu Dudau wrote: On Mon, Jun 06, 2022 at 12:47:13PM +0100, carsten.haitz...@foss.arm.com wrote: From: Carsten Haitzler If something has already set up the DPU before the komeda driver comes up, it will fail to init because it was just writing to the SRST bit in the GCU co

Re: [PATCH 2/3] drm/komeda - At init write GCU control block to handle already on DPU

2022-07-08 Thread Liviu Dudau
On Mon, Jun 06, 2022 at 12:47:13PM +0100, carsten.haitz...@foss.arm.com wrote: > From: Carsten Haitzler > > If something has already set up the DPU before the komeda driver comes > up, it will fail to init because it was just writing to the SRST bit in > the GCU control register and ignoring othe

[PATCH 2/3] drm/komeda - At init write GCU control block to handle already on DPU

2022-06-06 Thread carsten . haitzler
From: Carsten Haitzler If something has already set up the DPU before the komeda driver comes up, it will fail to init because it was just writing to the SRST bit in the GCU control register and ignoring others. This resulted in TBU bringup stalling and init failing. By writing completely we also