All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Lai <plai@codeaurora.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	Liam Girdwood <lrg@ti.com>,
	brubin@codeaurora.org
Subject: Re: ASoC Peek individual register debugfs
Date: Fri, 22 Jul 2011 11:52:44 -0700	[thread overview]
Message-ID: <4E29C6FC.6060801@codeaurora.org> (raw)
In-Reply-To: <20110722090757.GG23192@opensource.wolfsonmicro.com>

On 7/22/2011 2:07 AM, Mark Brown wrote:
> On Thu, Jul 21, 2011 at 05:33:07PM -0700, Patrick Lai wrote:
>
>> Does latest soc-core.c provide debugfs interface for peeking individual
>> register? If not, I plan to add this interface.
>
> 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

Please let me know if the proposal is not appropriate. Otherwise,
I will start implementation going by proposed interface.

Thanks
Patrick

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2011-07-22 18:52 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 [this message]
2011-07-23  6:44     ` 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=4E29C6FC.6060801@codeaurora.org \
    --to=plai@codeaurora.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=brubin@codeaurora.org \
    --cc=lrg@ti.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.