Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Nikhil Mahale <nmahale@nvidia.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.com, aplattner@nvidia.com
Subject: Re: [alsa-devel] [PATCH v1 0/5] ALSA: hda - Add DP-MST support for NVIDIA codecs
Date: Thu, 14 Nov 2019 11:38:02 +0100	[thread overview]
Message-ID: <s5hr22an3p1.wl-tiwai@suse.de> (raw)
In-Reply-To: <20191114033704.18171-1-nmahale@nvidia.com>

On Thu, 14 Nov 2019 04:36:59 +0100,
Nikhil Mahale wrote:
> 
> Today, DisplayPort multi-stream transport (DP-MST) audio is not
> supported on codec drivers which don't use the audio component
> (acomp) binding.
> 
> The commit ade49db337a9 (ALSA: hda/hdmi - Allow audio component for
> AMD/ATI and Nvidia HDMI) added the DRM audio component binding for
> the NVIDIA codec drivers, but the traditional HD-audio unsolicited
> event code path is still in use by the proprietary NVIDIA graphics
> driver.
> 
> This patch set adds DP-MST audio support for non-acomp codec drivers
> which use the traditional HD-audio unsolicited event code path. This
> patch set adds DP-MST support for NVIDIA codecs.
> 
> The patch set has been tested for HDMI/DP-SST/DP-MST(4 dp-mst audio
> streams) configurations on NVIDIA Kepler and Maxwell GPUs, using
> both the nouveau driver and the proprietary NVIDIA graphics driver.

Thanks for the patch.  The logic looks good, but there are a few
concerns in implementation details.  Will comment in the reply of each
patch.

The timing is a bit late for merging into 5.5, though, for this kind
of non-trivial changes.  It'll be likely applied after 5.5 merge
window, so for 5.6.


Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2019-11-14 10:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-14  3:36 [alsa-devel] [PATCH v1 0/5] ALSA: hda - Add DP-MST support for NVIDIA codecs Nikhil Mahale
2019-11-14  3:37 ` [alsa-devel] [PATCH v1 1/5] ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense Nikhil Mahale
2019-11-14  3:37 ` [alsa-devel] [PATCH v1 2/5] ALSA: hda - Add DP-MST jack support Nikhil Mahale
2019-11-14 10:46   ` Kai Vehmanen
2019-11-15  9:39     ` Nikhil Mahale
2019-11-14 10:54   ` Takashi Iwai
2019-11-15  9:46     ` Nikhil Mahale
2019-11-14  3:37 ` [alsa-devel] [PATCH v1 3/5] ALSA: hda - Add DP-MST conn list support Nikhil Mahale
2019-11-14 10:57   ` Takashi Iwai
2019-11-14 11:47     ` Nikhil Mahale
2019-11-14 13:14       ` Takashi Iwai
2019-11-15  9:52         ` Nikhil Mahale
2019-11-15 10:30           ` Takashi Iwai
2019-11-19  8:43             ` Nikhil Mahale
2019-11-14  3:37 ` [alsa-devel] [PATCH v1 4/5] ALSA: hda - Add DP-MST support for non-acomp codecs Nikhil Mahale
2019-11-14  3:37 ` [alsa-devel] [PATCH v1 5/5] ALSA: hda - Add DP-MST support for NVIDIA codecs Nikhil Mahale
2019-11-14 11:02   ` Takashi Iwai
2019-11-14 11:50     ` Nikhil Mahale
2019-11-14 13:15       ` Takashi Iwai
2019-11-14 10:38 ` Takashi Iwai [this message]
2019-11-15  9:37   ` [alsa-devel] [PATCH v1 0/5] " Nikhil Mahale

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=s5hr22an3p1.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=aplattner@nvidia.com \
    --cc=nmahale@nvidia.com \
    --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