From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
General PulseAudio Discussion
<pulseaudio-discuss@lists.freedesktop.org>,
Vinod Koul <vinod.koul@intel.com>,
"han.lu" <han.lu@linux.intel.com>,
Linux Upstreaming Team <linux@endlessm.com>
Subject: Re: [alsa-devel] ASoC and pulseaudio
Date: Wed, 16 Mar 2016 16:17:02 +0100 [thread overview]
Message-ID: <s5hwpp2bggh.wl-tiwai@suse.de> (raw)
In-Reply-To: <20160316150949.GX2566@sirena.org.uk>
On Wed, 16 Mar 2016 16:09:49 +0100,
Mark Brown wrote:
>
> On Wed, Mar 16, 2016 at 08:27:04PM +0530, Vinod Koul wrote:
>
> > So I don't think FW name would help, if required we should add dev_info
> > to print the firmware which is getting loaded.
>
> We can't really be relying on userspace trawling through the logs -
> quite apart from anything else the message might be long gone by the
> time the relevant program gets started.
>
> Might be an idea to record it in sysfs somewhere?
Yeah, that should be feasible. Also, there is a "component" field
assigned to the card. This is supposed to be referred by user-space
as additional information. See snd_component_add().
Takashi
_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
next prev parent reply other threads:[~2016-03-16 15:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL9uMOHRjcCJomr6zzR0ySh384AVj1FRvASZSp3KsPqfeS8Lzw@mail.gmail.com>
[not found] ` <56C8AEFD.4060808@linux.intel.com>
[not found] ` <1456225994.6424.35.camel@loki>
[not found] ` <B51200AC81AB024499A3C2C9A1BB90A83D3AABF9@SHSMSX101.ccr.corp.intel.com>
2016-03-14 8:19 ` ASoC and pulseaudio Liam Girdwood
2016-03-14 15:23 ` [alsa-devel] " Pierre-Louis Bossart
2016-03-14 16:06 ` Mark Brown
2016-03-15 6:01 ` Liam Girdwood
2016-03-15 8:45 ` Mark Brown
2016-03-15 8:55 ` Takashi Iwai
2016-03-15 9:48 ` Liam Girdwood
2016-03-15 9:56 ` Takashi Iwai
2016-03-15 10:58 ` Liam Girdwood
2016-03-16 14:57 ` [pulseaudio-discuss] " Vinod Koul
2016-03-16 15:09 ` [alsa-devel] " Mark Brown
2016-03-16 15:17 ` Takashi Iwai [this message]
2016-03-16 15:53 ` [pulseaudio-discuss] " Vinod Koul
2016-03-16 17:59 ` [alsa-devel] " Liam Girdwood
2016-03-17 11:23 ` [pulseaudio-discuss] " Lu, Han
2016-03-17 11:28 ` [alsa-devel] " Lu, Han
2016-03-17 16:29 ` Vinod Koul
2016-03-16 17:58 ` Liam Girdwood
2016-03-16 17:57 ` Liam Girdwood
2016-03-15 10:00 ` Mark Brown
2016-03-15 10:48 ` [alsa-devel] " Liam Girdwood
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=s5hwpp2bggh.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=han.lu@linux.intel.com \
--cc=linux@endlessm.com \
--cc=pulseaudio-discuss@lists.freedesktop.org \
--cc=vinod.koul@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 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).