From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Patrick Lai <plai@codeaurora.org>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
Liam Girdwood <lrg@ti.com>,
brubin@codeaurora.org
Subject: Re: ASoC Peek individual register debugfs
Date: Sat, 23 Jul 2011 07:44:13 +0100 [thread overview]
Message-ID: <20110723064412.GA31413@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4E29C6FC.6060801@codeaurora.org>
On Fri, Jul 22, 2011 at 11:52:44AM -0700, Patrick Lai wrote:
> On 7/22/2011 2:07 AM, Mark Brown wrote:
> >codec_reg. This is the sort of question that can easily be answered by
> >looking at the code, or a running system.
> I checked soc-core.c on Linux next and I do not believe there is
> such debugfs interface. Here is the interface proposal.
> By default, cat codec_reg prints entire register dump
> If someone echo "<register_addr>" > codec_reg before running
> cat codec_reg, only register address and value of given register
> would be printed. Afterward, state gets reset. Entire register dump
> gets printed if user cat codec_reg again
No, that's bad as it means you can rely on the behaviour of the existing
file. Just use codec_reg, it already does what you need - if you look
at the code you'll see that it only displays the registers you actually
read from it and since the registers are displayed in a fixed length
format they'll always appear at a consistent place in the file.
prev parent reply other threads:[~2011-07-23 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 0:33 ASoC Peek individual register debugfs Patrick Lai
2011-07-22 9:07 ` Mark Brown
2011-07-22 18:52 ` Patrick Lai
2011-07-23 6:44 ` 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=20110723064412.GA31413@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=brubin@codeaurora.org \
--cc=lrg@ti.com \
--cc=plai@codeaurora.org \
/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.