sed and added atomic_commit() vfunc for writeback jobs]
Signed-off-by: Rob Clark
---
Documentation/gpu/drm-kms.rst| 9 ++
drivers/gpu/drm/Makefile | 2 +-
drivers/gpu/drm/drm_atomic.c | 130
drivers/gpu/drm/drm_atomic_helper.c |
On Fri, Feb 23, 2018 at 9:00 AM, Liviu Dudau wrote:
> Hi Rob,
>
> On Fri, Feb 23, 2018 at 08:17:51AM -0500, Rob Clark wrote:
>> From: Brian Starkey
>>
>> Writeback connectors represent writeback engines which can write the
>> CRTC output to a memory framebuffe
On Fri, Feb 23, 2018 at 10:59 AM, Sean Paul wrote:
>
> Have we considered hiding writeback behind a client cap instead?
It is kinda *almost* unneeded, since the connector reports itself as
disconnected.
I'm not sure what the reason was to drop the cap, but I think it would
be better to have a ca
So, I guess this is to do w/ the magic of merge commits, but it looks
like the hunk changing the crtc_ww_class got lost:
~/src/linux master git show --pretty=short
08295b3b5beec9aac0f7a9db86f0fc3792039da3
drivers/gpu/drm/drm_modeset_lock.c
commit 08295b3b5beec9aac0f7a9db86f0fc3792039da3
Au
On Wed, Jan 16, 2019 at 11:49 AM Thomas Hellstrom wrote:
>
> Hi,
>
> On Wed, 2019-01-16 at 09:24 -0500, Rob Clark wrote:
> > So, I guess this is to do w/ the magic of merge commits, but it looks
> > like the hunk changing the crtc_ww_class got lost:
>
> So what hap
