On Tue, 30 Apr 2019 08:27:54 +0200, rodomar705@protonmail.com wrote:

Nope, neither adding AZX_DCAPS_PM_RUNTIME as seen on other AMD codecs below seems to affect it, unfortunately.

Please don't drop Cc to ML and others.

And, did you try other position_fix option value, too?

Otherwise I have out of idea. It must be platform-specific issue only the hardware vendors know.

Takashi

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ Il lunedì 29 aprile 2019 21:28, Takashi Iwai tiwai@suse.de ha scritto:

...

On Mon, 29 Apr 2019 20:21:22 +0200, rodomar705@protonmail.com wrote:

...

Whoops, sorry. Here it is.

OK, it's an AMD chip and not listed explicitly in the driver config. Does the patch below have any influence?

Takashi

--- a/sound/pci/hda/hda_intel.c +++ b/sound/pci/hda/hda_intel.c @@ -2452,6 +2452,9 @@ static const struct pci_device_id azx_ids[] = { /* AMD Hudson */ { PCI_DEVICE(0x1022, 0x780d), .driver_data = AZX_DRIVER_GENERIC | AZX_DCAPS_PRESET_ATI_SB },

• /* AMD family 17h */

• { PCI_DEVICE(0x1022, 0x1457),

•   .driver_data = AZX_DRIVER_GENERIC | AZX_DCAPS_PRESET_ATI_SB },
  
  
  

  /* AMD Stoney */ { PCI_DEVICE(0x1022, 0x157a), .driver_data = AZX_DRIVER_GENERIC | AZX_DCAPS_PRESET_ATI_SB |