From patchwork Thu Nov 12 14:28:12 2026 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Emfox Zhou X-Patchwork-Id: 28883 Return-Path: X-Original-To: parsemail@patchwork.libcamera.org Delivered-To: parsemail@patchwork.libcamera.org Received: from lancelot.ideasonboard.com (lancelot.ideasonboard.com [92.243.16.209]) by patchwork.libcamera.org (Postfix) with ESMTPS id 11301C3304 for ; Thu, 12 Nov 2026 14:38:53 +0000 (UTC) Received: from lancelot.ideasonboard.com (localhost [IPv6:::1]) by lancelot.ideasonboard.com (Postfix) with ESMTP id 39F3C6A7C4; Thu, 12 Nov 2026 15:38:52 +0100 (CET) Authentication-Results: lancelot.ideasonboard.com; dkim=pass (2048-bit key; unprotected) header.d=debian.org header.i=@debian.org header.b="FN9sGYIE"; dkim-atps=neutral Received: from stravinsky.debian.org (stravinsky.debian.org [IPv6:2001:41b8:202:deb::311:108]) by lancelot.ideasonboard.com (Postfix) with ESMTPS id A502B691CE for ; Thu, 12 Nov 2026 15:28:20 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:MIME-Version:Content-Transfer-Encoding :Content-Type:Cc:To:Message-ID:Date:Subject:From:Reply-To:Content-ID: Content-Description:In-Reply-To:References; bh=AJtF+wc5G5v46SLqLpmaRO010TCMvjdlnQnOozWa6VY=; b=FN9sGYIE+DU9ytVv+xTs9spokX cTIoua+jun0BPNvDoyp0PpCxYZxSpotsyiwYQrqHK+njyH3F3ZstBCgt9hBXnCnR5ZxITdZ+hX0aq n67qJye0dw0ZGM8sW762coNRZ5VqEmG5gCO5XQf0W8JUyY6VTG1xelNK7dqt8XWyKwen58z4ppQK2 Yc5uZoINdV+p5itUOqXKFMsZ/385VBhC2NZ9MMdpZQIlK0bFj75cpaVU0GROM/q1lL/3diDUqgBmJ SrIQOBfPmw3xI9uz89BFHHEeyYCWBhGoDLZzADxeJoI0pJKsiuxta7dTlCkE7EwUyxuHQpWrYkMcO VnmbP+Sg==; Received: from authenticated-user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from ) id 1xRVmk-00E2CX-1I; Thu, 12 Nov 2026 14:28:19 +0000 From: Emfox Zhou Subject: [PATCH 0/1] ipa: softisp: Add tuning data for the Surface Pro 8 cameras Date: Thu, 12 Nov 2026 22:28:12 +0800 Message-ID: <179449369268.366128.18140816117565550812@debian.org> To: libcamera-devel@lists.libcamera.org Cc: Kieran Bingham , Laurent Pinchart , Sergey Lebedev MIME-Version: 1.0 X-Debian-User: emfox X-Mailman-Approved-At: Thu, 12 Nov 2026 15:38:51 +0100 X-BeenThere: libcamera-devel@lists.libcamera.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libcamera-devel-bounces@lists.libcamera.org Sender: "libcamera-devel" Two tuning files for the two cameras of the Surface Pro 8, the ov13858 at the back and the ov5693 in front. Both already work with the software ISP, but with no tuning file they fall back to uncalibrated.yaml and the colour is visibly green. This follows the September thread where Kieran said per-sensor tuning is wanted, and that the licensing of matrices read out of a vendor blob is not settled. The gains and matrices here come from the AIQB that ships with the Windows driver of this machine; the black level is measured. The provenance is stated in the commit message rather than the numbers being presented as mine, so the decision stays with the maintainers. One question this series runs into: the tuning file is looked up by sensor model, and the ov13858 is also the rear camera of the Surface Pro 11, where Sergey has a file from a different module. Two modules, one name. Do you want a per-module scheme, and if so what should the file be called, or should one module be picked as representative for the sensor? Emfox