From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: "Lin, Mengdong" <mengdong.lin@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: How to create a proc entry for an ASoc codec?
Date: Fri, 11 Apr 2014 10:28:47 +0100 [thread overview]
Message-ID: <1397208527.2406.24.camel@loki> (raw)
In-Reply-To: <F46914AEC2663F4A9BB62374E5EEF8F82B3DB083@SHSMSX101.ccr.corp.intel.com>
On Fri, 2014-04-11 at 10:16 +0100, Lin, Mengdong wrote:
> Hi,
>
>
>
> How to create a proc entry for an ASoc codec under the sound card?
>
>
>
> We hope to create an proc entry for an I2S codec
> under /proc/asound/cardx, to debug the codec status at runtime.
>
>
>
> So after the machine driver calls snd_soc_register_card(&soc_card), I
> calls snd_card_proc_new(soc_card .snd_card, ….)
>
> But no codec entry is created although dmesg shows this function
> succeeds.
>
> How ASoC creates the proc entries such as ‘id’ for the sound card?
>
You should see this :-
cat /proc/asound/card0/id
broadwellrt286
ASoC exposes sound card specific data under the sysfs entry for the
device. e.g.
ls /sys/bus/platform/devices/broadwell-audio/
Capture PCM/ driver/ modalias Offload1/ sound/ System PCM/
Codec/ Loopback PCM/ Offload0/ power/ subsystem/ uevent
Liam
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2014-04-11 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 9:16 How to create a proc entry for an ASoc codec? Lin, Mengdong
2014-04-11 9:28 ` Liam Girdwood [this message]
2014-04-21 22:42 ` Mark Brown
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=1397208527.2406.24.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=mengdong.lin@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