From: Ken Sloat <KSloat@aampglobal.com>
To: "eugen.hristev@microchip.com" <eugen.hristev@microchip.com>
Cc: Ken Sloat <KSloat@aampglobal.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"ludovic.desroches@microchip.com"
<ludovic.desroches@microchip.com>,
"sakari.ailus@iki.fi" <sakari.ailus@iki.fi>,
"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: [PATCH v3 2/2] media: atmel-isc: Update device tree binding documentation
Date: Mon, 4 Feb 2019 14:18:14 +0000 [thread overview]
Message-ID: <20190204141756.234563-2-ksloat@aampglobal.com> (raw)
In-Reply-To: <20190204141756.234563-1-ksloat@aampglobal.com>
From: Ken Sloat <ksloat@aampglobal.com>
Update device tree binding documentation specifying how to
enable BT656 with CRC decoding and specify properties for
default parallel bus type.
Signed-off-by: Ken Sloat <ksloat@aampglobal.com>
---
Changes in v2:
-Use correct media "bus-type" dt property.
Changes in v3:
-Specify default bus type.
-Document optional parallel bus flags.
.../devicetree/bindings/media/atmel-isc.txt | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/Documentation/devicetree/bindings/media/atmel-isc.txt b/Documentation/devicetree/bindings/media/atmel-isc.txt
index bbe0e87c6188..db3749a3964f 100644
--- a/Documentation/devicetree/bindings/media/atmel-isc.txt
+++ b/Documentation/devicetree/bindings/media/atmel-isc.txt
@@ -21,6 +21,21 @@ Required properties for ISC:
- pinctrl-names, pinctrl-0
Please refer to pinctrl-bindings.txt.
+Optional properties for ISC:
+- bus-type
+ When set to 6, Bt.656 decoding (embedded sync) with CRC decoding
+ is enabled. If omitted, then the default bus-type is parallel and
+ the additional properties to follow can be specified:
+- hsync-active
+ Active state of the HSYNC signal, 0/1 for LOW/HIGH respectively.
+ If unspecified, this signal is set as active HIGH.
+- vsync-active
+ Active state of the VSYNC signal, 0/1 for LOW/HIGH respectively.
+ If unspecified, this signal is set as active HIGH.
+- pclk-sample
+ Sample data on rising (1) or falling (0) edge of the pixel clock
+ signal. If unspecified, data is sampled on the rising edge.
+
ISC supports a single port node with parallel bus. It should contain one
'port' child node with child 'endpoint' node. Please refer to the bindings
defined in Documentation/devicetree/bindings/media/video-interfaces.txt.
--
2.17.1
next prev parent reply other threads:[~2019-02-04 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 14:18 [PATCH v3 1/2] media: atmel-isc: Add support for BT656 with CRC decoding Ken Sloat
2019-02-04 14:18 ` Ken Sloat [this message]
2019-02-06 12:56 ` [PATCH v3 2/2] media: atmel-isc: Update device tree binding documentation sakari.ailus
2019-02-14 15:44 ` Rob Herring
2019-02-18 11:59 ` sakari.ailus
2019-02-06 12:55 ` [PATCH v3 1/2] media: atmel-isc: Add support for BT656 with CRC decoding sakari.ailus
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=20190204141756.234563-2-ksloat@aampglobal.com \
--to=ksloat@aampglobal.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=eugen.hristev@microchip.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=mchehab@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=sakari.ailus@iki.fi \
/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).