Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: uclinux-dist-devel@blackfin.uclinux.org, alsa-devel@alsa-project.org
Subject: Re: [Uclinux-dist-devel] [PATCH 2/2] ASoC: Blackfin AD1836/AD1938 machine drivers: require SPI master
Date: Thu, 8 Oct 2009 11:01:36 +0100	[thread overview]
Message-ID: <20091008100135.GA9053@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <8bd0f97a0910071727x72fe950x804f295ba25d514c@mail.gmail.com>

On Wed, Oct 07, 2009 at 08:27:56PM -0400, Mike Frysinger wrote:

> i dont think the soc-cache could be used currently by the ad1836 as it
> doesnt use a 7/9 split with the address/data.  it uses like 6/10 (4
> addr bits, one bit for read/write, one bit is always 0, and 10 data
> bits).  guessing the write bit can be considered part of the addr as
> the read always comes from the cache, but that still gives us 5/10
> split.  maybe a new 6/10 set of funcs should be added ...

That's the idea - add new functions for any new register formats.

> snd_soc_7_9_write() looks like it does a little more bit work than it
> needs to ?  if data is declared as a u16, then you have:
> u16 data = (reg << 9) | (value & 0x01ff);
> this is what the ad1836 driver does now for its data split.

Probably.  I'd need to check but I believe that's there to handle
endianness variations in the host, though a cpu_to_ in what you have
above ought to be able to take care of that.  The code was cut'n'pasted
from what was in the drivers already.

> in the mean time, rather than adding #ifdef to the codec driver, we
> could create a local header like "bus-stubs.h" that stubs all the
> relevant functions to an error value.  then all codec drivers that
> dont use soc-cache can use that instead and the only change needed is
> to add:
> #include "bus-stubs.h"

I'm not sure I feel up to doing that locally in ASoC rather than in the
relevant subsystems.

  reply	other threads:[~2009-10-08 10:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-06  5:51 [PATCH 1/2] ASoC: AD1980/AD73311: make sure to set dev member Mike Frysinger
2009-10-06  5:51 ` [PATCH 2/2] ASoC: Blackfin AD1836/AD1938 machine drivers: require SPI master Mike Frysinger
2009-10-06  9:33   ` Mark Brown
     [not found]     ` <20091006093325.GA10118-HF5t3jzXg/6ND3a5+9QAFujbO/Zr0HzV@public.gmane.org>
2009-10-06  9:41       ` Mike Frysinger
2009-10-06  9:50         ` [Uclinux-dist-devel] " Mark Brown
2009-10-06 10:00           ` Mike Frysinger
2009-10-06 10:39             ` Mark Brown
2009-10-06 11:32               ` Mike Frysinger
2009-10-06 11:52                 ` Mark Brown
2009-10-06 21:09                   ` Mike Frysinger
2009-10-06 22:07                     ` Mark Brown
2009-10-07  8:32                       ` Mike Frysinger
2009-10-07 10:19                         ` Mark Brown
2009-10-08  0:27                           ` Mike Frysinger
2009-10-08 10:01                             ` Mark Brown [this message]
2009-10-09  0:01                               ` Mike Frysinger
2009-10-10  3:47                               ` Barry Song
     [not found]                                 ` <3c17e3570910092047n39db1ac9vfe76b9304897a794-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-10 11:11                                   ` [alsa-devel] " Mark Brown
     [not found] ` <1254808311-3594-1-git-send-email-vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2009-10-06  9:42   ` [alsa-devel] [PATCH 1/2] ASoC: AD1980/AD73311: make sure to set dev member Mark Brown
2009-10-06  9:59     ` [Uclinux-dist-devel] " Mike Frysinger

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=20091008100135.GA9053@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=vapier.adi@gmail.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