alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Nikhil Mahale <nmahale@nvidia.com>
To: Jaroslav Kysela <perex@perex.cz>,
	Martin Regner <martin@larkos.de>, Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, tiwai@suse.com, aplattner@nvidia.com
Subject: Re: [alsa-devel] [PATCH v3 4/4] ALSA: hda - Add DP-MST support for NVIDIA codecs
Date: Mon, 3 Feb 2020 14:44:28 +0530	[thread overview]
Message-ID: <7a374408-27cb-aa33-b4bc-ee7d9e54baa2@nvidia.com> (raw)
In-Reply-To: <dd1124fb-e3cd-3f8a-a231-f6a0597b4b51@perex.cz>

hdmi_present_sense()
  |-> hdmi_present_sense_via_verbs()
code path need to query PCM jack using pin_idx_to_jack() function and update
its status, just like sync_eld_via_acomp().

Sending patch to get it fixed.

Thanks,
Nikhil Mahale

On 2/3/20 1:07 PM, Jaroslav Kysela wrote:
> External email: Use caution opening links or attachments
> 
> 
> Dne 03. 02. 20 v 0:50 Martin Regner napsal(a):
>> Hi Jaroslav,
>>
>> thanks for the tip. I tried this (in my case echo on  >
>> /sys/bus/pci/devices/0000\:09\:00.1/power/control) but that didn't help.
>>
>> If i comment out the line
>>
>> spec->dyn_pcm_assign = true;
>>
>> in patch_nvhdmi sound is working again.
> 
> Could you show us (upload it to the alsa server and post only URLs) the output
> from alsa-info.sh for both variants (spec->dyn_pcm_assign = true and false) ?
> 
>                                        Thanks,
>                                                Jaroslav
> 
>>
>> Curiously nobody else seems to have this problem. This makes me think
>> the problem lies elsewhere but i have no more ideas at the moment.
>>
>> On 03.02.20 00:00, Jaroslav Kysela wrote:
>>> Dne 02. 02. 20 v 15:18 Martin Regner napsal(a):
>>>> Hi Takashi,
>>>>
>>>> thanks for your reply. I tried that with
>>>>
>>>> cat /proc/asound/card0/codec#0
>>>>
>>>> but that doesn't help. I'm digging me through the kernel config right
>>>> now. May have to change something else.
>>>>
>>>> I simply could create a patch on my gentoo system switching from
>>>> patch_nvhdmi to patch_nvhdmi_legacy for every new kernel, but that won't
>>>> work forever.
>>>>
>>>> If you have other thinks i could try i'd appreciate to hear them.
>>>
>>> You may try to disable PM:
>>>
>>> echo on > /sys/bus/pci/devices/0000\:01\:00.1/power/control
>>>
>>>                  Jaroslav
>>>
>>>
>>>>
>>>> kind regards
>>>> Martin
>>>>
>>>> On 02.02.20 09:37, Takashi Iwai wrote:
>>>>> On Sat, 01 Feb 2020 16:28:08 +0100,
>>>>> Martin Regner wrote:
>>>>>> Hi there,
>>>>>>
>>>>>> since i updated to kernel 5.5 i have no sound over hdmi anymore
>>>>>> (GeForce RTX
>>>>>> 2070).
>>>>>>
>>>>>> With the previous kernel 5.4.14 everything is fine.
>>>>>>
>>>>>> Although i got sound with speaker-test -D hdmi:CARD=NVidia,DEV=2 -c
>>>>>> 2 -r
>>>>>> 44100, pavucontrol shows all hdmi sound devices as unplugged.
>>>>>>
>>>>>> I bisected it down to this commit
>>>>>> (5398e94fb753d022301825ebfa5f7cf8a660d8eb)
>>>>>> and changed the line
>>>>>>
>>>>>> HDA_CODEC_ENTRY(0x10de0093, "GPU 93 HDMI/DP",  patch_nvhdmi)
>>>>>>
>>>>>> to
>>>>>>
>>>>>> HDA_CODEC_ENTRY(0x10de0093, "GPU 93 HDMI/DP", patch_nvhdmi_legacy)
>>>>>>
>>>>>> Now it's working again. I'm not sure if this is a problem with
>>>>>> pulseaudio or
>>>>>> if the RTX 2070 does not support the mentioned codec.
>>>>> The runtime PM turns off the link, so the hotplug notification won't
>>>>> be delivered as default.  Please try reading the corresponding proc
>>>>> file, /proc/asound/card*/codec* file.  This may power up the codec and
>>>>> trigger the hotplug detection if that's the cause.
>>>>>
>>>>>
>>>>> Takashi
>>>>
>>>>
>>>> _______________________________________________
>>>> Alsa-devel mailing list
>>>> Alsa-devel@alsa-project.org
>>>> https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>>>
>>>
>>>
>>
> 
> 
> -- 
> Jaroslav Kysela <perex@perex.cz>
> Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2020-02-03  9:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19  8:47 [alsa-devel] [PATCH v3 0/4] ALSA: hda - Add DP-MST support for NVIDIA codecs Nikhil Mahale
2019-11-19  8:47 ` [alsa-devel] [PATCH v3 1/4] ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense Nikhil Mahale
2019-11-19  8:47 ` [alsa-devel] [PATCH v3 2/4] ALSA: hda - Add DP-MST jack support Nikhil Mahale
2019-11-19  8:47 ` [alsa-devel] [PATCH v3 3/4] ALSA: hda - Add DP-MST support for non-acomp codecs Nikhil Mahale
2019-11-19  8:47 ` [alsa-devel] [PATCH v3 4/4] ALSA: hda - Add DP-MST support for NVIDIA codecs Nikhil Mahale
2020-02-01 15:28   ` Martin Regner
2020-02-02  8:37     ` Takashi Iwai
2020-02-02 14:18       ` Martin Regner
2020-02-02 23:00         ` Jaroslav Kysela
2020-02-02 23:50           ` Martin Regner
2020-02-03  7:37             ` Jaroslav Kysela
2020-02-03  9:14               ` Nikhil Mahale [this message]
2019-11-19 10:57 ` [alsa-devel] [PATCH v3 0/4] " Takashi Iwai
2019-11-19 13:40   ` Kai Vehmanen

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=7a374408-27cb-aa33-b4bc-ee7d9e54baa2@nvidia.com \
    --to=nmahale@nvidia.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=aplattner@nvidia.com \
    --cc=martin@larkos.de \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    /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).