From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.11]) (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 CFF69342523 for ; Thu, 9 Apr 2026 20:15:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775765733; cv=none; b=FhHEMCBXdvh8SWn2ckkzHzmg/urW7kqhSoUYXIQZC81dKmnflnq7z3iHzEI/A7NmpI9pNJRfkre4T0m6nGLzdqXZWRBcIzmhGjrR7wTcV9Favm7Sqo3IBEn9R4NDFezZTQw2JUf+Jk45EEt2W6ex9P6jy0Bn8G/BIoNSpsFyRLg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775765733; c=relaxed/simple; bh=L5c4oIUvm/3JzV3/sSGK5EH65oBbXnEfhkEglXcvHtI=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=BjXXzaUvk4k69eVbufSkv4/0NcTiP/MaTer9I0MHIOMHBGPm0JcvUAiaU9ZanpLLjpTyADoLgEreDzD7g9r+bE2zAEMRBpguivKSGeAmTVNB90xvRjWtX/Zd3C6QDjev1raIzKVHeFWJugn5Uy1MZ2RODuFj8CXSyKeg2/d+8+w= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=QSgXxPog; arc=none smtp.client-ip=192.198.163.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="QSgXxPog" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1775765732; x=1807301732; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=L5c4oIUvm/3JzV3/sSGK5EH65oBbXnEfhkEglXcvHtI=; b=QSgXxPogQGbaPdTSQeUQN685Gyfv88ehDf8u5eEb5jDiDy7SAdmn1Odp LcOUVrfTXg/k8wD3cPXB0TIwq+IyMTv2BmWAA4UH+wUkjHXYzCESmFvuA zyXStm72/6JkSf38DYsGKCzl1mVsLrsPqcXahKIdKjcuj+e7J/bpqwu48 qKO+uO9ZF+SqriM5ecev3ri/hC75kJpr5IiNVJkuz9ClkF2J36h8w6xyL MuNYDj63aSWeOvzgYiwA+8togkWgc6jHNKeY5rhXsN+KHp+F3J4ewl5lL YvdEY7a3X3AmTgo4a0hgkkRTg8PA3qAF3R/YitAhP0sGmsdX1OGubjki/ g==; X-CSE-ConnectionGUID: ZfKTd9N/T4CnIrHMnP2zGQ== X-CSE-MsgGUID: xkgjYYS7RSeSUan9hW68lQ== X-IronPort-AV: E=McAfee;i="6800,10657,11754"; a="87409098" X-IronPort-AV: E=Sophos;i="6.23,170,1770624000"; d="scan'208";a="87409098" Received: from fmviesa003.fm.intel.com ([10.60.135.143]) by fmvoesa105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Apr 2026 13:15:18 -0700 X-CSE-ConnectionGUID: NMGV9NNfSGGK0/rXSfbXeQ== X-CSE-MsgGUID: ejuaIKMIRkCZRASV3/xUvA== X-ExtLoop1: 1 Received: from dalessan-mobl3.ger.corp.intel.com (HELO kekkonen.fi.intel.com) ([10.245.244.29]) by fmviesa003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Apr 2026 13:15:11 -0700 Received: from punajuuri.localdomain (unknown [192.168.240.130]) by kekkonen.fi.intel.com (Postfix) with ESMTP id 5E1BB1226B0; Thu, 09 Apr 2026 23:15:13 +0300 (EEST) Received: from sailus by punajuuri.localdomain with local (Exim 4.98.2) (envelope-from ) id 1wAvmH-000000045lZ-3Qy0; Thu, 09 Apr 2026 23:15:01 +0300 Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo From: Sakari Ailus To: linux-media@vger.kernel.org Cc: hans@jjverkuil.nl, laurent.pinchart@ideasonboard.com, Prabhakar , Kate Hsuan , Dave Stevenson , Tommaso Merciai , Benjamin Mugnier , Sylvain Petinot , Christophe JAILLET , Julien Massot , Naushir Patuck , Stefan Klug , Mirela Rabulea , =?UTF-8?q?Andr=C3=A9=20Apitzsch?= , Heimir Thor Sverrisson , Kieran Bingham , Mehdi Djait , Ricardo Ribalda Delgado , Hans de Goede , Jacopo Mondi , Tomi Valkeinen , David Plowman , "Yu, Ong Hock" , "Ng, Khai Wen" , Jai Luthra , Rishikesh Donadkar Subject: [PATCH v12 14/86] media: Documentation: Document embedded data guidelines for camera sensors Date: Thu, 9 Apr 2026 23:13:49 +0300 Message-ID: <20260409201501.975242-15-sakari.ailus@linux.intel.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260409201501.975242-1-sakari.ailus@linux.intel.com> References: <20260409201501.975242-1-sakari.ailus@linux.intel.com> Precedence: bulk X-Mailing-List: linux-media@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Document how embedded data support should be implemented for camera sensors, and when and how CCS embedded data layout should be referenced. Signed-off-by: Sakari Ailus Reviewed-by: Julien Massot Reviewed-by: Jacopo Mondi --- .../media/drivers/camera-sensor.rst | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/Documentation/userspace-api/media/drivers/camera-sensor.rst b/Documentation/userspace-api/media/drivers/camera-sensor.rst index 75d783b75c48..87f86a2f6cc5 100644 --- a/Documentation/userspace-api/media/drivers/camera-sensor.rst +++ b/Documentation/userspace-api/media/drivers/camera-sensor.rst @@ -117,3 +117,22 @@ register programming sequences shall initialize the :ref:`V4L2_CID_HFLIP values programmed by the register sequences. The default values of these controls shall be 0 (disabled). Especially these controls shall not be inverted, independently of the sensor's mounting rotation. + +Embedded data +------------- + +Many sensors, mostly raw sensors, support embedded data which is used to convey +the sensor configuration for the captured frame back to the host. While CSI-2 is +the most common data interface used by such sensors, embedded data can be +available on other interfaces as well. + +Embedded data support is indicated by the presence of an internal sink pad (pad +that has both the :ref:`MEDIA_PAD_FL_SINK ` and +:ref:`MEDIA_PAD_FL_INTERNAL ` flags set) with a metadata +format to model the embedded data stream. If the sub-device driver supports +disabling embedded data, this can be done by disabling the embedded data route +via the ``VIDIOC_SUBDEV_S_ROUTING`` IOCTL. + +In general, changing the embedded data layout from the driver-configured values +is not supported. The width of the metadata is device-specific and equal to or +less than the width of the image data, as configured on the pixel data stream. -- 2.47.3