From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DFAE83A8FEB for ; Tue, 3 Feb 2026 14:19:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=205.220.168.131 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770128363; cv=none; b=mJVnf82UQ7JcmLiEJbcQrT1CVYLsiHDTly6bCehJiXFn4xd8KyVSUo0YRVyZPWjDLmkxDdzVSSZU/Z4kS63t3EDHEveAwkn27FOF9SarR+PH+U8PPKk9XyvDt5/jhT0l7p0lgVxZWcqzseEfJyscP7xyWKQubcTgTgF/uw4xFks= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770128363; c=relaxed/simple; bh=rAaF3IJyKMtMVHi4hbNf4T+7dOMjju3GOZeNCYpnCZo=; h=Message-ID:Date:MIME-Version:From:Subject:To:Cc:References: In-Reply-To:Content-Type; b=VtR8vggAOryscQIrP7m5EyUgs01vXzbS8zq7qhn5jvYoRO1Oe6gzcvjMo1F39ZT9xwTwiSy6iopwcjIOTcdrr6RG7SZa4+7Qh+ZxmpsnF+1/ywab9NGMaJwMsHgFfUvDTUyjOi9BqlC185j6DtBjnO40tpiNywUZaJKK7Nq34UQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com; spf=pass smtp.mailfrom=oss.qualcomm.com; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b=BjSf/ZFF; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b=EN+P8f0t; arc=none smtp.client-ip=205.220.168.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b="BjSf/ZFF"; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b="EN+P8f0t" Received: from pps.filterd (m0279864.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 613E1xH8256051 for ; Tue, 3 Feb 2026 14:19:17 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qualcomm.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=qcppdkim1; bh= 4rfFv6kfMbhro4k4r2I8vRYN/RWIM5KJYEpa411uDzw=; b=BjSf/ZFFaQoN/MaL rkMc3PW7aZa26VNkzmqPIqpcLLUqRSeSkd/3haNJG5KrxPq35WCki20FR3odWoNe L//mTObl9Rk5U6ImSSrlgiH97pVGBmGbhNH8rIsAPgJqXvhfRe8NgRkarRLjI/7f jn6Cp0T/Jlm7n3NkeZoxgBJ6y6KhSmQyJefZy9fitnadddwAw6rqWBzhXOG41anl qzvZ5ZeLlbPP9/xQ4W+Tx1BWoHCXIFhuvoOExb9zfxriJ/r8+4P5M70h9JUoRPTt RBCQ+jVh4WVXR7Lgp/KiRSTh3ZhRym+a0suk3sggLQvWHyb3LZ0se+8AvsXMN5ND Qfdv3w== Received: from mail-qk1-f197.google.com (mail-qk1-f197.google.com [209.85.222.197]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 4c2v0kmbcn-1 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Tue, 03 Feb 2026 14:19:17 +0000 (GMT) Received: by mail-qk1-f197.google.com with SMTP id af79cd13be357-8c71500f274so581473985a.1 for ; Tue, 03 Feb 2026 06:19:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oss.qualcomm.com; s=google; t=1770128356; x=1770733156; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:subject:from:user-agent:mime-version:date:message-id:from:to :cc:subject:date:message-id:reply-to; bh=4rfFv6kfMbhro4k4r2I8vRYN/RWIM5KJYEpa411uDzw=; b=EN+P8f0tTI+bZH8vkRBQYonu0Jig1CFyNqtnCN6A8vcDwNeKzTcKpB40w7fJtyyfVy SziHocqsHncSocE118r3vdUokKRx/ITHY0pTrofnkb6W+hrmf1h5nkMnlo2+rfh3nMej IDST+wuW1jtAH8KdZWttfKDO2Wd6SUNVAnF01rI7MCaTx1hu+8LeOJMFTYgNl/1PFRMz 5j4T/aT8hTSw/4yBn+otB95d2pdTyDwFPydiESMBk6VuIp5MIuUnYxx9xKjsdt8aV43x UUoSdyy/XYj+IJN3Ky09qWOc0jvUK5Vo/0FBpbqkY76S3gP22pcjamCdWDsEKr0u8cGQ 9rbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770128356; x=1770733156; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:subject:from:user-agent:mime-version:date:message-id:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=4rfFv6kfMbhro4k4r2I8vRYN/RWIM5KJYEpa411uDzw=; b=t6PBGRtqr56p3LyPAxpzwQt6R21YxgvT2N90zhx54CXSMQ6+BGt+k1nPUvDD3NNvDx xENa3tFXw5UMX5FZCyp07BzRYpFDc8MiSbFdtPdFtH3W2r/a03+/ioSsYcYvTfXLstjZ b+ZRWx1P92mliEInvgMEF7lxHPEpetYJ8FT0aJnuvmiampN9w7wCSn9emXBkecw/zfvh EBmVvwc6mSpYpacsOdpWU3iZXyKYo9JkjlouuAMQq0VdszHWlBQkZ/ZpJYLQ8tye2FcX m+xxPfnB1I8jWUATK+9drbpJZM/H1Ic7xSFuaAYQpsMd8nFFLf6dP7wDytoxh1tkkhCL ISQQ== X-Forwarded-Encrypted: i=1; AJvYcCU9pnKJlZw9aOix+j1qmqdt1zxvUzjvbmaWYMGoMxgRZsctht3thF/5jKSudjhq1y6c4zXMmR2NXEXkD2CroUA=@vger.kernel.org X-Gm-Message-State: AOJu0Yw4s5En2deYZ/q156Sx1ULcbwsUxNuQ8VxGUkrs3KJ8g80xIILU 1qY9ka3bMCnuKOvu5Fb7wZCndP1+a5RFwYAUeq1vvwCUUzvnjrJoORv9z8z31az7Kp2T6o8hUQf dLs/E0ddD9RnWA7mYz01WvvHsyx1rGp1lLFwQloGoBm5FKAYogC5ipZ+oyueWDtqqZoquDHM= X-Gm-Gg: AZuq6aJpz5uib0klyYvC3Tc8E0Fn29WU0D15OkjwnZVa7g+a76+jrQcqp7YWZVNgj3j 8aL89nA2uc3vyk8cwHnmNUjIibu9npDy9ZMla+RUd2dtsEB3+YxiGc1tPqj0KojSQr7Dif+T0lD gpNaRMvGPtwHgl8JrVyZRWyv/D3zTkhVApE4Snh4UXLfs1f0WPRcSudXeFio2/7Cvq3yDF96Z7a 96kXcsh9B3XG6SSmxjSru6a5VXjf35Rw7wpNpqY5P5+2CUQJpYxaYGLFRpntSfSOKAKXY6mQ5kT 7W3kGd27xrga2LRnhvWJEcIiMpebV2B2L/utWEHSDUhaGJ+uEtcgOVBhmlGns3LCbTFBt2x/yAJ rhBv1lJ1Ha9XKN+cpYU6tXH5E4BvyAxmp60L1NRt7pSrYlhPf1OJ7Z/7ddeyhz6aG5II7K7RRq/ UP8ra2iHSJED3qX9sfqQ3MaCXnWJVK+rsBJo3MP+jqy8Ve7fy99QRsiE4uTJcRgjbnbQklYEfGG /Js X-Received: by 2002:a05:620a:bd5:b0:8c5:1fd2:e9ef with SMTP id af79cd13be357-8c9eb27018amr1905936185a.28.1770128355936; Tue, 03 Feb 2026 06:19:15 -0800 (PST) X-Received: by 2002:a05:620a:bd5:b0:8c5:1fd2:e9ef with SMTP id af79cd13be357-8c9eb27018amr1905930185a.28.1770128355359; Tue, 03 Feb 2026 06:19:15 -0800 (PST) Received: from ?IPV6:2001:1c00:c32:7800:5bfa:a036:83f0:f9ec? (2001-1c00-0c32-7800-5bfa-a036-83f0-f9ec.cable.dynamic.v6.ziggo.nl. [2001:1c00:c32:7800:5bfa:a036:83f0:f9ec]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-b8dbf1847f9sm1064954166b.42.2026.02.03.06.19.13 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 03 Feb 2026 06:19:14 -0800 (PST) Message-ID: Date: Tue, 3 Feb 2026 15:19:13 +0100 Precedence: bulk X-Mailing-List: linux-integrity@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: johannes.goede@oss.qualcomm.com Subject: Re: [RFC PATCH v2] media: Virtual camera driver To: Jani Nikula , Jarkko Sakkinen , linux-media@vger.kernel.org Cc: anisse@astier.eu, oleksandr@natalenko.name, linux-integrity@vger.kernel.org, Mauro Carvalho Chehab , Hans Verkuil , Laurent Pinchart , Sakari Ailus , Jacopo Mondi , Ricardo Ribalda , open list References: <20260202204425.2614054-1-jarkko@kernel.org> <6b192c71-c389-4a6e-b7c3-ddcd5cc4aa34@oss.qualcomm.com> <37a0d91c2e78c97f3d956444c4f7a2a2fca9ae06@intel.com> Content-Language: en-US, nl In-Reply-To: <37a0d91c2e78c97f3d956444c4f7a2a2fca9ae06@intel.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Authority-Analysis: v=2.4 cv=Reqdyltv c=1 sm=1 tr=0 ts=698203e5 cx=c_pps a=50t2pK5VMbmlHzFWWp8p/g==:117 a=xqWC_Br6kY4A:10 a=IkcTkHD0fZMA:10 a=HzLeVaNsDn8A:10 a=s4-Qcg_JpJYA:10 a=VkNPw1HP01LnGYTKEx00:22 a=NEAV23lmAAAA:8 a=EUspDBNiAAAA:8 a=E8RJ7uGaLTfD5B8v_isA:9 a=QEXdDO2ut3YA:10 a=IoWCM6iH3mJn3m4BftBB:22 X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwMjAzMDExNCBTYWx0ZWRfX68vwXbDIcr3A pdmowXP5FVaFeLVz/WeO70JlZeafoKkuQFodpRUz0kQUHdJ+w59MctBvgAg9sp29pdeDyLSUcT9 cDv3Gbl6y4hIXJAjRDxdVaOXPt8Ks/wkFBdMeyVZEPY9AhFlnjShnq4I+c29QXIAvPLm+qkVxrL abx23iM82ftbCT3OjUCd+Rhatc5NWxrdWMAviw8bkSs9Mgc1KdWBQXO5PP88Mn1YmUPoUnsaOS5 Au6ttWTU+ZKw1imtgJQpGYqi6GwtYi0gqkFGuTy7vJM7MxT5f3iBngR765WIV7Yi4w4La7wiPYM pE3sgbakz3RJlg9M1A/q4yT2zYZMfjMXwUbGV2b5tH2Seh9L2e+B+2XFt/sDUJCi4/Ho4r1Jxco X54T/rpvZ9r/pHvsFT3iF+5zRXVTJwK/dcT0BJiKvWOHdkgMmulQFlgrrDRlvytTa9fvr+FpdyN exYz0ZJyUOUoJXhdI2w== X-Proofpoint-GUID: m3NnNwlCfA63p5tN4ajA5PQBdGO9oGMw X-Proofpoint-ORIG-GUID: m3NnNwlCfA63p5tN4ajA5PQBdGO9oGMw X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.51,FMLib:17.12.100.49 definitions=2026-02-03_04,2026-02-02_01,2025-10-01_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 spamscore=0 suspectscore=0 adultscore=0 lowpriorityscore=0 clxscore=1015 phishscore=0 impostorscore=0 malwarescore=0 bulkscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2601150000 definitions=main-2602030114 Hi Jani, On 3-Feb-26 14:20, Jani Nikula wrote: > On Tue, 03 Feb 2026, johannes.goede@oss.qualcomm.com wrote: >> The problem is that what you're suggesting is basically a much >> improved (using dma-buf is way better) v4l2-loopback driver and >> v4l2-loopback has been blocked from getting merged into the kernel >> because besides the mobile-phone camera use, the other main use-case >> is to allow running proprietary camera stacks like Intel's proprietary >> camerastack and then presenting that to userspace as a standard v4l2 >> cam so that userspace apps will just work. > > ... > >> The community concensus is that the solution here is for apps to >> access cameras through pipewire. Together with the shift of laptops >> cameras from UVC to "raw" MIPI cameras there also is a shift to >> running applications sandboxed as flatpacks because of the changing >> "cyber" security landscape. This is why pipewire was chosen because >> it also solves the accessing cameras from a sandbox issue. > > Why is v4l2-loopback problematic from the perspective of facilitating > running proprietary camera stacks, but pipewire isn't? Once pipewire mostly works everywhere for camera access then indeed this will allow proprietary stacks to present themselves as a pipewire src. For now though most proprietary stacks seem to prefer v4l2loopback because pipewire is not supported as camera source yet by a lot of apps. As I indicated in my original email personally I'm a bit divided on whether a virtual camera driver should be kept out of the kernel to not promote proprietary userspace stacks, but this is not my call. OTHO evdi: https://github.com/DisplayLink/evdi has been kept out of the kernel for pretty much the same reasons by the drm/kms folks. At least AFAIK there still is no way to present virtual kms capable display outputs backed by userspace in the kernel. I completely understand where you're coming from wrt v4l2-loopback support (or something equivalent) but asking for this really is the same as asking for the evdi driver to get merged, which AFAIK has been blocked for the reason of avoiding proprietary userspace display output drivers (I guess there might be technical reasons too). Regards, Hans