3 Jul
2018
3 Jul
'18
7:45 p.m.
On Tue, 3 Jul 2018 19:44:00 +0200 Boris Brezillon boris.brezillon@bootlin.com wrote:
On Tue, 3 Jul 2018 19:40:46 +0200 Boris Brezillon boris.brezillon@bootlin.com wrote:
Fix the bullet list declaration in the overview section.
Signed-off-by: Boris Brezillon boris.brezillon@bootlin.com
Forgot to add:
Reported-by: Daniel Vetter daniel.vetter@ffwll.ch
And
Fixes: 935774cd71fe ("drm: Add writeback connector type")
is missing too.
drivers/gpu/drm/drm_writeback.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/drm_writeback.c b/drivers/gpu/drm/drm_writeback.c index 827395071f0b..69e7a63cfcc3 100644 --- a/drivers/gpu/drm/drm_writeback.c +++ b/drivers/gpu/drm/drm_writeback.c @@ -22,10 +22,13 @@
- Writeback connectors are used to expose hardware which can write the output
- from a CRTC to a memory buffer. They are used and act similarly to other
- types of connectors, with some important differences:
- Writeback connectors don't provide a way to output visually to the user.
- Writeback connectors should always report as "disconnected" (so that
- clients which don't understand them will ignore them).
- Writeback connectors don't have EDID.
- Writeback connectors don't provide a way to output visually to the user.
- Writeback connectors should always report as "disconnected" (so that
- clients which don't understand them will ignore them).
- Writeback connectors don't have EDID.
- A framebuffer may only be attached to a writeback connector when the
- connector is attached to a CRTC. The WRITEBACK_FB_ID property which sets the