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:   Thu, 11 Aug 2022 18:08:55 +0300
From:   Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     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>,
        Sakari Ailus <sakari.ailus@linux.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>,
        Sergey Senozhatsky <senozhatsky@chromium.org>,
        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
Subject: Re: Missing MIPI IPU6 camera driver for Intel Alder Lake laptops
Message-ID: <YvUbhx4HSxAAwIvv@pendragon.ideasonboard.com>
References: <52c87d91-422d-fca0-4dd5-bbaa559c81b6@molgen.mpg.de>
 <YvUKLbv/pOfbbeL+@pendragon.ideasonboard.com>
 <YvUaEDMbZD70x+hD@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <YvUaEDMbZD70x+hD@kroah.com>
Precedence: bulk

On Thu, Aug 11, 2022 at 05:02:40PM +0200, Greg KH wrote:
> On Thu, Aug 11, 2022 at 04:54:53PM +0300, Laurent Pinchart wrote:
> > For the time being, I agree with your recommendation to not buy these
> > devices if you care about camera support.
> 
> I second this, don't buy these devices if the vendor is not willing to
> get their drivers upstreamed properly.

"Not willing" may be a bit too harsh here. I wouldn't just blame Intel
for not upstreaming a driver if it turns out that the V4L2 API isn't a
good match and we have no proposal to provide an alternative.

This being said, I agree it's the vendor's responsibility to at least
engage with the upstream community to find a solution, and collaborate
on the implementation. I'm sure there have been way more private
discussions than I'm aware of, maybe now is the right time to extend
this to a wider audience and create a realistic plan on how to move
forward. You all know my e-mail address :-)

-- 
Regards,

Laurent Pinchart