From: Sameer Pujar <spujar@nvidia.com>
To: <robh+dt@kernel.org>, <thierry.reding@gmail.com>, <broonie@kernel.org>
Cc: <jonathanh@nvidia.com>, <sharadg@nvidia.com>,
<devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
Sameer Pujar <spujar@nvidia.com>
Subject: [RESEND PATCH 2/2] dt-bindings: tegra: Add missing HDA properties
Date: Thu, 3 Dec 2020 20:06:42 +0530 [thread overview]
Message-ID: <1607006202-4078-3-git-send-email-spujar@nvidia.com> (raw)
In-Reply-To: <1607006202-4078-1-git-send-email-spujar@nvidia.com>
Document the missing properties which are currently required for
Tegra186/Tegra194 DT files.
Signed-off-by: Sameer Pujar <spujar@nvidia.com>
---
.../devicetree/bindings/sound/nvidia,tegra30-hda.yaml | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/Documentation/devicetree/bindings/sound/nvidia,tegra30-hda.yaml b/Documentation/devicetree/bindings/sound/nvidia,tegra30-hda.yaml
index 3059bc3..e543a61 100644
--- a/Documentation/devicetree/bindings/sound/nvidia,tegra30-hda.yaml
+++ b/Documentation/devicetree/bindings/sound/nvidia,tegra30-hda.yaml
@@ -60,6 +60,20 @@ properties:
- const: hda2hdmi
- const: hda2codec_2x
+ power-domains:
+ maxItems: 1
+
+ interconnects:
+ maxItems: 2
+
+ interconnect-names:
+ items:
+ - const: dma-mem
+ - const: write
+
+ iommus:
+ maxItems: 1
+
nvidia,model:
$ref: /schemas/types.yaml#/definitions/string
description: |
--
2.7.4
next prev parent reply other threads:[~2020-12-03 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 14:36 [RESEND PATCH 0/2] Convert Tegra HDA doc to json-schema Sameer Pujar
2020-12-03 14:36 ` [RESEND PATCH 1/2] dt-bindings: tegra: Convert " Sameer Pujar
2020-12-09 20:15 ` Rob Herring
2020-12-03 14:36 ` Sameer Pujar [this message]
2020-12-09 20:15 ` [RESEND PATCH 2/2] dt-bindings: tegra: Add missing HDA properties Rob Herring
2020-12-11 17:49 ` [RESEND PATCH 0/2] Convert Tegra HDA doc to json-schema Mark Brown
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=1607006202-4078-3-git-send-email-spujar@nvidia.com \
--to=spujar@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sharadg@nvidia.com \
--cc=thierry.reding@gmail.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 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).