[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201216215840.GM26370@paasikivi.fi.intel.com>
Date: Wed, 16 Dec 2020 23:58:40 +0200
From: Sakari Ailus <sakari.ailus@...ux.intel.com>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc: Rob Herring <robh@...nel.org>,
Guennadi Liakhovetski <g.liakhovetski@....de>,
Maxime Ripard <mripard@...nel.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Jacopo Mondi <jacopo@...ndi.org>,
Laurent Pinchart <laurent.pinchart+renesas@...asonboard.com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org
Subject: Re: [PATCH v3 1/2] media: dt-bindings: Convert video-interfaces.txt
properties to schemas
Hi Laurent,
On Wed, Dec 16, 2020 at 04:52:20PM +0200, Laurent Pinchart wrote:
> > + clock-lanes:
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > + # Assume up to 9 physical lane indices
> > + maximum: 8
> > + description:
> > + Physical clock lane index. Position of an entry determines
>
> s/index/indexes/ (or indices) as there are potentially multiple entries
> (even if in practice, for all bus types we currently support, only one
> clock lane is supported) ?
We could easily change it if that appears.
The property was named in plural to align with data-lanes, without
intention of having more clock lanes. We could of course allow more if that
happens, but I doubt it.
--
Sakari Ailus
Powered by blists - more mailing lists