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 62378201017; Thu, 26 Jun 2025 12:42:50 +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=1750941772; cv=none; b=qVG49866NjakCfNk1lCrK+V0pMZ0eryEOW+OYzQkNP5W2LYbOKMZtQ0NgrP12zVCrnQoAB8zQZpvwbUseoEU7g4KxXK0J0x0FkoIwNrs1pi5D89xK7rnT3U3KGWlPOBR05v/+2pCir6X46BpPQXF4nba6X6E/n/4THAqyl+jTHI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750941772; c=relaxed/simple; bh=/a+MiBN3U4KcgRah2otQEl2ZAfbGFptjDWZeI5tiwVM=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=YCNbCtnITuDTFsP9j0GQYoQuWfk7qTu6TQzAJaV44Ht2Vplcy1mpIShlACmUxFt5DqYIaSv0qH/xDxM8uhEP/01hs4IGkXko0M2w09kG9yS3qzQpZpj6yt5bZU84AdlU0YBVUJnjhwo9zOO7EU3xMp9apKHY1EFSMoRiBntHJZQ= 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=Bq4Wvv7+; 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="Bq4Wvv7+" Received: from pendragon.ideasonboard.com (85-76-34-12-nat.elisa-mobile.fi [85.76.34.12]) by perceval.ideasonboard.com (Postfix) with UTF8SMTPSA id 132F13D5; Thu, 26 Jun 2025 14:42:29 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1750941750; bh=/a+MiBN3U4KcgRah2otQEl2ZAfbGFptjDWZeI5tiwVM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Bq4Wvv7+34jFLzYlwax7THsGzi1+IcvoqEvmMityKXbu1cRceUKUfyPc9xLPq6Yg1 5e7lBeQMd1mjDDUf7CAbCWM6vKjjRSCnysXhkVZNSJHFXG8dQxWTAF/53UWhBurTCL nwcJ1NV6NnTQjYrHmqVW+4izlymLQFc3gg4w9n5c= Date: Thu, 26 Jun 2025 15:42:24 +0300 From: Laurent Pinchart To: Frank Li Cc: Mauro Carvalho Chehab , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Kumar M , linux-media@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, imx@lists.linux.dev, "Guoniu.zhou" , Stefan Hladnik , Florian Rebaudo Subject: Re: [PATCH v3 2/2] media: i2c: Add ON Semiconductor AP1302 ISP driver Message-ID: <20250626124224.GK8738@pendragon.ideasonboard.com> References: <20250623-ap1302-v3-0-c9ca5b791494@nxp.com> <20250623-ap1302-v3-2-c9ca5b791494@nxp.com> <20250623224701.GE15951@pendragon.ideasonboard.com> <20250624185643.GE20757@pendragon.ideasonboard.com> Precedence: bulk X-Mailing-List: linux-media@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: On Tue, Jun 24, 2025 at 03:18:42PM -0400, Frank Li wrote: > On Tue, Jun 24, 2025 at 09:56:43PM +0300, Laurent Pinchart wrote: > > On Tue, Jun 24, 2025 at 02:47:10PM -0400, Frank Li wrote: > > > On Tue, Jun 24, 2025 at 01:47:01AM +0300, Laurent Pinchart wrote: > > > > On Mon, Jun 23, 2025 at 03:17:38PM -0400, Frank Li wrote: > > > > > From: Anil Kumar Mamidala > > > > > > > > > > The AP1302 is a standalone ISP for ON Semiconductor sensors. > > > > > AP1302 ISP supports single and dual sensor inputs. The driver > > > > > code supports AR1335, AR0144 and AR0330 sensors with single and > > > > > dual mode by loading the corresponding firmware. > > > > > > > > > > Signed-off-by: Anil Kumar Mamidala > > > > > Signed-off-by: Laurent Pinchart > > > > > Signed-off-by: Stefan Hladnik > > > > > Signed-off-by: Florian Rebaudo > > > > > Signed-off-by: Frank Li > > > > > --- > > > > > Change in v3: > > > > > - add extra empty line between difference register define > > > > > - add bits.h > > > > > - use GEN_MASK and align regiser bit define from 31 to 0. > > > > > - add ap1302_sensor_supply > > > > > - add enable gpio > > > > > - update firmware header format > > > > > > > > One of the main issues with this driver is that we need to standardize > > > > the header format. The standardized format will need to be approved by > > > > onsemi as we will need to provide not just a driver, but also a > > > > toolchain that will produce firmwares in the right format. Furthermore, > > > > some time ago the AP1302 firmware was extended with the ability to > > > > dynamically compute PLL parameters IIRC. This needs to be taken into > > > > account. > > > > > > It is quite common when work with firmwares. Generally, it need version > > > information at header. > > > > > > The driver need check firmware's API version, if miss match or incompatible, > > > just return and report error. > > > > > > we can't assume firmware always align driver code because many user just > > > update kernel without update rootfs or firmware package. > > > > Sure, but that's not the point. The point is that there are multiple > > out-of-tree ap1302 driver versions, developed or adapted by different > > SoC vendors. Those variants use firmware files produced by those SoC > > vendors, and they not standard. > > I am not sure if firwmare is open source. Most like not. The firmware is not open-source, but I don't think that's relevant. > We need create > difference compatible string for difference Soc vendor. No, that we must absolutely not do :-) If it's the same AP1302 and same camera sensor, we must not have different compatible strings when the AP1302 is connected to an NXP SoC or a MediaTek SoC. > > We need to standardize on a firmware > > format to upstream a driver, and that standardization needs to involve > > the device manufacturer. > > we need workable version (easy extend) firstly, when let other vendor follow. > > Frank Li > > > > > > I want to resuscitate this driver and get it merged. There's more work > > > > to do, in collaboration with onsemi, and I haven't had time to tackle > > > > it. If you want to propose a proper design for firmware handling I would > > > > be happy to participate in the discussion. > > > > > > who is onsemi contact windows. > > > > > > > > - update raw sensor supply delay time > > > > > - use gpiod_set_value_cansleep() insteand gpiod_set_value() > > > > > - update use latest v4l2 api > > > > > - use ctrl_to_sd() helper function > > > > > - add ap1302_g_volatile_ctrl() > > > > > - remove ap1302_get_fmt() > > > > > - use guard for mutex. > > > > > - use dev_err_probe > > > > > - use devm_add_action_or_reset to simple error handle at probe. > > > > > - use read_poll_timeout() simple dma idle polling. > > > > > > > > > > previous upstream: > > > > > https://lore.kernel.org/linux-media/1631091372-16191-1-git-send-email-anil.mamidala@xilinx.com/ > > > > > --- > > > > > MAINTAINERS | 1 + > > > > > drivers/media/i2c/Kconfig | 9 + > > > > > drivers/media/i2c/Makefile | 1 + > > > > > drivers/media/i2c/ap1302.c | 2838 ++++++++++++++++++++++++++++++++++++++++++++ > > > > > 4 files changed, 2849 insertions(+) > > > > > > > > [snip] -- Regards, Laurent Pinchart