Hi Jacopo, (Cc'ing the devicetree list.) On Mon, Oct 07, 2019 at 06:29:03PM +0200, Jacopo Mondi wrote: > Add the 'location' device property, used to specify a device mounting > position. The property is particularly meaningful for mobile devices > with a well defined usage orientation. > > Signed-off-by: Jacopo Mondi <jacopo@xxxxxxxxxx> > --- > .../devicetree/bindings/media/video-interfaces.txt | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/Documentation/devicetree/bindings/media/video-interfaces.txt b/Documentation/devicetree/bindings/media/video-interfaces.txt > index f884ada0bffc..1211bdf80722 100644 > --- a/Documentation/devicetree/bindings/media/video-interfaces.txt > +++ b/Documentation/devicetree/bindings/media/video-interfaces.txt > @@ -89,6 +89,17 @@ Optional properties > but a number of degrees counter clockwise. Typical values are 0 and 180 > (upside down). > > +- location: The mount location of a device (typically an image sensor or a flash > + LED) expressed as a position relative to the usage orientation of the system > + where the device is installed on. > + Possible values are: > + 0 - Front. The device is mounted on the front facing side of the system. How about starting from 1? Then 0 can remain "undefined" value, i.e. the caller can initialise the value to zero without the need to figure out whether reading a given property was successful or not. > + For mobile devices such as smartphones, tablets and laptops the front side is > + the user facing side. > + 1 - Back. The device is mounted on the back side of the system, which is > + defined as the opposite side of the front facing one. > + 2 - External. The device is not attached directly to the system but is > + attached in a way that allows it to move freely. > > Optional endpoint properties > ---------------------------- -- Sakari Ailus sakari.ailus@xxxxxxxxxxxxxxx
