All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ola Lilja <ola.o.lilja@stericsson.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Liam Girdwood <lrg@ti.com>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 10/11] ASoC: codecs: Add AB8500 codec-driver
Date: Wed, 9 May 2012 11:51:00 +0100	[thread overview]
Message-ID: <20120509105059.GF3955@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FAA3440.7070600@stericsson.com>


[-- Attachment #1.1: Type: text/plain, Size: 1820 bytes --]

On Wed, May 09, 2012 at 11:09:20AM +0200, Ola Lilja wrote:
> On 05/09/2012 10:33 AM, Mark Brown wrote:
> > On Wed, May 09, 2012 at 09:48:35AM +0200, Ola Lilja wrote:

> > Please don't just ignore review and continue to submit the same stuff
> > unless there's been clear discussion that what's happening is actually
> > OK.

> I wasn't aware of that the comment with | above was a show-stopper since I
> explained before why we need to do it. I wasn't either aware that you meant that
> I should just move it to the machine-driver. Furthermore, I didn't want to spam
> to much comments each time.

At the very least this should go in the machine driver, though I have to
say I remain very much unsure that this needs to be directly controlled
from the application layer at all.

> >> >> +int ab8500_audio_setup_if1(struct snd_soc_codec *codec,
> >> >> +			unsigned int fmt,
> >> >> +			unsigned int wl,
> >> >> +			unsigned int delay)

> >> > Why is this not static?

> >> Because it is called from the machine-driver.

> > Why?  No other driver does this...

> This is setting up an I2S-interface connected directly to another chip for
> FM-radio. It is not triggered by opening an ALSA-device. How/where do you want
> me to do this?

Once again, work with the frameworks not against or around them.
Whenever you find yourself putting in a custom device specific API
that's externally visible this should be a warning sign.

In this case there's nothing unusual here, it's exactly the same as the
connection to a digital baseband or back to back link to another CODEC.
The CODEC driver should just provide a DAI and let the framework connect
it up, currently that should be with a CODEC<->CODEC link though older
systems use a bodge where the link is described as a normal PCM.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2012-05-09 13:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 13:57 [PATCH 10/11] ASoC: codecs: Add AB8500 codec-driver Ola Lilja
2012-05-08 18:27 ` Mark Brown
2012-05-09  7:48   ` Ola Lilja
2012-05-09  8:33     ` Mark Brown
2012-05-09  9:09       ` Ola Lilja
2012-05-09 10:51         ` Mark Brown [this message]
2012-05-23  7:04   ` Ola Lilja
2012-05-23 17:40     ` Mark Brown
2012-05-24  6:21       ` Ola Lilja
2012-05-24 10:33         ` 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=20120509105059.GF3955@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linus.walleij@linaro.org \
    --cc=lrg@ti.com \
    --cc=ola.o.lilja@stericsson.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.