From: Takashi Iwai <tiwai@suse.de>
To: raoxu <raoxu@uniontech.com>
Cc: perex@perex.cz, tiwai@suse.com, peter.ujfalusi@linux.intel.com,
kai.vehmanen@linux.intel.com, tglx@kernel.org,
broonie@kernel.org, stuart.a.hayhurst@gmail.com,
wangruikang@iscas.ac.cn, zhangheng@kylinos.cn,
cassiogabrielcontato@gmail.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda: Add Lisuan HDMI controller and codec support
Date: Mon, 17 Aug 2026 13:51:39 +0200 [thread overview]
Message-ID: <878q65rmlw.wl-tiwai@suse.de> (raw)
In-Reply-To: <DE1B62191D573D37+20260817085531.992573-1-raoxu@uniontech.com>
On Mon, 17 Aug 2026 10:55:31 +0200,
raoxu wrote:
>
> From: Xu Rao <raoxu@uniontech.com>
>
> Lisuan GPUs expose an HD-audio controller at PCI ID 4c54:5010 and an
> HDMI/DP codec with codec ID 0x4c545020. Neither ID is currently matched
> by the HDA stack, leaving HDMI/DP audio unavailable on these devices.
>
> The existing downstream support uses the generic HDMI codec path and
> attaches no Lisuan-specific capability flags to the controller. Its
> dedicated AZX driver type only changes the short driver name.
>
> Use the corresponding generic upstream paths instead: bind 4c54:5010 to
> AZX_DRIVER_GENERIC, register 0x4c545020 as MODEL_GENERIC, and add the
> Lisuan codec vendor name. This keeps the enablement minimal and avoids
> a vendor-only AZX driver type with no vendor-specific behavior.
>
> Signed-off-by: Xu Rao <raoxu@uniontech.com>
Applied now. Thanks.
Takashi
prev parent reply other threads:[~2026-08-17 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 8:55 raoxu
2026-08-17 11:51 ` Takashi Iwai [this message]
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=878q65rmlw.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=broonie@kernel.org \
--cc=cassiogabrielcontato@gmail.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=raoxu@uniontech.com \
--cc=stuart.a.hayhurst@gmail.com \
--cc=tglx@kernel.org \
--cc=tiwai@suse.com \
--cc=wangruikang@iscas.ac.cn \
--cc=zhangheng@kylinos.cn \
/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®