From: Sheetal <sheetal@nvidia.com>
To: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Mohan Kumar <mkumard@nvidia.com>,
Sameer Pujar <spujar@nvidia.com>, <linux-sound@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Anupama Kunkulagunta" <akunkulagunt@nvidia.com>,
Sheetal <sheetal@nvidia.com>
Subject: [PATCH] ALSA: hda/tegra: Add Tegra268 HDMI/DP codec ID
Date: Wed, 4 Nov 2026 10:29:55 +0000 [thread overview]
Message-ID: <20261104102955.1089991-1-sheetal@nvidia.com> (raw)
From: Anupama Kunkulagunta <akunkulagunt@nvidia.com>
The Tegra268 HDMI/DP HDA codec reports codec ID 0x10de0037, which is
not present in the Tegra HDMI codec driver's device table. Add this
ID so the driver can bind to the Tegra268 codec.
Tegra268 uses the same HDMI/DP codec programming model as Tegra234.
Reuse MODEL_TEGRA234 to enable DP MST, dynamic pin output assignment
and HDMI interrupt trigger control for Tegra268.
Signed-off-by: Anupama Kunkulagunta <akunkulagunt@nvidia.com>
Signed-off-by: Sheetal <sheetal@nvidia.com>
---
sound/hda/codecs/hdmi/tegrahdmi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/hda/codecs/hdmi/tegrahdmi.c b/sound/hda/codecs/hdmi/tegrahdmi.c
index 171d1ee154d9..6baa98a3c627 100644
--- a/sound/hda/codecs/hdmi/tegrahdmi.c
+++ b/sound/hda/codecs/hdmi/tegrahdmi.c
@@ -338,6 +338,7 @@ static const struct hda_device_id snd_hda_id_tegrahdmi[] = {
HDA_CODEC_ID_MODEL(0x10de0033, "SoC 33 HDMI/DP", MODEL_TEGRA234),
HDA_CODEC_ID_MODEL(0x10de0034, "Tegra264 HDMI/DP", MODEL_TEGRA234),
HDA_CODEC_ID_MODEL(0x10de0035, "SoC 35 HDMI/DP", MODEL_TEGRA234),
+ HDA_CODEC_ID_MODEL(0x10de0037, "Tegra268 HDMI/DP", MODEL_TEGRA234),
{} /* terminator */
};
MODULE_DEVICE_TABLE(hdaudio, snd_hda_id_tegrahdmi);
base-commit: d6bcfc94eb4da6e089c5473970cd96727292fd97
--
2.43.0
next reply other threads:[~2026-11-04 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 10:29 Sheetal [this message]
2026-11-04 14:42 ` Takashi Iwai
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=20261104102955.1089991-1-sheetal@nvidia.com \
--to=sheetal@nvidia.com \
--cc=akunkulagunt@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=perex@perex.cz \
--cc=spujar@nvidia.com \
--cc=thierry.reding@kernel.org \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®