Received: by 10.223.164.202 with SMTP id h10csp2940226wrb; Tue, 28 Nov 2017 03:56:26 -0800 (PST) X-Google-Smtp-Source: AGs4zMbAJzzbE5NYWXB48mDsLVhde2mwINVnprQCLAPrrAIqzwvXZRBZYOlN3UzzwOoaXpfu0AoW X-Received: by 10.99.102.196 with SMTP id a187mr40432980pgc.346.1511870186107; Tue, 28 Nov 2017 03:56:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1511870186; cv=none; d=google.com; s=arc-20160816; b=YV1XNtN49qXQrX98EyFGKnC9KM4hEU6vfQCWsr3VIOZIaNE9Xrapym7oMHZlsETZ0p +JqbuJJL5CThbA1vwlCYaVCZ5qxp6eeJ7I/bHxwQRqSr+a9DWHRNHtOEhGEAIMqlHbIe aLkd9HHJAlrwOpanyB0j26XRl9zbvYLhY6Df0MDdI60ETA8+ly0ISjXDjVE6JUCz4L53 2wv8aV+PcF34rrAejhEp8MKB2CQOx4Sl/5fRGBUH6+R5PS03nuZ7pGdy0mNkLzsrd2vi QzA9bC6+pCa7yLTkA/dA6Y/bUVk3rz1rl4QzsycpnNSsPkbuFqIzKmbpVQIXsJqQfBrK jtSA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=bIiS/wYHfZZKQ+a6ofrW3XY6fewapsgoci9ek/Ufp8M=; b=wA8QLgEwcUNToHWg/ewff03SutSacF8dA5kx/gYujd24rEHWmzPzJ+Nyivw7Ht8pNx Oacw8LSYW42MZ+5FnpMiw7LMTrii3ztbj/kcYzDs8phDnFWE37MrpeIpYvJyeLqovAcm rCM8jbSNZuWwz3dC5jJoELKarNlHnJUiDL4w7eQYljKKV+0dMDfiwnB1f2u8pAzJULeM 9tyty5cnbTTVdET5Q0AvTJgeE9ywEikAPzDXs7aDwWlOjOXP/ytl1faZ2VHP0wZI45HR CNenoiO8+uuPrwCVkmU/F6shRGJoTH+R0O4L1MkpXTC0tcXHVidkSoKhbO6JK10R3B3c qKFw== ARC-Authentication-Results: i=1; mx.google.com; dkim=temperror (no key for signature) header.i=@micronovasrl.com header.s=dkim header.b=HOM4KZqx; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q80si27129049pfj.192.2017.11.28.03.56.14; Tue, 28 Nov 2017 03:56:26 -0800 (PST) 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; Authentication-Results: mx.google.com; dkim=temperror (no key for signature) header.i=@micronovasrl.com header.s=dkim header.b=HOM4KZqx; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754073AbdK1LyM (ORCPT + 78 others); Tue, 28 Nov 2017 06:54:12 -0500 Received: from mail.micronovasrl.com ([212.103.203.10]:54146 "EHLO mail.micronovasrl.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751818AbdK1LyK (ORCPT ); Tue, 28 Nov 2017 06:54:10 -0500 Received: from mail.micronovasrl.com (mail.micronovasrl.com [127.0.0.1]) by mail.micronovasrl.com (Postfix) with ESMTP id 4EFF7B00A19 for ; Tue, 28 Nov 2017 12:54:09 +0100 (CET) Authentication-Results: mail.micronovasrl.com (amavisd-new); dkim=pass reason="pass (just generated, assumed good)" header.d=micronovasrl.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=micronovasrl.com; h=content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:to:subject:subject; s=dkim; t= 1511870048; x=1512734049; bh=bBOh9clJu0HwuzKu1uWherdOrZY86IoXfc3 UDbj98BY=; b=HOM4KZqx1Wb8H1qBWTBPQemvw17a+WvttXqWY+n+J0GR7Wn6tps Lekp/85TsXGYu+gzEa8K4zUNct3Si1oVkHomoNbKlcaUKVfkzFj/uyBtyAj+htm8 AHNN16mdQQFBYDBu6rb6TSK14PAz9v4c9KcrxDe/726WPZhnE0oPZb+w= X-Virus-Scanned: Debian amavisd-new at mail.micronovasrl.com Received: from mail.micronovasrl.com ([127.0.0.1]) by mail.micronovasrl.com (mail.micronovasrl.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id cOhoQrO6Y_NS for ; Tue, 28 Nov 2017 12:54:08 +0100 (CET) Received: from [192.168.123.215] (benettig-pc.dominio.micronovasrl.com [192.168.123.215]) by mail.micronovasrl.com (Postfix) with ESMTPSA id 97380B00171; Tue, 28 Nov 2017 12:54:08 +0100 (CET) Subject: Re: [linux-sunxi] Cedrus driver To: Thomas van Kleef , Maxime Ripard Cc: Hans Verkuil , Andreas Baierl , linux-sunxi , linux@armlinux.org.uk, wens@csie.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org References: <1511868558-1962148761.366cc20c7e@prakkezator.vehosting.nl> From: Giulio Benetti Message-ID: Date: Tue, 28 Nov 2017 12:54:08 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: it Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Thomas, Il 28/11/2017 12:29, Thomas van Kleef ha scritto: > Hi, > > On 28-11-17 12:26, Giulio Benetti wrote: >> Hi Thomas, >> >> Il 28/11/2017 12:20, Thomas van Kleef ha scritto: >>> On 28-11-17 10:50, Giulio Benetti wrote: >>>> Hi Maxime, >>>> >>>> Il 28/11/2017 09:35, Maxime Ripard ha scritto: >>>>> On Tue, Nov 28, 2017 at 01:03:59AM +0100, Giulio Benetti wrote: >>>>>> Hi Maxime, >>>>>> >>>>>> Il 16/11/2017 14:42, Giulio Benetti ha scritto: >>>>>>> Hi, >>>>>>> >>>>>>> Il 16/11/2017 14:39, Maxime Ripard ha scritto: >>>>>>>> On Thu, Nov 16, 2017 at 02:17:08PM +0100, Giulio Benetti wrote: >>>>>>>>> Hi Hans, >>>>>>>>> >>>>>>>>> Il 16/11/2017 14:12, Hans Verkuil ha scritto: >>>>>>>>>> On 16/11/17 13:57, Giulio Benetti wrote: >>>>>>>>>>> Il 16/11/2017 13:53, Maxime Ripard ha scritto: >>>>>>>>>>>> On Thu, Nov 16, 2017 at 01:30:52PM +0100, Giulio Benetti wrote: >>>>>>>>>>>>>> On Thu, Nov 16, 2017 at 11:37:30AM +0100, Giulio Benetti wrote: >>>>>>>>>>>>>>> Il 16/11/2017 11:31, Andreas Baierl ha scritto: >>>>>>>>>>>>>>>> Am 16.11.2017 um 11:13 schrieb Giulio Benetti: >>>>>>>>>>>>>>>>> Hello, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hello, >>>>>>>>>>>>>>>>> I'm wondering why cedrus >>>>>>>>>>>>>>>>> https://github.com/FlorentRevest/linux-sunxi-cedrus >>>>>>>>>>>>>>>>> has never been >>>>>>>>>>>>>>>>> merged with linux-sunxi sunxi-next. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Because it is not ready to be >>>>>>>>>>>>>>>> merged. It depends on the v4l2 >>>>>>>>>>>>>>>> request >>>>>>>>>>>>>>>> API, which was not merged and which is re-worked atm. >>>>>>>>>>>>>>>> Also, sunxi-cedrus itself is not in >>>>>>>>>>>>>>>> a finished state and is not as >>>>>>>>>>>>>>>> feature-complete to be merged. Anyway it might be something for >>>>>>>>>>>>>>>> staging... Has there been a [RFC] on the mailing list at all? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Where can I find a list of TODOs to get it ready to be merged? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Assuming that the request API is in, we'd need to: >>>>>>>>>>>>>> ������� - Finish the MPEG4 support >>>>>>>>>>>>>> ������� - Work on more useful codecs (H264 comes to my mind) >>>>>>>>>>>>>> ������� - Implement the DRM planes support for >>>>>>>>>>>>>> the custom frame format >>>>>>>>>>>>>> ������� - Implement the DRM planes support for scaling >>>>>>>>>>>>>> ������� - Test it on more SoCs >>>>>>>>>>>>>> >>>>>>>>>>>>>> Or something along those lines. >>>>>>>>>>>>> >>>>>>>>>>>>> Lot of work to do >>>>>>>>>>>> >>>>>>>>>>>> Well... If it was fast and easy it would have been done already :) >>>>>>>>>>> >>>>>>>>>>> :)) >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>>>>>> I see it seems to be dead, no commit in 1 year. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Yes, because the author did this >>>>>>>>>>>>>>>> during an internship, which ended >>>>>>>>>>>>>>>> ... >>>>>>>>>>>>>>>> Afaik nobody picked up his work yet. >>>>>>>>>>>>>> >>>>>>>>>>>>>> That's not entirely true. Some work has been >>>>>>>>>>>>>> done by Thomas (in CC), >>>>>>>>>>>>>> especially on the display engine side, but last time we talked his >>>>>>>>>>>>>> work was not really upstreamable. >>>>>>>>>>>>>> >>>>>>>>>>>>>> We will also resume that effort starting next march. >>>>>>>>>>>>> >>>>>>>>>>>>> Is it possible a preview on a separate >>>>>>>>>>>>> Reporitory to start working on now? >>>>>>>>>>>>> Expecially to start porting everything done by >>>>>>>>>>>>> FlorentRevest to mainline, >>>>>>>>>>>>> admitted you've not already done. >>>>>>>>>>>> >>>>>>>>>>>> I'm not sure what you're asking for. Florent's work >>>>>>>>>>>> *was* on mainline. >>>>>>>>>>> >>>>>>>>>>> and then they took it off because it was unmantained? >>>>>>>>>>> You've spoken about Thomas(in CC) not ready, >>>>>>>>>>> maybe I could help on that if it's public to accelerate. >>>>>>>>>>> If I'm able to of course, this is my primary concern. >>>>>>>>>>> >>>>>>>>>>> Otherwise, in which way can I help improving it to make >>>>>>>>>>> it accept to linux-sunxi? >>>>>>>>>>> Starting from Florent's work and porting it to sunxi-next to begin? >>>>>>>>>>> And after that adding all features you've listed? >>>>>>>>>>> Tell me what I can do(I repeat, if I'm able to). >>>>>>>>>> >>>>>>>>>> The bottleneck is that the Request API is not mainlined. We >>>>>>>>>> restarted work >>>>>>>>>> on it after a meeting a few weeks back where we all agreed >>>>>>>>>> on the roadmap >>>>>>>>>> so hopefully it will go into mainline Q1 or Q2 next year. >>>>>>>>>> >>>>>>>>>> That said, you can use Florent's patch series for further development. >>>>>>>>>> It should be relatively easy to convert it to the final version of the >>>>>>>>>> Request API. Just note that the public API of the final >>>>>>>>>> Request API will >>>>>>>>>> be somewhat different from the old version Florent's patch >>>>>>>>>> series is using. >>>>>>>>> >>>>>>>>> So I'm going to try soon to : >>>>>>>>> 1) adapt that patchset to sunxi-next >>>>>>>>> 2) add A20 support >>>>>>>>> 3) add A33 support >>>>>>>>> 4) after mainlined APIs, merge >>>>>>>> >>>>>>>> That sounds good. Thomas already has the support for the A20, and as I >>>>>>>> was saying, there is someone that is going to work full time on this >>>>>>>> in a couple monthes on our side. >>>>>>>> >>>>>>>> I'll set up a git repo on github so that we can collaborate until the >>>>>>>> request API is ready. >>>>>> >>>>>> Any news about git repo? >>>>>> When do you plan to do it more or less? >>>>> >>>>> I started to do it yesterday. >>>>> >>>>> https://github.com/free-electrons/linux-cedrus >>>>> https://github.com/free-electrons/libva-cedrus >>>> >>>> Great, I'm cloning. >>>> 1st: have it working with A20 with kernel as is and libva as buildroot package >>>> 2nd: porting to sunxi-next branch of linux-sunxi and check libva if can work as is >>>> >>>> Thank you >>>> So, I have been rebasing to 4.14.0 and have the cedrus driver working. >>> I have pulled linux-mainline 4.14.0. Then pulled the requests2 branch from Hans >>> Verkuil's media_tree. I have a patch available of the merge between these 2 >>> branches. >>> After this I pulled the sunxi-cedrus repository from Florent Revests github. I >>> believe this one is the same as the ones you are cloning right now. >>> I have merged this and have a patch available for this as well. >>> >>> So to summarize: >>> � o pulled linux 4.14 from: >>> ���� https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git >>> � o pulled requests2 from: >>> ���� https://git.linuxtv.org/hverkuil/media_tree.git?h=requests2 >>> ���� will be replaced with the work, when it is done, in: >>> ����� https://git.linuxtv.org/hverkuil/media_tree.git?h=ctrl-req-v2 >>> � o pulled linux-sunxi-cedrus from: >>> ���� https://github.com/FlorentRevest/linux-sunxi-cedrus >>> >>> � o merged and made patch between linux4.14 and requests2 >>> � o merged and made patch with linux-sunxi-cedrus >>> � o Verified that the video-engine is decofing mpeg-2 on the Allwinner A20. >>> >>> So maybe if someone is interested in this, I could place the patches somewhere? >>> Just let me know. >> >> Sure it's interesting! >> You could setup your github repo with all you patches applied as commits, but I think you should work against linux-sunxi sunxi-next branch. >> >>> >>> It would be nice to be able to play a file, so I would have to prepare our >>> custom player and make a patch between the current sunxi-cedrus-drv-video and >>> the one on https://github.com/FlorentRevest/sunxi-cedrus-drv-video. >>> So I will start with this if there is any interest. >> >> I am interested for sure. >> >>> >>> Should I be working in sunxi-next I wonder? >> >> Yes, this is the best way, cedrus is very specific to sunxi. >> So before working on mainline, I think the best is to work un sunxi-next branch. > Is the requests2 api in sunxi-next? It should be there, take a look at latest commit of yesterday: https://github.com/linux-sunxi/linux-sunxi/commit/df7cacd062cd84c551d7e72f15b1af6d71abc198 >> >> Is it right Maxime? >> >>>>> >>>>> Maxime >>>>> >>>> >>>> >> >> > Thomas > -- Giulio Benetti R&D Manager & Advanced Research MICRONOVA SRL Sede: Via A. Niedda 3 - 35010 Vigonza (PD) Tel. 049/8931563 - Fax 049/8931346 Cod.Fiscale - P.IVA 02663420285 Capitale Sociale � 26.000 i.v. Iscritta al Reg. Imprese di Padova N. 02663420285 Numero R.E.A. 258642 From 1585309283169943716@xxx Tue Nov 28 11:32:26 +0000 2017 X-GM-THRID: 1584225895006680074 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread