At Sun, 03 Nov 2013 08:50:55 +0100, Dagg Stompler wrote: > > > ----- Original Message ----- > > From: Deucher, Alexander > > Sent: 10/19/13 03:59 PM > > To: Dagg Stompler, Takashi Iwai > > Subject: RE: [alsa-devel] hdmi sound rerouted? > > > > > -----Original Message----- > > > > > From: Dagg Stompler [mailto:daggs@xxxxxxx] > > > > > Sent: Saturday, October 19, 2013 5:49 AM > > > > > To: Takashi Iwai; Deucher, Alexander > > > > > Cc: Clemens Ladisch; alsa-user@xxxxxxxxxxxxxxxxxxxxx; alsa-devel@alsa- > > > > > project.org > > > > > Subject: Re: [alsa-devel] hdmi sound rerouted? > > > > > > > > > > > ----- Original Message ----- > > > > > > From: Takashi Iwai > > > > > > Sent: 10/08/13 10:49 AM > > > > > > To: Deucher, Alexander > > > > > > Subject: Re: [alsa-devel] hdmi sound rerouted? > > > > > > > > > > > > At Mon, 7 Oct 2013 13:36:24 +0000, > > > > > > Deucher, Alexander wrote: > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: Takashi Iwai [mailto:tiwai@xxxxxxx] > > > > > > > > Sent: Monday, September 30, 2013 5:18 AM > > > > > > > > To: Deucher, Alexander > > > > > > > > Cc: Clemens Ladisch; Dagg Stompler; alsa-user@xxxxxxxxxxxxxxxxxxxxx; > > > > > alsa- > > > > > > > > devel@xxxxxxxxxxxxxxxx > > > > > > > > Subject: Re: [alsa-devel] hdmi sound rerouted? > > > > > > > > > > > > > > > > At Mon, 30 Sep 2013 02:23:22 +0000, > > > > > > > > Deucher, Alexander wrote: > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > > From: Clemens Ladisch [mailto:cladisch@xxxxxxxxxxxxxx] > > > > > > > > > > Sent: Saturday, September 28, 2013 6:33 PM > > > > > > > > > > To: Dagg Stompler > > > > > > > > > > Cc: alsa-user@xxxxxxxxxxxxxxxxxxxxx; Deucher, Alexander; alsa- > > > > > > > > devel@alsa- > > > > > > > > > > project.org > > > > > > > > > > Subject: Re: [alsa-devel] hdmi sound rerouted? > > > > > > > > > > > > > > > > > > > > Dagg Stompler wrote: > > > > > > > > > > >> daggs@xxxxxxx wrote: > > > > > > > > > > >>> card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] > > > > > > > > > > >>> card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] > > > > > > > > > > >>> card 2: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] > > > > > > > > > > >> > > > > > > > > > > >> The second one is called "Generic" because your kernel does not > > > > > (yet) > > > > > > > > > > >> know the hardware. > > > > > > > > > > >> > > > > > > > > > > >>> 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] > > > > > Cedar > > > > > > > > > > HDMI Audio [Radeon HD 5400/6300 Series] > > > > > > > > > > >>> 06:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] > > > > > RV635 > > > > > > > > > > HDMI Audio [Radeon HD 3600 Series] > > > > > > > > > > >> > > > > > > > > > > >> These are the HDMI outputs of *two* graphics cards. The first > > > > > one's > > > > > > > > > > >> model is so new that the driver doesn't know it. > > > > > > > > > > > > > > > > > > > > > > the 3600 doesn't have hdmi socket so I think it is irrelevant for my > > > > > issue. > > > > > > > > > > > > > > > > > > > > The RV635 chip does support HDMI outputs (even if none are > > > > > actually > > > > > > > > > > connected), so the corresponding PCI device shows up here. > > > > > > > > > > > > > > > > > > > > >>> If you update the kernel, you will get two devices named "HDA > > > > > ATI > > > > > > > > > > HDMI". > > > > > > > > > > > > > > > > > > > > > > upgrade to where? > > > > > > > > > > > > > > > > > > > > Oops. Even the latest driver lacks the PCI IDs of many HDMI HDA > > > > > devices > > > > > > > > > > (aa50/aa58/aa60/aa68/aa80/aa88/aa90/aa98: > > > > > > > > > > Cypress/Juniper/Redwood/Cedar/ > > > > > > > > > > Cayman+Antilles/Barts/Turks/Caicos). > > > > > > > > > > > > > > > > > > > > Alex, are these devices that require disabling snooping? > > > > > > > > > > > > > > > > > > Sorry what does snooping mean in this context? > > > > > > > > > > > > > > > > Most of HD-audio controller have a snoop control, but the recent AMD > > > > > > > > HDMI audio controller don't have the feature, thus the driver must use > > > > > > > > the non-cached pages. At least, PCI ID 1002:aaa0, aaa8 and aab0 are > > > > > > > > known to require such. > > > > > > > > > > > > > > > > Now the question is whether all new chips above (aa50,...) require the > > > > > > > > same workaround, too. Could you check this or forward the inquiry to > > > > > > > > someone in AMD? > > > > > > > > > > > > > > According to our internal teams, disabling snooping is only required on > > > > > the audio parts included in Evergreen and Northern Islands GPUs. Older chips > > > > > like R7xx (aa48) and newer chips like Southern Islands (aaa0) are able to use > > > > > snooping. I'm not real familiar with the audio portions of the GPUs so if you > > > > > need further clarification, let me know. > > > > > > > > > > > > Thanks for the information. > > > > > > > > > > > > Though, it's strange that the information doesn't match with what I've > > > > > > heard (and also with what I've tested with a laptop). I've heard that > > > > > > it's Southern Island HDMI that needs the snoop-disablement. > > > > > > > > > > > > Could you ask again whether it's really Evergreen / Nothern Islands? > > > > > > > > > > > > > > > > > > thanks, > > > > > > > > > > > > Takashi > > > > > > > > > > > > > > > > > > > > Alex > > > > > > > > > > > > > > > > > > > > > > > FWIW, such a chip needs to set AZX_DRIVER_ATIHDMI_NS bits in > > > > > > > > driver_data of pci entries in sound/pci/hda/hda_intel.c. > > > > > > > > > > > > > > > > > > > > > > > > thanks, > > > > > > > > > > > > > > > > Takashi > > > > > > > > > > > > > > > > > > > > > > > > any updates on the matter guys? > > > > > > > > > > > > Haven't heard back. I'll ping them again. > > > > > > > > Alex > > sorry for nudging, any updates? Well, what's your original issue? I wasn't in the loop from the beginning, so I don't know what is the information you need to know. If disablement of the snoop is mandatory on your board, we need to add the workaround in the driver no matter what spec says. (The datasheet is often wrong in practice :) Takashi ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
