Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp2188462ybl; Thu, 15 Aug 2019 07:55:52 -0700 (PDT) X-Google-Smtp-Source: APXvYqxYwHZZFWO1zjb+CYVCrn5FjNc+PudF9rnXbWVg1zUqULHJ12ODIbX4IHtYXIyzq6Q5I+Yc X-Received: by 2002:a17:902:3003:: with SMTP id u3mr4698388plb.8.1565880952797; Thu, 15 Aug 2019 07:55:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565880952; cv=none; d=google.com; s=arc-20160816; b=yWr08jIKlxaBz6dlgVbpvTPJyFG3yevU81sQyyGRQSe5XCm+BJAjbx2tULmZz8Gcvf vHA+h/vjC3ndl8s8k1jTK1yEQHqqDfvXa+R4NQKc6ij4JH+w34RhUE7ne/k6ScmFynhf C6AnfmH3vTv46ORaWjJRZR+Gr00qSS5TyjbWrnetg5vrvUDago2ATPggK6GO7JwM6Dbf PPD0V+DBnAw41/q8fMcqVHAUJTMDFRMDhuD21VMjYhx8qYh8hFoYsf+AAPTyYXUA4Qa7 mhFeDFxL5DetCFKt1QPGi8lTtXKoznAfYI1psSqmusvgT9/3tJQzpUKDNBRwH7iVnkL5 lENQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=Ch88eZrPdKHv0ddG+je1mJ3bBxQ7EGyBWJU8VicrvOk=; b=PJg8663ErB/OCX+IoPs/vD4mGB25Dm3s2AzH2U6W4ZZwVNLSuL9PQugMHN91AyH0uK Cr/v0sKeF+Uwknn5QmOj/QKcTmBq64OZQoUq55EdONRPh6/AIMmzzj4wlaHGXUkovj0r Wx7mS4vQw0rDfjzWVh1JCk8iQ54nGrADRlFSrDvdBM/ZEoCp7p8o49qLj6/10Vmtkv7u 3QDvy0tsNRuTG88t+Hw3owcWbQZfbAnoaW5+gHzmOxBktQbvV3ap97k7AgfJxcag0NPw nsDYSacV7WEu/ez3VOLNPxmpJdN1wKETcqlt8adkZyWNIJWy//mI2oJsN6bV8zq2qDbP mRjg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass (test mode) header.i=@ideasonboard.com header.s=mail header.b=EKMIUjSE; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v189si2215083pfv.99.2019.08.15.07.55.37; Thu, 15 Aug 2019 07:55:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass (test mode) header.i=@ideasonboard.com header.s=mail header.b=EKMIUjSE; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732020AbfHOM6h (ORCPT + 99 others); Thu, 15 Aug 2019 08:58:37 -0400 Received: from perceval.ideasonboard.com ([213.167.242.64]:45238 "EHLO perceval.ideasonboard.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729818AbfHOM6h (ORCPT ); Thu, 15 Aug 2019 08:58:37 -0400 Received: from pendragon.ideasonboard.com (dfj612yhrgyx302h3jwwy-3.rev.dnainternet.fi [IPv6:2001:14ba:21f5:5b00:ce28:277f:58d7:3ca4]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id AC9BD2AF; Thu, 15 Aug 2019 14:58:34 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1565873914; bh=mi6MwhXdNTovhLsU8H3i0i1nB7aiZZZgLLkKMJdQkUI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=EKMIUjSEjxY+Zh/gFLwrZ9y+EKc+z12mbdR7SQfOiafsOBygmEvLxZ80CR6UIqxzT /b9hHHmYenMjQpe2UTaWgSzi/7N6FndkY24W0zug61pYfvNXN2tWoO/p0+OKnrMWKu LLA5l1jyBlZOYci2NtOaNaInNcM/qdTMjfMSOEZA= Date: Thu, 15 Aug 2019 15:58:31 +0300 From: Laurent Pinchart To: Jacopo Mondi Cc: Sakari Ailus , Mauro Carvalho Chehab , Hans Verkuil , Rob Herring , "open list:MEDIA INPUT INFRASTRUCTURE (V4L/DVB)" , open list , devicetree@vger.kernel.org Subject: Re: [RFC 1/5] media: dt-bindings: Document 'location' property Message-ID: <20190815125831.GH13823@pendragon.ideasonboard.com> References: <20190814202815.32491-1-jacopo@jmondi.org> <20190814202815.32491-2-jacopo@jmondi.org> <20190815065635.GJ6133@paasikivi.fi.intel.com> <20190815125548.kh2pdxzysafltswc@uno.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190815125548.kh2pdxzysafltswc@uno.localdomain> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 15, 2019 at 02:55:48PM +0200, Jacopo Mondi wrote: > On Thu, Aug 15, 2019 at 09:56:35AM +0300, Sakari Ailus wrote: > > On Wed, Aug 14, 2019 at 10:28:11PM +0200, Jacopo Mondi wrote: > > > Add the 'location' device property, used to specify the camera device > > > mounting position. The property is particularly meaningful for mobile > > > devices with a well defined usage orientation. > > > > > > Signed-off-by: Jacopo Mondi > > > --- > > > Documentation/devicetree/bindings/media/video-interfaces.txt | 4 ++++ > > > 1 file changed, 4 insertions(+) > > > > > > diff --git a/Documentation/devicetree/bindings/media/video-interfaces.txt b/Documentation/devicetree/bindings/media/video-interfaces.txt > > > index f884ada0bffc..819077b2649c 100644 > > > --- a/Documentation/devicetree/bindings/media/video-interfaces.txt > > > +++ b/Documentation/devicetree/bindings/media/video-interfaces.txt > > > @@ -89,6 +89,10 @@ Optional properties > > > but a number of degrees counter clockwise. Typical values are 0 and 180 > > > (upside down). > > > > > > +- location: The camera device mounting position, relative to the device > > > + usage orientation. Possible values are: > > > + 0 - Front camera. The image sensor is mounted on the front side of the device. > > > + 1 - Back camera. The image sensor is mounted on the back side of the device. > > > > Would it make sense to make this a little more generic? Such as s/image > > sensor/ device/, for instance? > > Laurent seems to be of the opposite opinion, but i think staying as > generic as possible might be a good idea. Now I have a linguistic > problem though. > > +- location: The device mounting position, relative to the device > + usage orientation. Possible values are: > + 0 - Front. The device is mounted on the front side of the device. > + 1 - Back. The device is mounted on the back side of the device. > > So I need one "device" to indicate the lens/flash/image sensor and one > to indicate the device they're installed on :) Any idea? > > > > > Is this also relevant for flash or lens devices? > > > > Flash (torch) devices could be present, at least principle, without a > > camera. There once was even such a Nokia phone, 1100 unless I'm mistaken. > > :-) > > Not to mention that lenses are indeed installed in the same package as > the camera sensor, but they're described as separate device nodes as > flash leds are, so the mounting location might need to be specified in their > device node properties too, even if it would be the same as the image > sensor one. For the lens I really don't think we need it. For the flash, I envision it will be useful to know more about its physical location relative to the camera sensor, but that will be a displacement, not a front/back location as the flash should really be on the same side as the camera sensor :-) Note that, technically speaking, it will not be the location of the flash controller itself, but of its LED (or other light source). A flash controller could possibly control multiple LEDs, for different sensors, and possibly on different sides of the devices, so we may need to create subnodes for light sources in the flash controller DT node. -- Regards, Laurent Pinchart