From: Mark Brown <broonie@kernel.org>
To: "Lin, Mengdong" <mengdong.lin@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>
Subject: Re: How to create a proc entry for an ASoc codec?
Date: Mon, 21 Apr 2014 23:42:10 +0100 [thread overview]
Message-ID: <20140421224210.GJ12304@sirena.org.uk> (raw)
In-Reply-To: <F46914AEC2663F4A9BB62374E5EEF8F82B3DB083@SHSMSX101.ccr.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 785 bytes --]
On Fri, Apr 11, 2014 at 09:16:03AM +0000, Lin, Mengdong wrote:
> 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?
In addition to what Liam said it's worth mentioning that due to the
deprecation of /proc most of the ASoC diagnostics are exposed via
debugfs (and for things using regmap that also has debugfs data too) -
you're likely to get much more useful information that way.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2014-04-21 22:42 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
2014-04-21 22:42 ` Mark Brown [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=20140421224210.GJ12304@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@intel.com \
--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