Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Wed, 17 Aug 2022 18:49:44 +0900
From:   Sergey Senozhatsky <senozhatsky@chromium.org>
To:     Sakari Ailus <sakari.ailus@linux.intel.com>
Cc:     Greg KH <gregkh@linuxfoundation.org>,
        Sergey Senozhatsky <senozhatsky@chromium.org>,
        Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
        Paul Menzel <pmenzel@molgen.mpg.de>,
        Wang Yating <yating.wang@intel.com>,
        Christoph Jechlitschek <christoph.jechlitschek@intel.com>,
        Hao Yao <hao.yao@intel.com>, Andy Yeh <andy.yeh@intel.com>,
        Bingbu Cao <bingbu.cao@intel.com>,
        Tianshu Qiu <tian.shu.qiu@intel.com>,
        linux-media@vger.kernel.org, Mark Pearson <markpearson@lenovo.com>,
        Dell.Client.Kernel@dell.com, linux-kernel@vger.kernel.org,
        Guenter Roeck <groeck@google.com>,
        Andy Whitcroft <apw@canonical.com>,
        Kai-Heng Feng <kai.heng.feng@canonical.com>,
        Christian Schaller <cschalle@redhat.com>,
        Wouter Bolsterlee <wouter@bolsterl.ee>,
        Miguel Palhas <mpalhas@gmail.com>,
        it+linux-media@molgen.mpg.de, "Hu, Jerry W" <jerry.w.hu@intel.com>
Subject: Re: Missing MIPI IPU6 camera driver for Intel Alder Lake laptops
Message-ID: <Yvy5uCh7kW+oNEcn@google.com>
References: <YvUaEDMbZD70x+hD@kroah.com>
 <YvUbhx4HSxAAwIvv@pendragon.ideasonboard.com>
 <YvUghWZbXIUofg5A@kroah.com>
 <YvmqL6Wz7o77ukF5@google.com>
 <YvnpVmnROTsWWw0o@kroah.com>
 <YvnrJBI8599+E43T@google.com>
 <YvnvnL9pBAgWMgTk@kroah.com>
 <YvnwtN1SwQjilJ97@google.com>
 <YvnybHVFmpUJs4qi@kroah.com>
 <YvyiLHBgRQ9XsTrW@paasikivi.fi.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <YvyiLHBgRQ9XsTrW@paasikivi.fi.intel.com>
Precedence: bulk

On (22/08/17 08:09), Sakari Ailus wrote:
> 
> Do note that USB webcams in Alder Lake laptops still work as usual, with
> the uvcvideo driver.

A massive +1 to this.

> This of course does not help the owners of such hardware but perhaps
> explains the current state of affairs a little. Eventually we will need a
> new kernel interface for this but at this point I can't tell whether it
> will be based on KCAM Sergey mentioned, or not.

We don't consider KCAM ready and this is why we have not published it
to the mailing list. We haven't really started with KCAM yet, but we
are about to do so. And I'm sure that we will find out a thing or two
missing or not working properly while we convert a real H/W driver to
KCAM. We will sit down and write some code to address those problems.