[Freedreno] xinerma - xrandr apq8064 drm fbdev

2017-06-14 Thread Vinay Simha B N
hi, i am having two encoders dsi1 and dsi2 of same resolution, i want to configure as single resolution 960x864, after configuring as right-of , i got 960x864 resolution, but not able to use as single fb as of xinerma xrandr --output DSI-1 --mode 480x864 --right-of DSI-2 root@linaro-alip:~# xran

Re: [Freedreno] xinerma - xrandr apq8064 drm fbdev

2017-06-14 Thread Rob Clark
On Wed, Jun 14, 2017 at 7:25 AM, Vinay Simha B N wrote: > hi, > > i am having two encoders dsi1 and dsi2 of same resolution, i want to > configure as single resolution 960x864, > > after configuring as right-of , i got 960x864 resolution, but not able to > use as single fb as of xinerma > xrandr -

Re: [Freedreno] [PATCH] drm/msm: Separate locking of buffer resources from struct_mutex

2017-06-14 Thread Rob Clark
On Tue, Jun 13, 2017 at 6:52 PM, Sushmita Susheelendra wrote: > Buffer object specific resources like pages, domains, sg list > need not be protected with struct_mutex. They can be protected > with a buffer object level lock. This simplifies locking and > makes it easier to avoid potential recursi

Re: [Freedreno] [PATCH] drm/msm: Separate locking of buffer resources from struct_mutex

2017-06-14 Thread Susheelendra, Sushmita
Hi Rob, Yes, I’d completely missed the shrinker path in this cleanup. But, yeah, I see how get_pages (which is called with msm_obj->lock held) -> drm_gem_get_pages could trigger shrinker_scan which calls msm_gem_purge. It makes sense to prevent any get_pages/vmap on objects that’ve been marked a

Re: [Freedreno] [PATCH] drm/msm: Separate locking of buffer resources from struct_mutex

2017-06-14 Thread Rob Clark
I think the trick is what is the best way to synchronize access to msm_obj->madv in the shrinker path, since we can't reliably just take msm_obj->lock in shrinker path since we might already hold it: https://hastebin.com/ubafepahov.xml fwiw, that was with my work-in-progress attempt to deal with s