Message ID | 20230113010135.2620818-1-shravan.chippa@microchip.com (mailing list archive) |
---|---|
Headers | show
Return-Path: <linux-media-owner@vger.kernel.org> X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3D5F8C54EBD for <linux-media@archiver.kernel.org>; Fri, 13 Jan 2023 01:01:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239769AbjAMBBs (ORCPT <rfc822;linux-media@archiver.kernel.org>); Thu, 12 Jan 2023 20:01:48 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54158 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235143AbjAMBBr (ORCPT <rfc822;linux-media@vger.kernel.org>); Thu, 12 Jan 2023 20:01:47 -0500 Received: from esa.microchip.iphmx.com (esa.microchip.iphmx.com [68.232.154.123]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8B0A510CF; Thu, 12 Jan 2023 17:01:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1673571706; x=1705107706; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=0t8AreH3mEzM1QqyAtblkZEvJtBktvGR13ETzZaDdZA=; b=S+xMu1b9SJVKLMthRj23eGFOFNTVFPOxXJXEZMHCqe9NnBdRDLpB4sBh 4b67UiSPa4jEfaj6KMSRB+Gsyi7Hks8jIp+9NCvQSqnw+QBh8XhRoG56f 5WwGIlddZUky85gmElFWYuGv2hUTWRwTxaC07WV3VL2NFtAMlAYZIJjRU bLT2Mcib8Pqt2uHpGKJjIHwk80TnNQlmasa0vzPz30mTAF7Ykj05CoH0S xXQmYixoGfYNMGHLZwaBJlsC6EcCBsfeWzk1KNp9/kDaPEoROAEuQAv9L CCDHczpC/eH1j/r8/kLeFFVAwCqf/OGaNXbducGgida0ldchRWyWBAa0M A==; X-IronPort-AV: E=Sophos;i="5.97,212,1669100400"; d="scan'208";a="195570674" Received: from unknown (HELO email.microchip.com) ([170.129.1.10]) by esa2.microchip.iphmx.com with ESMTP/TLS/AES256-SHA256; 12 Jan 2023 18:01:45 -0700 Received: from chn-vm-ex02.mchp-main.com (10.10.85.144) by chn-vm-ex04.mchp-main.com (10.10.85.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.16; Thu, 12 Jan 2023 18:01:45 -0700 Received: from microchip1-OptiPlex-9020.microchip.com (10.10.115.15) by chn-vm-ex02.mchp-main.com (10.10.85.144) with Microsoft SMTP Server id 15.1.2507.16 via Frontend Transport; Thu, 12 Jan 2023 18:01:42 -0700 From: shravan kumar <shravan.chippa@microchip.com> To: <paul.j.murphy@intel.com>, <daniele.alessandrelli@intel.com>, <mchehab@kernel.org> CC: <linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>, "shravan kumar" <shravan.chippa@microchip.com>, Jacopo Mondi <jacopo@jmondi.org>, Sakari Ailus <sakari.ailus@iki.fi> Subject: [PATCH v9 0/4] media: i2c: imx334: support lower bandwidth mode Date: Fri, 13 Jan 2023 06:31:31 +0530 Message-ID: <20230113010135.2620818-1-shravan.chippa@microchip.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain Precedence: bulk List-ID: <linux-media.vger.kernel.org> X-Mailing-List: linux-media@vger.kernel.org |
Series |
media: i2c: imx334: support lower bandwidth mode
|
expand
|
From: Shravan Chippa <shravan.chippa@microchip.com> Hi This patch series is for imx334 sensor driver support for lower bandwidth Some platforms may not be capable of supporting the bandwidth required for 12 bit or 3840x2160@60 resolutions. Add support for dynamically selecting 10 bit and 1920x1080@30 resolutions while leaving the existing configuration as default V8 -> V9 -Updated all array values with samall later to get unifamity in mode array values -corrected hblank_min, hbalank, pix_clk for 1920x1080@30 updated according to link frequency -corrected mutex use for imx334_get_format_code function -corrected the fmt->format.code value assinment -in function imx334_get_format_code variable "i" value comparision corrected V7 -> V8 -patch drop "mimx334-odify-link-frequency" as per the commnets linkfrquncy will be half of the line bandwidth -changed 1920x1080@30 mode link frequency from (891000000Mbps) to (445500000Mbps). linkfrquncy will be half of the line bandwidth V6 -> V7 Reloved: kernel test robot warning "drivers/media/i2c/imx334.c:767:15: warning: unused variable 'i' " V5 -> V6 -Drop the dt-binding patch -Optimize the code to avoid duplicating the lines -Added proper mutex while imx334_mbus_codes array -Modified Function __v4l2_ctrl_modify_range arguments as per the review commants -Added hblank dummy set ctrl -Removed Redundant comment -corrected code alignment -All commit msgs are re-written V4 -> V5 -Added 5 more patchs as per the review comments witch has below updates -Updated 1782000000Mbps link frequency for 3840x2160@60 as per the mode values -Updated 1782000000Mbps link frequency in dt-bindings also -Updated 3840x2160@60 mode array with default(reset) values -Updated hblank __v4l2_ctrl_s_ctrl() to __v4l2_ctrl_modify_range() Suggested-by: Jacopo Mondi <jacopo@jmondi.org> -Current mode update only when we try to set V4L2_SUBDEV_FORMAT_ACTIVE -Added link frequency (891000000Mbps) and pixel rate (74250000) to 1920x1080@30 mode Suggested-by: Sakari Ailus <sakari.ailus@iki.fi> -Updated commit message V3 -> V4 - Make the 12 bit and 3840x2160 as default - Set bus code SRGGB12 if set format fails V2 -> V3 - Fixed the warning reported by kernel test robot V1 -> V2 - Addressed the review comment given by Jacopo Mondi, Which has bug in imx334_enum_frame_size() loop function, Shravan Chippa (4): media: i2c: imx334: replace __v4l2_ctrl_s_ctrl to __v4l2_ctrl_modify_range media: i2c: imx334: add missing reset values for mode 3840x2160_regs[] media: i2c: imx334: support lower bandwidth mode media: i2c: imx334: update pixel and link frequency drivers/media/i2c/imx334.c | 339 +++++++++++++++++++++++++++++++++---- 1 file changed, 309 insertions(+), 30 deletions(-)