From patchwork Sun Jan 19 14:38:55 2025 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Sakari Ailus X-Patchwork-Id: 13944476 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.17]) (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 176751C68A6 for ; Sun, 19 Jan 2025 14:39:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.17 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737297561; cv=none; b=KN47n5Yn0fPAqGsDFKArWtRaJqab1wjZyKkpA2WMIZgJcL+y+EoDG4zAa/XaTW3LhpddyIPoQFBO28fuIe54ppiv7RkN/naIwJBd3Y/UtkpBdGNhGZfiQE4n6UZn7L0OM6OA0Dqxr5D6Txzmtmu3686liDXDd+a3lT4A+wMwVKU= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737297561; c=relaxed/simple; bh=yLazcRgU+7Ai6aEnad47gl7ttRJcAgLl/+5EXDlaXVY=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=D+15B9/7nPLm5gcnvQtLICcTHb4dRswyIlzhF1VP2k0DXWz7bRm+x3xc2VdZ52e6OSFNBk/h4WUvfCz3yEx2u8ss4w94y6daOBFxBE4XoBZ5LJ98qKf9DXTy5brkyuFHY1H5Xkh8DItRp60EMwwAguMzwpFxZTfKceTOR50EI8o= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=none smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=RhdUN9SN; arc=none smtp.client-ip=192.198.163.17 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=none 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="RhdUN9SN" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1737297560; x=1768833560; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=yLazcRgU+7Ai6aEnad47gl7ttRJcAgLl/+5EXDlaXVY=; b=RhdUN9SNMChw7zsi87dARGUmsEz0GSjWA34/vyoYV4LeM5uj7c3N9dr1 Havs2k8QVnTR+LJeH7UjRB3/fpJWueNLVfKKa0Nr7itBAS1bNpOhPXmOd tSrCPzK2Xl36TJjGIzqrT6npu7JNserIyWE2vPoRQr7nwZ/cYleD/NO+E +ReIZzgBKs4AUm7Pe7D4iomZ0NQUGunHO3bLpR7JqVMJMMeHwNx4y98oO 0IBIAgd8+dDOOTp7HpqfTInwAQ6A4tMDoOeZHAIy4Ks+BvzOF8b5ZB68U /X26QVsuABVYnE3voXzQonuV4gTTKYU1BWKIAgPCEE2DtDm/bkEiON5MZ g==; X-CSE-ConnectionGUID: lpcKe2HDSAa9KV9fKrmdzg== X-CSE-MsgGUID: mRgWhhw2RMatIrwVxEJKUg== X-IronPort-AV: E=McAfee;i="6700,10204,11320"; a="37579681" X-IronPort-AV: E=Sophos;i="6.13,217,1732608000"; d="scan'208";a="37579681" Received: from orviesa004.jf.intel.com ([10.64.159.144]) by fmvoesa111.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Jan 2025 06:39:19 -0800 X-CSE-ConnectionGUID: Bbj5HgRaSxWiRDEvQpZb0Q== X-CSE-MsgGUID: NUQaXBdfTvGoh730BbisNA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.13,217,1732608000"; d="scan'208";a="111232028" Received: from turnipsi.fi.intel.com (HELO kekkonen.fi.intel.com) ([10.237.72.44]) by orviesa004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Jan 2025 06:39:11 -0800 Received: from svinhufvud.intel.com (maa-artisokka.localdomain [192.168.240.50]) by kekkonen.fi.intel.com (Postfix) with ESMTP id EBE5E11F95E; Sun, 19 Jan 2025 16:39:04 +0200 (EET) Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo From: Sakari Ailus To: linux-media@vger.kernel.org Cc: Benjamin Mugnier , Sylvain Petinot , Yong Zhi , Dan Scally , Jacopo Mondi , hverkuil@xs4all.nl, laurent.pinchart@ideasonboard.com, bingbu.cao@intel.com, Tianshu Qiu , Maxime Ripard , Rui Miguel Silva , Martin Kepplinger , Purism Kernel Team , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , Robert Foss , Todor Tomov , Bryan O'Donoghue , Tomi Valkeinen , Raspberry Pi Kernel Maintenance , Florian Fainelli , Broadcom internal kernel review list , Maxime Coquelin , Alexandre Torgue , Benoit Parrot , Ricardo Ribalda , "Duc-Long, Le" Subject: [PATCH v9 0/9] Use V4L2 mbus config for conveying link frequency Date: Sun, 19 Jan 2025 16:38:55 +0200 Message-Id: <20250119143904.114991-1-sakari.ailus@linux.intel.com> X-Mailer: git-send-email 2.39.5 Precedence: bulk X-Mailing-List: linux-media@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Hi folks, This set adds a few helpers for obtaining the link frequency from the V4L2 mbus config for devices that don't need to provide an UAPI to change it, and finally move drivers to call v4l2_get_link_freq() on a pad. since v8: - Use memset() to zero mbus config in call_get_mbus_config() instead of documenting the caller is responsible for that. - Call the function obtaining media pad in the external sub-device camss_find_sensor_pad() in the qcom camss driver. Correspondingly, call the related local variables "sensor_pad" instead of "sensor". since v7: - Drop ctrl_to_csi() as it's now unused. - Add patches to document how CSI-2 receiver should obtain the link frequency, moving stopping streaming out of CSI-2 specific part and adding a note on setting all fields in get_mbus_config() op. - Added a patch to convert existing users of v4l2_get_link_freq() to operate on a media pad (vs. the control handler). I'll postpone merging this however to test it a bit as it touches a number of drivers for which I have no hardware for. - Revert the order or the ivsc and ipu6 patches. - Improved documentation as discussed with Laurent in v7 review. since v6: - Remove comments on #else / #endif, it's trivial. - Add a patch to convert the ipu6 driver. since v5: - Only support pad-based operation with CONFIG_MEDIA_CONTROLLER (1st and 2nd patches). since v4: - Rework documentation a little. - Remove wrong alignment change in 2nd patch. - Move link_freq field after the type field in struct v4l2_mbus_config. since v3: - Add back missing ret I accidentally removed rather than moved to the 2nd patch. since v2: - Switch to V4L2 mbus config for conveying the link frequency. since v1: - Add a new 64-bit integer control V4L2_CID_CUR_LINK_FREQ instead of re-using V4L2_CID_LINK_FREQ. Sakari Ailus (9): media: v4l: Support passing media pad argument to v4l2_get_link_freq() media: v4l: Support obtaining link frequency via get_mbus_config media: Documentation: Update link frequency driver documentation media: Documentation: tx-rx: Move transmitter control out of CSI-2 part media: Documentation: Receiver drivers should call v4l2_get_link_freq() media: v4l: Memset argument to 0 before calling get_mbus_config pad op media: intel/ipu6: Obtain link frequency from the remote subdev pad media: ivsc: csi: Obtain link frequency from the media pad media: v4l: Convert the users of v4l2_get_link_freq to call it on a pad Documentation/driver-api/media/tx-rx.rst | 26 ++++--- drivers/media/i2c/st-mipid02.c | 5 +- drivers/media/i2c/tc358746.c | 4 +- drivers/media/pci/intel/ipu3/ipu3-cio2.c | 11 ++- drivers/media/pci/intel/ipu6/ipu6-isys-csi2.c | 12 +-- drivers/media/pci/intel/ivsc/mei_csi.c | 78 +++++++------------ drivers/media/platform/cadence/cdns-csi2rx.c | 4 +- drivers/media/platform/nxp/imx-mipi-csis.c | 5 +- drivers/media/platform/nxp/imx8mq-mipi-csi2.c | 11 ++- .../media/platform/qcom/camss/camss-vfe-17x.c | 9 ++- .../platform/qcom/camss/camss-vfe-gen1.c | 9 ++- drivers/media/platform/qcom/camss/camss.c | 27 +++---- drivers/media/platform/qcom/camss/camss.h | 2 +- .../media/platform/raspberrypi/rp1-cfe/cfe.c | 4 +- drivers/media/platform/st/stm32/stm32-csi.c | 4 +- drivers/media/platform/ti/cal/cal-camerarx.c | 3 +- drivers/media/platform/ti/cal/cal.c | 4 +- drivers/media/platform/ti/cal/cal.h | 1 + drivers/media/v4l2-core/v4l2-common.c | 32 +++++++- drivers/media/v4l2-core/v4l2-subdev.c | 2 + include/media/v4l2-common.h | 19 ++++- include/media/v4l2-mediabus.h | 2 + include/media/v4l2-subdev.h | 4 +- 23 files changed, 161 insertions(+), 117 deletions(-) base-commit: c4b7779abc6633677e6edb79e2809f4f61fde157