From: Jacopo Mondi <jacopo+renesas@jmondi.org>
To: robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-media@vger.kernel.org
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
mchehab@kernel.org, sakari.ailus@linux.intel.com,
hverkuil-cisco@xs4all.nl, dave.stevenson@raspberrypi.com,
dongchun.zhu@mediatek.com, linux-renesas-soc@vger.kernel.org,
laurent.pinchart@ideasonboard.com,
roman.kovalivskyi@globallogic.com, Rob Herring <robh@kernel.org>,
Jacopo Mondi <jacopo@jmondi.org>
Subject: [PATCH v3 2/3] dt-bindings: media: i2c: Document 'remote-endpoint'
Date: Wed, 15 Jul 2020 14:48:37 +0200 [thread overview]
Message-ID: <20200715124838.84552-3-jacopo+renesas@jmondi.org> (raw)
In-Reply-To: <20200715124838.84552-1-jacopo+renesas@jmondi.org>
Document the 'remote-endpoint' property and add it to the list of required
endpoint properties in imx219 and ov8856 dt-schema binding files.
While at it, remove 'endpoint' from the list of required properties in
the ov8856 bindings file, as it is allowed to specify port nodes without
a connected endpoint.
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Jacopo Mondi <jacopo@jmondi.org>
---
Documentation/devicetree/bindings/media/i2c/imx219.yaml | 5 +++++
Documentation/devicetree/bindings/media/i2c/ov8856.yaml | 7 ++++---
2 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/media/i2c/imx219.yaml b/Documentation/devicetree/bindings/media/i2c/imx219.yaml
index dfc4d29a4f04..0251e15fe0a7 100644
--- a/Documentation/devicetree/bindings/media/i2c/imx219.yaml
+++ b/Documentation/devicetree/bindings/media/i2c/imx219.yaml
@@ -71,8 +71,13 @@ properties:
description:
Allowed data bus frequencies.
+ remote-endpoint:
+ description: |-
+ phandle to the video receiver input port
+
required:
- link-frequencies
+ - remote-endpoint
required:
- compatible
diff --git a/Documentation/devicetree/bindings/media/i2c/ov8856.yaml b/Documentation/devicetree/bindings/media/i2c/ov8856.yaml
index 1956b2a32bf4..8d662f9dac5f 100644
--- a/Documentation/devicetree/bindings/media/i2c/ov8856.yaml
+++ b/Documentation/devicetree/bindings/media/i2c/ov8856.yaml
@@ -84,12 +84,13 @@ properties:
Allowed data bus frequencies. 360000000, 180000000 Hz or both
are supported by the driver.
+ remote-endpoint:
+ description: |-
+ phandle to the video receiver input port
required:
- link-frequencies
-
- required:
- - endpoint
+ - remote-endpoint
required:
- compatible
--
2.27.0
next prev parent reply other threads:[~2020-07-15 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 12:48 [PATCH v3 0/3] dt-bidings: media: ov5647 bindings + small fix Jacopo Mondi
2020-07-15 12:48 ` [PATCH v3 1/3] dt-bindings: media: ov5647: Convert to json-schema Jacopo Mondi
2020-07-15 12:48 ` Jacopo Mondi [this message]
2020-07-15 12:48 ` [PATCH v3 3/3] media: MAINTAINERS: ov5647: Replace maintainer Jacopo Mondi
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=20200715124838.84552-3-jacopo+renesas@jmondi.org \
--to=jacopo+renesas@jmondi.org \
--cc=dave.stevenson@raspberrypi.com \
--cc=devicetree@vger.kernel.org \
--cc=dongchun.zhu@mediatek.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jacopo@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=roman.kovalivskyi@globallogic.com \
--cc=sakari.ailus@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.