From: Sheetal <sheetal@nvidia.com>
To: <alsa-devel@alsa-project.org>, <perex@perex.cz>
Cc: <jonathanh@nvidia.com>, <thierry.reding@kernel.org>,
<mkumard@nvidia.com>, <spujar@nvidia.com>,
Sheetal <sheetal@nvidia.com>
Subject: [PATCH] tegra-hda: Add HDMI/DP outputs 2-4 for Tegra186+
Date: Thu, 16 Apr 2026 09:06:00 +0000 [thread overview]
Message-ID: <20260416090600.2237882-1-sheetal@nvidia.com> (raw)
Declare the maximum four HDMI/DisplayPort outputs (PCM devices 3, 7,
8 and 9) so PipeWire can see every available port. The HDMI macro's
built-in ControlExists check ensures devices are only created when the
corresponding jack control exists, so SoCs with fewer outputs are
unaffected.
Signed-off-by: Sheetal <sheetal@nvidia.com>
---
ucm2/Tegra/tegra-hda/tegra-hda-HiFi.conf | 28 ++++++++++++++++++++++--
1 file changed, 26 insertions(+), 2 deletions(-)
diff --git a/ucm2/Tegra/tegra-hda/tegra-hda-HiFi.conf b/ucm2/Tegra/tegra-hda/tegra-hda-HiFi.conf
index 3277f6d..f26941b 100644
--- a/ucm2/Tegra/tegra-hda/tegra-hda-HiFi.conf
+++ b/ucm2/Tegra/tegra-hda/tegra-hda-HiFi.conf
@@ -1,10 +1,34 @@
Include.hdmi.File "/codecs/hda/hdmi.conf"
-If.hdmi {
+If.hdmi1 {
Condition { Type AlwaysTrue }
- True.Macro.hdmi.HDMI {
+ True.Macro.hdmi1.HDMI {
Number 1
Device 3
Priority 1100
}
}
+If.hdmi2 {
+ Condition { Type AlwaysTrue }
+ True.Macro.hdmi2.HDMI {
+ Number 2
+ Device 7
+ Priority 1200
+ }
+}
+If.hdmi3 {
+ Condition { Type AlwaysTrue }
+ True.Macro.hdmi3.HDMI {
+ Number 3
+ Device 8
+ Priority 1300
+ }
+}
+If.hdmi4 {
+ Condition { Type AlwaysTrue }
+ True.Macro.hdmi4.HDMI {
+ Number 4
+ Device 9
+ Priority 1400
+ }
+}
--
2.17.1
next reply other threads:[~2026-04-16 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 9:06 Sheetal [this message]
2026-04-16 11:49 ` [PATCH] tegra-hda: Add HDMI/DP outputs 2-4 for Tegra186+ Jaroslav Kysela
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=20260416090600.2237882-1-sheetal@nvidia.com \
--to=sheetal@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=jonathanh@nvidia.com \
--cc=mkumard@nvidia.com \
--cc=perex@perex.cz \
--cc=spujar@nvidia.com \
--cc=thierry.reding@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