From: Fabio Estevam <festevam@gmail.com>
To: hverkuil-cisco@xs4all.nl
Cc: lars@metafoo.de, matthew.michilot@gmail.com,
tharvey@gateworks.com, linux-media@vger.kernel.org,
slongerbeam@gmail.com, niklas.soderlund@ragnatech.se,
robh+dt@kernel.org, devicetree@vger.kernel.org,
Fabio Estevam <festevam@gmail.com>
Subject: [PATCH 1/2] dt-bindings: adv7180: Introduce adv,adv7182-force-bt656-4
Date: Thu, 27 May 2021 14:32:08 -0300 [thread overview]
Message-ID: <20210527173209.3874124-1-festevam@gmail.com> (raw)
Captured NTSC video would be out of sync when using the adv7280 with
the BT.656-4 protocol. Certain registers (0x04, 0x31, 0xE6) need to
be configured properly to ensure BT.656-4 compatibility.
Introduce the 'adv,adv7182-force-bt656-4' property to allow the ADV7280
behavior to be consistent with the ADV7180, where BT.656-4 timing
is used.
Signed-off-by: Fabio Estevam <festevam@gmail.com>
---
Documentation/devicetree/bindings/media/i2c/adv7180.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/media/i2c/adv7180.yaml b/Documentation/devicetree/bindings/media/i2c/adv7180.yaml
index bcfd93739b4f..83e47b0c9fa2 100644
--- a/Documentation/devicetree/bindings/media/i2c/adv7180.yaml
+++ b/Documentation/devicetree/bindings/media/i2c/adv7180.yaml
@@ -35,6 +35,11 @@ properties:
powerdown-gpios:
maxItems: 1
+ adv,adv7182-force-bt656-4:
+ description:
+ Indicates that ADV7182 should output a BT.656-4 compatible stream.
+ type: boolean
+
port:
$ref: /schemas/graph.yaml#/properties/port
--
2.25.1
next reply other threads:[~2021-05-27 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 17:32 Fabio Estevam [this message]
2021-05-27 17:32 ` [PATCH 2/2] media: i2c: adv7180: fix adv7280 BT.656-4 compatibility Fabio Estevam
2021-06-04 20:54 ` [PATCH 1/2] dt-bindings: adv7180: Introduce adv,adv7182-force-bt656-4 Rob Herring
2021-06-04 21:08 ` Fabio Estevam
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=20210527173209.3874124-1-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=lars@metafoo.de \
--cc=linux-media@vger.kernel.org \
--cc=matthew.michilot@gmail.com \
--cc=niklas.soderlund@ragnatech.se \
--cc=robh+dt@kernel.org \
--cc=slongerbeam@gmail.com \
--cc=tharvey@gateworks.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.