From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/1 - try2] ASoC: add support for multiple cards/codecs in debugfs
Date: Thu, 1 Oct 2009 11:51:07 +0100 [thread overview]
Message-ID: <20091001105107.GB19998@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1254382367-27948-2-git-send-email-peter.ujfalusi@nokia.com>
On Thu, Oct 01, 2009 at 10:32:47AM +0300, Peter Ujfalusi wrote:
> In order to support multiple codecs on the same system in the debugfs
> the directory hierarchy need to be changed by adding directory per codec
> under the asoc direcorty:
> debugfs/asoc/{dev_name(socdev->dev)}-{codec->name}/codec_reg
I'd rather use dev_name() for the CODEC itself if possible, that is more
likely to be stable going forward and one of the immediate aims with the
API refactoring is to remove socdev entirely at runtime.
That can be done in a followup, though.
> @@ -126,7 +126,7 @@ static int soc_pcm_apply_symmetry(struct snd_pcm_substream *substream)
>
> if (codec_dai->symmetric_rates || cpu_dai->symmetric_rates ||
> machine->symmetric_rates) {
> - dev_dbg(card->dev, "Symmetry forces %dHz rate\n",
> + dev_dbg(card->dev, "Symmetry forces %dHz rate\n",
> machine->rate);
>
> ret = snd_pcm_hw_constraint_minmax(substream->runtime,
but this doesn't seem to accomplish that goal? I can't actually spot
the difference either, I'm assuming it's just whitespace? If so I'll
apply as-is.
next prev parent reply other threads:[~2009-10-01 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 7:32 [PATCH 0/1 - try2] ASoC: debugfs support improvement Peter Ujfalusi
2009-10-01 7:32 ` [PATCH 1/1 - try2] ASoC: add support for multiple cards/codecs in debugfs Peter Ujfalusi
2009-10-01 10:51 ` Mark Brown [this message]
2009-10-01 11:02 ` Peter Ujfalusi
2009-10-01 11:09 ` Mark Brown
2009-10-01 13:49 ` Peter Ujfalusi
2009-10-01 14:06 ` Mark Brown
2009-10-01 11:19 ` Mark Brown
2009-10-01 13:06 ` Peter Ujfalusi
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=20091001105107.GB19998@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=peter.ujfalusi@nokia.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.