From: Takashi Iwai <tiwai@suse.de>
To: Paul Menzel <pmenzel+alsa-devel@molgen.mpg.de>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: azx_probe() called twice
Date: Wed, 25 Apr 2018 14:34:46 +0200 [thread overview]
Message-ID: <s5hpo2njwgp.wl-tiwai@suse.de> (raw)
In-Reply-To: <96db5a48-418e-3344-ef0d-99e6180cebfe@molgen.mpg.de>
On Wed, 25 Apr 2018 14:29:31 +0200,
Paul Menzel wrote:
>
> Dear Takashi,
>
>
> On 04/25/18 13:58, Takashi Iwai wrote:
> > On Wed, 25 Apr 2018 13:48:27 +0200, Paul Menzel wrote:
>
> >> With the attached debug patch, `azx_probe()` seems to have been called
> >> twice on the ASRock E350M1. Is that expected? It also differs, that
> >> it’s only called once during some boots, and twice during others.
> >
> > How many HD-audio devices does it have?
>
> I’d say one (ALC892), but how do I verify that?
I meant HD-audio controllers.
> Please find lspci and
> Linux logs attached from an older boot with Linux 4.11.
....
> 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler HDMI Audio
....
> 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40)
So you have two HD-audio controllers (one for HDMI/DP and another for
Realtek codec). It's expected behavior that azx_probe() gets called
twice.
Takashi
next prev parent reply other threads:[~2018-04-25 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 11:48 Paul Menzel
2018-04-25 11:58 ` Takashi Iwai
2018-04-25 12:29 ` Paul Menzel
2018-04-25 12:34 ` Takashi Iwai [this message]
2018-04-25 12:38 ` Probe HD-audio devices in parallel (was: azx_probe() called twice) Paul Menzel
2018-04-25 13:42 ` Takashi Iwai
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=s5hpo2njwgp.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel+alsa-devel@molgen.mpg.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
all inboxes | Powered by JetHome®