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 6808F36606B; Tue, 1 Sep 2026 07:43:56 +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=1788248640; cv=none; b=IDKtMJtATSgjRAvLk2udeNqiOYb/5UWpnuhMRN/9vjj5fzVSJx2XSZxamsPW01ajPwKffxpoVojSMNP2i8zTZFnWHOlhGOnLOaFEqIusy6zOteV4L+wjzBC7T1oPcwVC9dWFKVwkoALN5nmE32QLnlJHIYQeh3x/b1Vx4h0Q2BA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788248640; c=relaxed/simple; bh=23MEUiek+8f+VaOu4ez1Qqr+tEDb5JGFf45CrX9anlc=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=DgWboIjMj/Gwg9vleOHaZPmLyKHfrHoN8qsZPE+JEWyPPJoKJZH3V1fFZ7iS2L9bUCMuyA5zzM+0kHDAgZSd/NvSVaMi+xxEb5zOX1DOq3or1WHKslwgdIx9POJCXwhkYJh6XGaX+bbTouHXJXIH3YP9kG5v/r43ChtcCsKK52U= 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=fpChyKXU; 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="fpChyKXU" Received: from [192.168.88.20] (91-158-153-178.elisa-laajakaista.fi [91.158.153.178]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 7305A22B; Tue, 1 Sep 2026 09:42:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1788248538; bh=23MEUiek+8f+VaOu4ez1Qqr+tEDb5JGFf45CrX9anlc=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=fpChyKXUP4yuQGR9dVLhuBh8jiFCp8fj42Gvq6MeIeP/2SUVYU0Jq/HBWwOhHibnx 6qITDhowNTKXddkFVxpEEJSDzqO3VBvaoqrkDiBHYvtwxDc2srbypCSbxBmNdkRNYb 4bKhXEx4QT/xFMWLVGDkAqWQ5AKA6J3whoF3YFBI= Message-ID: <16626ec7-d1ec-4a54-ad1b-a59790cd33e8@ideasonboard.com> Date: Tue, 1 Sep 2026 10:43:44 +0300 Precedence: bulk X-Mailing-List: linux-media@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v16 00/22] media: i2c: add Maxim GMSL2/3 serializer and deserializer drivers To: Ceclan Dumitru , =?UTF-8?Q?Niklas_S=C3=B6derlund?= , dumitru.ceclan@analog.com Cc: Tomi Valkeinen , Mauro Carvalho Chehab , Sakari Ailus , Laurent Pinchart , Julien Massot , Rob Herring , Greg Kroah-Hartman , linux-media@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-staging@lists.linux.dev, linux-gpio@vger.kernel.org, Martin Hecht , Andrian Suciu , Cosmin Tanislav , Vivekananda Dayananda , Cory Keitz References: <20260831-gmsl2-3_serdes-v16-0-4fa6e08bb514@analog.com> <20260831170303.GB1116206@ragnatech.se> <65b703e7-e4a0-4046-9d35-7d0ff1057f96@gmail.com> From: Tomi Valkeinen Content-Language: en-US In-Reply-To: <65b703e7-e4a0-4046-9d35-7d0ff1057f96@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi, On 01/09/2026 10:39, Ceclan Dumitru wrote: > > > On 8/31/26 8:03 PM, Niklas Söderlund wrote: >> Hello, >> >> Thanks for your continued effort pushing this work forward! >> >> On 2026-08-31 16:21:19 +0300, Dumitru Ceclan via B4 Relay wrote: >>> This series adds new drivers for multiple Maxim GMSL2 and GMSL3 devices, >>> replacing the few GMSL2 drivers already in upstream, and introducing a >>> common framework that can be used to implement such GMSL chips, which >>> avoids code duplication while also adding support for previously >>> unsupported features. >>> >>> While the normally acceptable and polite way would be to extend the >>> current mainline drivers, the choice was made here to add a totally new >>> set of drivers. The current drivers support only a small subset of the >>> possible features, and only a few devices, so the end result after >>> extending them would in any case be essentially fully rewritten, new >>> drivers. >>> >>> This series depends on support for internal pads, for which a patch has >>> been added. >> >> It also depends on enabling the streams API right? At least I need to do >> so to be able to use the TPG. Out of curiosity do you know the plan to >> enable it by default upstream? >> > > I do not know when default enable is planned, but series could make it > so VIDEO_MAXIM_SERDES selection causes v4l2_subdev_enable_streams_api=1. > I am not sure that such a hack would be acceptable by Sakari or > upstream in general. I haven't tested with this driver, but in theory these kind of drivers should work with the Streams API still disabled. The Streams API is a uAPI, so the driver itself works without it. If the default routing for the drivers provides a sensible single route, one can use the drivers with a single camera. This is what the FPD-Link drivers do (although it's been a long time since I verified it with Streams API disabled). Tomi