linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Rob Herring <robh@kernel.org>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Maxime Ripard <mripard@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Jacopo Mondi <jacopo@jmondi.org>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v3 1/2] media: dt-bindings: Convert video-interfaces.txt properties to schemas
Date: Wed, 16 Dec 2020 23:58:40 +0200	[thread overview]
Message-ID: <20201216215840.GM26370@paasikivi.fi.intel.com> (raw)
In-Reply-To: <X9ofJMIivzPzi8x7@pendragon.ideasonboard.com>

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

  reply	other threads:[~2020-12-16 22:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10 21:16 [PATCH v2 0/2] dt-bindings: media: Convert video-interfaces.txt to schemas Rob Herring
2020-12-10 21:16 ` [PATCH v2 1/2] media: dt-bindings: Convert video-interfaces.txt properties " Rob Herring
2020-12-16 10:18   ` Guennadi Liakhovetski
2020-12-16 14:12     ` Rob Herring
2020-12-16 14:24       ` Laurent Pinchart
2020-12-16 15:03         ` Sakari Ailus
2020-12-16 15:06       ` Guennadi Liakhovetski
2020-12-10 21:16 ` [PATCH v2 2/2] dt-bindings: media: Use graph and video-interfaces schemas Rob Herring
2020-12-10 21:16 ` [PATCH v3 0/2] dt-bindings: media: Convert video-interfaces.txt to schemas Rob Herring
2020-12-16 14:22   ` Hans Verkuil
2020-12-10 21:16 ` [PATCH v3 1/2] media: dt-bindings: Convert video-interfaces.txt properties " Rob Herring
2020-12-16 14:52   ` Laurent Pinchart
2020-12-16 21:58     ` Sakari Ailus [this message]
2020-12-18 18:19     ` Rob Herring
2020-12-19 17:10       ` Laurent Pinchart
2020-12-10 21:16 ` [PATCH v3 2/2] dt-bindings: media: Use graph and video-interfaces schemas Rob Herring
2020-12-16 15:19   ` Laurent Pinchart
2020-12-16 17:38     ` Rob Herring
2020-12-16 17:43       ` Laurent Pinchart
2020-12-16 21:59         ` Sakari Ailus
2020-12-10 22:39 ` [PATCH v2 0/2] dt-bindings: media: Convert video-interfaces.txt to schemas Rob Herring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201216215840.GM26370@paasikivi.fi.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=jacopo@jmondi.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=mripard@kernel.org \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).