From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Dufresne Subject: Re: [PATCH v4 3/5] staging: Introduce NVIDIA Tegra video decoder driver Date: Sun, 10 Dec 2017 14:29:39 -0500 Message-ID: <1512934179.4281.15.camel@ndufresne.ca> References: <1a3798f337c0097e67d70226ae3ba665fd9156c2.1508448293.git.digetx@gmail.com> <3ac6a087-def2-014f-673d-1be9d5094635@gmail.com> <93c98569-0282-80d9-78ad-c8ab8fd9db92@xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: Sender: linux-media-owner@vger.kernel.org To: Dmitry Osipenko , Hans Verkuil , Thierry Reding , Jonathan Hunter , Greg Kroah-Hartman , Rob Herring , Mauro Carvalho Chehab , Stephen Warren , Vladimir Zapolskiy Cc: Dan Carpenter , linux-media@vger.kernel.org, linux-tegra@vger.kernel.org, devel@driverdev.osuosl.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Maxime Ripard , Giulio Benetti List-Id: devicetree@vger.kernel.org Le dimanche 10 décembre 2017 à 21:56 +0300, Dmitry Osipenko a écrit : > > I've CC-ed Maxime and Giulio as well: they are looking into adding support for > > the stateless allwinner codec based on this code as well. There may well be > > opportunities for you to work together, esp. on the userspace side. Note that > > Rockchip has the same issue, they too have a stateless HW codec. > > IIUC, we will have to define video decoder parameters in V4L API and then make a > V4L driver / userspace prototype (ffmpeg for example) that will use the requests > API for video decoding in order to upstream the requests API. Does it sound good? Chromium/Chrome already have support for that type of decoder in their tree. In theory, it should just work. Nicolas