From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Scott Jiang <scott.jiang.linux@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
uclinux-dist-devel@blackfin.uclinux.org,
alsa-devel@alsa-project.org
Subject: Re: snd soc spi read/write
Date: Wed, 10 Aug 2011 01:04:48 +0900 [thread overview]
Message-ID: <20110809160447.GM15861@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAHG8p1AG2mteW0Bw6ScHCsM5okLr7Vd7Hqy=T8zz+C746qpn+g@mail.gmail.com>
On Tue, Aug 09, 2011 at 11:41:30AM +0800, Scott Jiang wrote:
> There are three methods:
> 1. pass different registers to snd_soc_read and snd_soc_write. But
> snd_kcontrol and snd_soc_dapm_widget can't work because I pass only
> one register.
> 2. deal with this bit in hw_read, but this will be deprecated by
> others whose chip doesn't have this bit.
> 3. I'd like to use SND_SOC_CUS type, but it has been removed since
> linux 3.0. I suggest we can reserve this type, considering SPI is a
> simple "de facto" standard.
No, like I say we just need to teach regmap about this stuff. It's not
that odd, it's just your hardware designers seem to want to consume
extra bandwidth on the control bus for some reason AFAICT as it looks
like all the registers are 0x8xx.
next prev parent reply other threads:[~2011-08-09 16:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 10:24 snd soc spi read/write Scott Jiang
2011-08-04 10:35 ` Mark Brown
2011-08-05 2:24 ` Scott Jiang
2011-08-05 5:42 ` Mark Brown
2011-08-05 6:26 ` Scott Jiang
2011-08-05 6:34 ` Mark Brown
[not found] ` <CAHG8p1BBza_M_Cgrq2O2U+Xc-=rPHeNBKMD_KwfZsLX5Npz9jA@mail.gmail.com>
[not found] ` <20110805072908.GA28149@opensource.wolfsonmicro.com>
2011-08-05 8:00 ` Scott Jiang
2011-08-05 8:30 ` Mark Brown
2011-08-09 3:41 ` Scott Jiang
2011-08-09 16:04 ` Mark Brown [this message]
2011-08-10 11:54 ` Takashi Iwai
2011-08-10 14:55 ` Mark Brown
2011-08-10 15:00 ` Takashi Iwai
2011-08-10 15:03 ` Mark Brown
2011-08-10 15:15 ` Takashi Iwai
2011-08-10 15:34 ` Mark Brown
2011-08-10 16:02 ` Takashi Iwai
2011-08-11 3:17 ` Mark Brown
2011-08-10 21:31 ` Lars-Peter Clausen
2011-08-11 0:33 ` Mark Brown
2011-08-11 1:50 ` Lars-Peter Clausen
2011-08-11 2:46 ` Mark Brown
2011-08-11 3:09 ` Lars-Peter Clausen
2011-08-11 5:32 ` Mark Brown
2011-08-11 6:41 ` Lars-Peter Clausen
2011-08-17 9:16 ` Dimitris Papastamos
2011-08-05 6:11 ` Takashi Iwai
2011-08-05 6:21 ` Takashi Iwai
2011-08-05 6:27 ` 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=20110809160447.GM15861@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=scott.jiang.linux@gmail.com \
--cc=tiwai@suse.de \
--cc=uclinux-dist-devel@blackfin.uclinux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox