Re: GPU/DRM issue with DSI commands on msm 8916

2018-04-19 Thread Daniel Mack
On Wednesday, April 18, 2018 10:06 AM, Archit Taneja wrote: > On Tuesday 17 April 2018 05:51 PM, Daniel Mack wrote: > Thanks for debugging this so thoroughly. > >> It shows an underlying problem in the msm driver's clock components >> though, because without this patch, the clocks will be effectiv

Re: GPU/DRM issue with DSI commands on msm 8916

2018-04-19 Thread Daniel Mack
On Wednesday, April 18, 2018 10:53 AM, Archit Taneja wrote: > On Wednesday 18 April 2018 01:58 PM, Daniel Mack wrote: >> On Wednesday, April 18, 2018 10:06 AM, Archit Taneja wrote: >>> One easy way to get around this would be to not try to set the clock >>> rates every time we try to send a comman

Re: GPU/DRM issue with DSI commands on msm 8916

2018-04-18 Thread Archit Taneja
On Wednesday 18 April 2018 01:58 PM, Daniel Mack wrote: On Wednesday, April 18, 2018 10:06 AM, Archit Taneja wrote: On Tuesday 17 April 2018 05:51 PM, Daniel Mack wrote: Thanks for debugging this so thoroughly. It shows an underlying problem in the msm driver's clock components though, becau

Re: GPU/DRM issue with DSI commands on msm 8916

2018-04-18 Thread Archit Taneja
Hi Daniel, On Tuesday 17 April 2018 05:51 PM, Daniel Mack wrote: (cc Stephen) Hi Archit, On Monday, April 16, 2018 07:06 PM, Daniel Mack wrote: On Monday, April 09, 2018 03:08 PM, Archit Taneja wrote: You could comment out the pm_runtime_put_sync() calls in drivers/gpu/drm/msm/dsi/dsi_host.c

Re: GPU/DRM issue with DSI commands on msm 8916

2018-04-18 Thread Daniel Mack
(cc Stephen) Hi Archit, On Monday, April 16, 2018 07:06 PM, Daniel Mack wrote: > On Monday, April 09, 2018 03:08 PM, Archit Taneja wrote: You could comment out the pm_runtime_put_sync() calls in drivers/gpu/drm/msm/dsi/dsi_host.c, in case some registers got reset during put_sync an

Re: GPU/DRM issue with DSI commands on msm 8916

2018-04-17 Thread Daniel Mack
Hi Archit, On Monday, April 09, 2018 03:08 PM, Archit Taneja wrote: >>> You could comment out the pm_runtime_put_sync() calls in >>> drivers/gpu/drm/msm/dsi/dsi_host.c, in case some registers got >>> reset during put_sync and weren't restored correctly after get_sync(). >> >> That was my first sus

Re: GPU/DRM issue with DSI commands on msm 8916

2018-04-09 Thread Daniel Mack
Hi Archit, Thanks a lot for your reply. On Friday, April 06, 2018 01:25 PM, Archit Taneja wrote: > On Thursday 05 April 2018 08:28 PM, Daniel Mack wrote: >> I'm having issues with the GPU/DRM drivers on a msm8916 based platform >> which is very similar to the DragonBoard 410c. In my setup, a DSI

Re: GPU/DRM issue with DSI commands on msm 8916

2018-04-09 Thread Archit Taneja
On Monday 09 April 2018 04:28 PM, Daniel Mack wrote: Hi Archit, Thanks a lot for your reply. On Friday, April 06, 2018 01:25 PM, Archit Taneja wrote: On Thursday 05 April 2018 08:28 PM, Daniel Mack wrote: I'm having issues with the GPU/DRM drivers on a msm8916 based platform which is very s

Re: GPU/DRM issue with DSI commands on msm 8916

2018-04-06 Thread Archit Taneja
Hi, On Thursday 05 April 2018 08:28 PM, Daniel Mack wrote: Hi, I'm having issues with the GPU/DRM drivers on a msm8916 based platform which is very similar to the DragonBoard 410c. In my setup, a DSI display is directly connected to the SoC, and the video link is stable. However, when the host

GPU/DRM issue with DSI commands on msm 8916

2018-04-05 Thread Daniel Mack
Hi, I'm having issues with the GPU/DRM drivers on a msm8916 based platform which is very similar to the DragonBoard 410c. In my setup, a DSI display is directly connected to the SoC, and the video link is stable. However, when the host sends DCS commands down to the DSI panel (for instance to set