From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_2 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F23D0C47404 for ; Thu, 12 Sep 2019 12:52:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C66B82075C for ; Thu, 12 Sep 2019 12:52:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1568292725; bh=SYbTgtlWwbFgw4eS3NY4Jh6oYcylB2UdeWZjL4tcw2s=; h=Date:From:To:Cc:Subject:In-Reply-To:References:List-ID:From; b=GN3Zog91STeCPlW+iQj3IpMS2apThEnXcMhipRPOcr9iZx1ctP/Ot2/mdEixG4vl7 l592F8Lu55vQTxavNdX0GUFSbqZZiuxt0/zH2gMQTOQY1KjeSngQkOGOlEpYF0e95z VVqE8EF4/Z1WOwzNSVrgibfFNoIHFGRkKWwX3s0w= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731746AbfILMwF (ORCPT ); Thu, 12 Sep 2019 08:52:05 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:56324 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731635AbfILMwE (ORCPT ); Thu, 12 Sep 2019 08:52:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=Content-Transfer-Encoding: Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To: From:Date:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=kght0b+/jFbvVUWoTghKwS4NUz1nLDzVraODRJdmu40=; b=YuHcfHpbhPBewfxZpfcydTIch LvRSwCK0iANhTS+gpyHMVN0rOe3WAZnneMWN+SV/o10NPISCub9wPRO8RYt0zQEMplDjYJHS90M0b 4Ys+ZU0KDEJXbmNVsfHW70qztZs86l0AsxdjvX1st+9l1Y29nGpn3POcFh73OiJVIRr7T0/+z4sxu BDR+ld1N8bkbaLr9VUDdAqNAHEOFECOwEI32Ps7iTVPqrqT4hwA/66XrlESvGzsnrD5/g7V4KRlmc 0rm7L4qzTEHzSpIBidC8WLaLiS+LIr8VGJr+bBGz6jwRt/pVPxIbiUa+MFz6RndX7fXpC6SC/s5hW zwJyIRXEA==; Received: from 179.186.109.23.dynamic.adsl.gvt.net.br ([179.186.109.23] helo=coco.lan) by bombadil.infradead.org with esmtpsa (Exim 4.92.2 #3 (Red Hat Linux)) id 1i8OZj-00006E-Fk; Thu, 12 Sep 2019 12:51:51 +0000 Date: Thu, 12 Sep 2019 09:51:47 -0300 From: Mauro Carvalho Chehab To: Laurent Pinchart Cc: Jacopo Mondi , Hans Verkuil , Sakari Ailus , tfiga@google.com, Rob Herring , linux-media@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH v2 01/10] media: dt-bindings: Document 'location' property Message-ID: <20190912095120.4a592631@coco.lan> In-Reply-To: <20190827122126.GQ5054@pendragon.ideasonboard.com> References: <20190827092339.8858-1-jacopo@jmondi.org> <20190827092339.8858-2-jacopo@jmondi.org> <20190827122126.GQ5054@pendragon.ideasonboard.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-media-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-media@vger.kernel.org Em Tue, 27 Aug 2019 15:21:26 +0300 Laurent Pinchart escreveu: > Hi Jacopo, > > Thank you for the patch. > > On Tue, Aug 27, 2019 at 11:23:27AM +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 > > --- > > .../devicetree/bindings/media/video-interfaces.txt | 10 ++++++++++ > > 1 file changed, 10 insertions(+) > > > > diff --git a/Documentation/devicetree/bindings/media/video-interfaces.txt b/Documentation/devicetree/bindings/media/video-interfaces.txt > > index f884ada0bffc..865f4142f432 100644 > > --- a/Documentation/devicetree/bindings/media/video-interfaces.txt > > +++ b/Documentation/devicetree/bindings/media/video-interfaces.txt > > @@ -89,6 +89,16 @@ Optional properties > > but a number of degrees counter clockwise. Typical values are 0 and 180 > > (upside down). > > > > +- location: The camera sensor mounting location, expressed as a position > > + relative to the usage orientation of the device the sensor is installed on. > > DT bindings being ABIs, we need to be precise and thorough there. One > particular point that bothers me is that the property is named location, > and its description refers to camera sensor mounting location. Yeah, "location" doesn't sound a good name for me neither. > > I see two options to fix this. One of them is to rename the property to > camera-location, but that would limit its future usage for other types > of devices. The other one is to document the property as applying to a > "device" instead of a "camera sensor", and add one sentence stating that > this property is valid for camera sensors only. > > This will require finding another name for the device that the device is > mounted on though, as using device twice would be very confusing. > > > + Possible values are: > > + 0 - Front. The image sensor is mounted on the front facing side of the device. > > + For mobile devices such as smartphones, tablets and laptops the front side is > > + the user facing side of the device. > > + 1 - Back. The image sensor is mounted on the back side of the device, which is > > + defined as the opposite side of the front facing one. > > + 2 - External. The image sensor is connected to the device by extension cables, > > + and can be freely moved, regardless of the device position. Hmm... Besides the point that Laurent and Rob already commented, just those 3 options doesn't seem good enough. I was reading a public article yesterday about a new device (Samsung Galaxy Fold[1]) with comes with 6 cameras, being 3 at back, 1 at front, when the device is opened, and 1 camera that could be either at the back or at the front, depending if the device is opened or not. Btw, on a device with multiple cameras at the same side, it would make sense to also be able to uniquely identify the location of each sensor somehow. There are also some other new devices with a front motorized slider camera that sits hidden inside the phone, until when someone uses it. Thanks, Mauro