From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Clark Dunson <cdunson@gmail.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>, alsa-devel@alsa-project.org
Subject: Re: Wolfson 5102 on Beaglebone Black using ALSA
Date: Sun, 22 May 2016 14:18:54 +0100 [thread overview]
Message-ID: <20160522131854.GT1646@localhost.localdomain> (raw)
In-Reply-To: <F5EE3526-E76D-485C-BB9C-B3A7B0DBA1F1@gmail.com>
On Tue, May 17, 2016 at 08:12:32AM -0700, Clark Dunson wrote:
> Thanks guys,
>
> Cannot thank you enough. We’ll probably go at it from both
> angles, schedule is very tight. We’ve worked with both the
> 3.18 cirrus branch, and 4.4 main line, would be so awesome if
> we could figure a way to write to the wm5102 regmap from user
> land. (Busybox i2cset is from the stone ages).
You could use debugfs, if you looking in
drivers/base/regmap/regmap-debugfs.c and change the undef to
a define for REGMAP_ALLOW_WRITE_DEBUGFS. Then you can write
registers by echoing register value pairs to the the registers
file in debugfs. Be careful though this is only intended for
testing and as the define makes all regmaps writable from
user-space depending on your system that may let you do things
that damage hardware.
Thanks,
Charles
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2016-05-22 13:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 22:16 Wolfson 5102 on Beaglebone Black using ALSA Clark Dunson
2016-05-15 10:29 ` Charles Keepax
2016-05-16 12:33 ` Peter Ujfalusi
2016-05-17 15:12 ` Clark Dunson
2016-05-22 13:18 ` Charles Keepax [this message]
2016-05-28 1:58 ` Clark Dunson
2016-05-30 8:35 ` Charles Keepax
2016-05-30 15:18 ` Clark Dunson
2016-05-30 17:19 ` Charles Keepax
2016-06-15 16:14 ` Clark Dunson
2016-06-15 16:50 ` Charles Keepax
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=20160522131854.GT1646@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=cdunson@gmail.com \
--cc=peter.ujfalusi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).