From: Stefan Schake <stschake@gmail.com>
To: eric@anholt.net, stefan.wahren@i2se.com,
gregkh@linuxfoundation.org, linux-rpi-kernel@lists.infradead.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
dave.stevenson@raspberrypi.org
Cc: Stefan Schake <stschake@gmail.com>
Subject: [PATCH] staging: bcm2835-camera: Add TODO for removing overlay support
Date: Fri, 11 May 2018 01:12:44 +0200 [thread overview]
Message-ID: <1525993965-4317-1-git-send-email-stschake@gmail.com> (raw)
The overlay code is non-functional since it relies on firmware control
of the HVS.
Signed-off-by: Stefan Schake <stschake@gmail.com>
---
Dave, does this match your understanding?
drivers/staging/vc04_services/bcm2835-camera/TODO | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/staging/vc04_services/bcm2835-camera/TODO b/drivers/staging/vc04_services/bcm2835-camera/TODO
index 0ab9e88..770fea6 100644
--- a/drivers/staging/vc04_services/bcm2835-camera/TODO
+++ b/drivers/staging/vc04_services/bcm2835-camera/TODO
@@ -32,3 +32,11 @@ We should have VCHI create a platform device once it's initialized,
and have this driver bind to it, so that we automatically load the
v4l2 module after VCHI loads.
+5) Remove overlay support.
+
+We advertise support for a V4L2 overlay implemented through the
+ril.video_render component. This component is non-functional with an
+upstream kernel since the VC4 DRM driver controls the HVS, not the
+firmware. Once we have dma-buf support, the same functionality with
+improved control can be achieved through the DRM interface. We should
+therefore remove all V4L2 overlay functionality from the driver.
--
2.7.4
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next reply other threads:[~2018-05-10 23:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 23:12 Stefan Schake [this message]
2018-05-11 9:21 ` [PATCH] staging: bcm2835-camera: Add TODO for removing overlay support Dave Stevenson
2018-05-14 11:59 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1525993965-4317-1-git-send-email-stschake@gmail.com \
--to=stschake@gmail.com \
--cc=dave.stevenson@raspberrypi.org \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=stefan.wahren@i2se.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.