From: Takashi Iwai <tiwai@suse.de>
To: "rander.wang" <rander.wang@linux.intel.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: HDAudio and pulse audio
Date: Sun, 28 Apr 2019 09:51:22 +0200 [thread overview]
Message-ID: <s5h36m2muth.wl-tiwai@suse.de> (raw)
In-Reply-To: <ca0ffa32-dc13-6fbf-42d7-65ee7879f681@linux.intel.com>
On Thu, 25 Apr 2019 10:50:32 +0200,
rander.wang wrote:
>
> Hi all,
>
> I am working on sound open firmware in ASoC to enable HDAudio
> with pulse audio in ubuntu.
> There is a HDAudio codec driver hdac_hda.c in ASoC, which
> invokes HDAudio functions defined
> in sound/pci/hda, for ASoC to utilize the HDAudio codec. Now I
> get a issue: pulse audio can't detect
> headphone pluged or not.
>
> Could anyone help to tell me about Jack detection flow in
> HDAudio and how does HDAudio
> work with pulse audio ? Does HDAudio report a event to pulse
> audio when headphone detected ?
> As I know, ASoC codec driver would invoke snd_soc_jack_report
> to notify user mode, how about HDAudio
> driver ?
PA only sees the "XXX Jack" ALSA control notification, IIRC.
And these controls are created by the HD-audio codec driver, and
driven by the HD-audio unsolicited events.
So first off, check whether the jack detection really works on your
chip by issuing the raw HD-audio verbs. If it's properly detected,
check whether the unsolicited events are issued and processed. Then
follow the code and see whether the "* Jack" control change is
invoked.
HTH,
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2019-04-28 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 8:50 HDAudio and pulse audio rander.wang
2019-04-28 7:51 ` Takashi Iwai [this message]
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=s5h36m2muth.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=rander.wang@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.