linux-kernel - Re: Missing MIPI IPU6 camera driver for Intel Alder Lake laptops

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 15 Aug 2022 10:15:49 +0300
From:   Laurent Pinchart <laurent.pinchart@...asonboard.com>
To:     Sergey Senozhatsky <senozhatsky@...omium.org>
Cc:     Greg KH <gregkh@...uxfoundation.org>,
        Paul Menzel <pmenzel@...gen.mpg.de>,
        Wang Yating <yating.wang@...el.com>,
        Christoph Jechlitschek <christoph.jechlitschek@...el.com>,
        Hao Yao <hao.yao@...el.com>, Andy Yeh <andy.yeh@...el.com>,
        Sakari Ailus <sakari.ailus@...ux.intel.com>,
        Bingbu Cao <bingbu.cao@...el.com>,
        Tianshu Qiu <tian.shu.qiu@...el.com>,
        linux-media@...r.kernel.org, Mark Pearson <markpearson@...ovo.com>,
        Dell.Client.Kernel@...l.com, linux-kernel@...r.kernel.org,
        Guenter Roeck <groeck@...gle.com>,
        Andy Whitcroft <apw@...onical.com>,
        Kai-Heng Feng <kai.heng.feng@...onical.com>,
        Christian Schaller <cschalle@...hat.com>,
        Wouter Bolsterlee <wouter@...sterl.ee>,
        Miguel Palhas <mpalhas@...il.com>, it+linux-media@...gen.mpg.de
Subject: Re: Missing MIPI IPU6 camera driver for Intel Alder Lake laptops

On Mon, Aug 15, 2022 at 04:07:32PM +0900, Sergey Senozhatsky wrote:
> On (22/08/15 09:02), Greg KH wrote:
> [..]
> > > We haven't sent out KCAM for upstream review yet. It's open sourced,
> > > as of this moment [1], but we still need some time and wanted to convert
> > > one of the previous generations of IPU drivers (IPU3) to KCAM first to
> > > see if everything is working as we wanted it to.
> > 
> > That didn't answer my question on when you were planning to actually
> > submit this :)
> 
> Definitely not today. Someday, for sure :)
> 
> I don't want to promise any timelines. But we are certainly not
> talking "weeks", we are talking "months". Several months is a
> realistic timeline.

If I were to bet, I'd say no less than a year :-) And even then, as
stated separately, you'll have to convince the upstream community that
the API is suitable. It would be best to work with upstream today on a
proposal that please all parties, and not wait a year for a full
implementation to be ready, submitted, and rejected.

-- 
Regards,

Laurent Pinchart