From: Thierry Reding <thierry.reding@gmail.com>
To: Hans Verkuil <hans.verkuil@cisco.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: [PATCH v2 1/3] dt-bindings: media: tegra-cec: Document Tegra186 and Tegra194
Date: Tue, 11 Dec 2018 10:48:39 +0100 [thread overview]
Message-ID: <20181211094841.16027-1-thierry.reding@gmail.com> (raw)
From: Thierry Reding <treding@nvidia.com>
The Tegra186 and Tegra194 contain a CEC controller that is identical to
that found in earlier generations. Document the compatible strings for
these newer chips.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
Changes in v2:
- new patch adding missing compatible strings
Documentation/devicetree/bindings/media/tegra-cec.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/media/tegra-cec.txt b/Documentation/devicetree/bindings/media/tegra-cec.txt
index c503f06f3b84..da3590f0b7a1 100644
--- a/Documentation/devicetree/bindings/media/tegra-cec.txt
+++ b/Documentation/devicetree/bindings/media/tegra-cec.txt
@@ -8,6 +8,8 @@ Required properties:
"nvidia,tegra114-cec"
"nvidia,tegra124-cec"
"nvidia,tegra210-cec"
+ "nvidia,tegra186-cec"
+ "nvidia,tegra194-cec"
- reg : Physical base address of the IP registers and length of memory
mapped region.
- interrupts : HDMI CEC interrupt number to the CPU.
--
2.19.1
next reply other threads:[~2018-12-11 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 9:48 Thierry Reding [this message]
2018-12-11 9:48 ` [PATCH v2 2/3] media: tegra-cec: Support Tegra186 and Tegra194 Thierry Reding
2018-12-11 9:48 ` [PATCH v2 3/3] media: tegra-cec: Export OF device ID match table Thierry Reding
2018-12-18 16:42 ` [PATCH v2 1/3] dt-bindings: media: tegra-cec: Document Tegra186 and Tegra194 Rob Herring
2018-12-18 21:32 ` Thierry Reding
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=20181211094841.16027-1-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hans.verkuil@cisco.com \
--cc=jonathanh@nvidia.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@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).