Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
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
Message-Id: <1525993965-4317-1-git-send-email-stschake@gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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