From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.12]) (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 AA74F3859CC; Mon, 9 Mar 2026 12:03:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.12 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773057814; cv=none; b=JCIRoazlv5IZA4pB5iZC9V3MdPmyBQFunoZEcROCMkmCjhpCfeCr40H971GvE9fU6XV9Zt5r1a6pXjnnL/2Y2HuWpOQw6akufw+jjn/cQrk5v++89xHvmcCdKXv1hpQPSTbBIPAffIwq2JMjZOga2+LMLppynys0qRi9965nlbw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773057814; c=relaxed/simple; bh=Akaiyu7zQ927nZZpLebwwa+egRsCipPJa4ER2KrnN1I=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=CSOn78/15+gS3I78nxjwnkE4luyLmnkPJonmBCGFctR4MrjBxpOGwigxb9anW46vzLMWISARcqQJn37POg58TMLBAHowEluHX3K3S5tUYJFn6vAYT+StslviMdctn02JrAjPgzvlNytEZpJCG6vAgBwMcwx08/ACaQqx/6OFItc= 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=SRX3cNs5; arc=none smtp.client-ip=192.198.163.12 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="SRX3cNs5" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1773057812; x=1804593812; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=Akaiyu7zQ927nZZpLebwwa+egRsCipPJa4ER2KrnN1I=; b=SRX3cNs5Fjl2bn3nvxyLG1D/emlwM4xHRTB3jFd0aBFEKjGQ+98+eOm4 yOzMndn3e8LvdJ543eSu6mPP7p5SHVqWkmYc8fplAxVFZDP6ZEOwkdeHN pRx03NPRkkyGZltuQhZ7hb5kg2bu6EwsIwukQddVpmP8PYoZNh74OziCC 2raXrnuh+V6ddEgeXh3zslmXrf4v/WRiJbSKps5jsZv0PBPt0QXvxodsy pIv7LuWePJtpuAh60A0Y2fDVDDvOHNobSg/yU+LCN7EhCCISreXyo0+W0 5OyocTqDaci+tWZYCtWv4w1qExLwQCPxBWEOYqI+e5ky1f0yPiomEeYSw g==; X-CSE-ConnectionGUID: PsCNgCzhSFmHHvi5h1RhHg== X-CSE-MsgGUID: YgJjfOUnRbG18jeHcWfcrw== X-IronPort-AV: E=McAfee;i="6800,10657,11723"; a="77957149" X-IronPort-AV: E=Sophos;i="6.23,109,1770624000"; d="scan'208";a="77957149" Received: from orviesa009.jf.intel.com ([10.64.159.149]) by fmvoesa106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Mar 2026 05:03:31 -0700 X-CSE-ConnectionGUID: XEjHmmRYQEOPI5XlEnX3Lg== X-CSE-MsgGUID: J6oNHFWqTS69yejH4/h7tA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.23,109,1770624000"; d="scan'208";a="219677798" Received: from vpanait-mobl.ger.corp.intel.com (HELO kekkonen.fi.intel.com) ([10.245.245.148]) by orviesa009-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Mar 2026 05:03:29 -0700 Received: from kekkonen.localdomain (localhost [IPv6:::1]) by kekkonen.fi.intel.com (Postfix) with SMTP id BAA04121D1F; Mon, 09 Mar 2026 14:03:59 +0200 (EET) Date: Mon, 9 Mar 2026 14:03:59 +0200 Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo From: Sakari Ailus To: Matthias Fend Cc: Krzysztof Kozlowski , Mauro Carvalho Chehab , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Jimmy Su , Philipp Zabel , linux-media@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, bsp-development.geo@leica-geosystems.com Subject: Re: [PATCH 1/8] dt-bindings: media: i2c: document Omnivision OV08D10 CMOS image sensor Message-ID: References: <20260226-ov08d10-v1-0-c3a916368123@emfend.at> <20260226-ov08d10-v1-1-c3a916368123@emfend.at> <20260227-imported-benevolent-stingray-e97dfd@quoll> <16086ec6-a50c-4d47-8c6a-0e7cb73a5d6d@emfend.at> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16086ec6-a50c-4d47-8c6a-0e7cb73a5d6d@emfend.at> Hi Matthias, Krzysztof, On Fri, Feb 27, 2026 at 04:10:50PM +0100, Matthias Fend wrote: > > > + reset-gpios: > > > + description: Active low XSHUTDN pin > > > > So maybe rather powerdown-gpios, see gpio-consumer-common.yaml? > > As activating the XSHUTDN pin on this sensor works like a reset, I guess > it's okay as it is. > > From what I've seen, it's also common practice for some other Omnivision > sensors to designate the XSHUTDN pin as the reset pin. > This is also the case, for example, with the recently added OS05B10. > > During a review for another sensor, I was asked to use the reset controller > framework instead of the GPIO pin for the reset function, which I did in > this case as well. > To my knowledge, the fallback from the reset controller to a simple reset > pin only works with the 'reset-gpios' property. I'd use "reset" for this, too: it's first and foremost reset. In most camera sensors with "xshutdown" or similar pin the function of the pin is documented to be hardware reset. Most such devices still use very little power in hardware reset state but from software point of view that is still secondary to the reset function. -- Regards, Sakari Ailus