From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from perceval.ideasonboard.com (perceval.ideasonboard.com [213.167.242.64]) (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 CDAFF3081C3 for ; Wed, 3 Sep 2025 13:41:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.167.242.64 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756906865; cv=none; b=GlrXYtAuC550tXAT7ShzQRxrVD+BGgL1b0nGSPy/vMGQnZfrfxBc4sBu/HdbSHzQCySky+38aPb0qdomNl2lBbKlRISbyT+kxlC7klMRUi964eS99ObfvquV2W872RJrZVHNMYYVJFnqYW8IR1WSRaZZKg7nExnwyeOiZ107t9Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756906865; c=relaxed/simple; bh=K/9dAyFF/P+rSML/+SeNcZwvlUM5MmpiClNT/7DQIXQ=; h=Content-Type:MIME-Version:In-Reply-To:References:Subject:From:Cc: To:Date:Message-ID; b=J+6lreAOVR5OOB2JAQofP1npmCa9pFW4PplkgKI2hadyuWy020qquMP1W3asJaB6yb9DvS15BJbmH7Ch21RKXq0y186InLZmbf22u7OkVluifQ/C7temO4pJcyRwCEjF+jnUPOa/3JBzIgJdwHaWZMMbj434t5xqbkDE1oTsUb8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=ideasonboard.com; spf=pass smtp.mailfrom=ideasonboard.com; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b=N0tq5TFE; arc=none smtp.client-ip=213.167.242.64 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=ideasonboard.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ideasonboard.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b="N0tq5TFE" Received: from mail.ideasonboard.com (unknown [IPv6:2401:4900:1c69:480e:e039:1d0b:c5ff:a9e2]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 33B7D83D; Wed, 3 Sep 2025 15:39:52 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1756906792; bh=K/9dAyFF/P+rSML/+SeNcZwvlUM5MmpiClNT/7DQIXQ=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=N0tq5TFEyFNEPAEWuQykFLtPtYKWwkIk7GdD6zDzio5OcB4Q61rd9DzuNVntZGLCm saS90oxafBg89QQmQ7ldOuP1fPOj99B68c5gIKWAx8fdaIT0O9rl4P1HvhWBqKxo1A qJtFV01IqAFswxeh6z1HOBHiL38eALSBaFLczvC4= Content-Type: text/plain; charset="utf-8" Precedence: bulk X-Mailing-List: linux-staging@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <731ead88-8dc9-4032-86f5-7a2dd5044b22@gmx.net> References: <20250827-vchiq-destage-v1-0-5052a0d81c42@ideasonboard.com> <20250827-vchiq-destage-v1-4-5052a0d81c42@ideasonboard.com> <731ead88-8dc9-4032-86f5-7a2dd5044b22@gmx.net> Subject: Re: [PATCH 4/5] media: staging: Drop bcm2835-camera driver From: Jai Luthra Cc: linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org, kernel-list@raspberrypi.com, Dave Stevenson , Laurent Pinchart To: Broadcom internal kernel review list , Florian Fainelli , Greg Kroah-Hartman , Ray Jui , Scott Branden , Stefan Wahren Date: Wed, 03 Sep 2025 19:10:55 +0530 Message-ID: <175690685574.8095.13306600513284108529@freya> User-Agent: alot/0.12.dev28+gd2c823fe Hi Stefan, Quoting Stefan Wahren (2025-08-28 00:48:22) > Hi Jai, >=20 > Am 27.08.25 um 08:24 schrieb Jai Luthra: > > The bcm2835-camera driver is replaced by the V4L2 bcm2835-unicam driver > > that is already upstream. So drop it from staging. > AFAIK the old Raspberry Pi Camera V1 isn't supported by V4L2=20 > bcm2835-unicam. Personally i'm fine with this, but this must be clear in = > the commit message.Did you already talked to distributions like Redhat & = > OpenSuSE about this step? As Dave mentioned, the OV5647 should work with V4L2. I don't have a sensor with me, but I can order one and try to get it working with the upstream kernel separate from this series. I did test the V2 camera module (IMX219) with my series applied on top of upstream kernel, and capture worked fine with bcm2835-unicam, so I don't believe V1 camera module should be an issue. > > This also simplifies destaging of VCHIQ MMAL, by reducing the users of > > the MMAL API (this driver is one of them). > AFAIU this drops the only one user of VCHIQ MMAL. So please explain, why = > we still need this API and how this should be tested? The bcm2835-isp and bcm2835-codec are other users, which are currently only present in the downstream Pi kernel [1]. I plan to upstream the ISP driver as a subsequent series (that was the main motivation for this series), thus keeping the MMAL API still here. [1] https://github.com/search?q=3Drepo%3Araspberrypi%2Flinux%20%23include%2= 0%22..%2Fvchiq-mmal%2F&type=3Dcode >=20 > Best regards Thanks, Jai