All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: matti.j.aaltonen@nokia.com
Cc: alsa-devel@alsa-project.org, peter.ujfalusi@nokia.com,
	lrg@slimlogic.co.uk
Subject: Re: [PATCH v2 0/1] *** SUBJECT HERE ***
Date: Thu, 22 Jul 2010 13:02:08 +0100	[thread overview]
Message-ID: <20100722120208.GF4737@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <A1C7E76B4973664FBB6C554A75234AC62BEEEB72A5@NOK-EUMSG-02.mgdnok.nokia.com>

On Thu, Jul 22, 2010 at 01:18:32PM +0200, matti.j.aaltonen@nokia.com wrote:
> From: ext Mark Brown [broonie@opensource.wolfsonmicro.com]

> >> >> +static int wl1273_set_dai_fmt(struct snd_soc_dai *codec_dai,
> >> >> +                           unsigned int fmt)
> >> >> +{
> >> >> +     return 0;
> >> >> +}

> >> >Remove unused functions.

> >> I tried leaving this out but then the codec stopped working. I guess I should
> >> mention that my test environment is 2.6.32. I'm only able to test that
> >> the codec compiles under 2.6.35. Anyway I left the function in.

> >Could you please be a little more specific - what do you mean when you
> >say "the CODEC stopped working?  The set_dai_fmt() function has always
> >been optional.

> I get this error message:

> aplay  -f dat -Dhw:wl1273 /root/sumppi.wav 
> [  297.179626] Can't set codec DAI configuration: -22
> [  297.184539] asoc: BT/FM PCM startup failed

So, obviously if your machine driver tries to configure the DAI format
on a device that doesn't support configuring the DAI format that's not
going to work.  You should just remove the attempt to do something
unsupported from the machine driver rather than adding a null function.
If there is a function there it needs to at least do validation of the
parameters.

> >So why do you believe that the soc_card driver needs to know the CODEC
> >mode?  This was the gist of my original question...

[Reflowed into 80 colummns, please fix your MUA configuration.]
> OK, sorry... The problem in a sense is that the codec supports three
> different modes: BT, FM RX and FM TX. All digital audio goes over a
> single McBSP connection. The BT part handles the audio routing, which
> is completely external to the radio driver and this codec. And the user
> of the codec is in principle responsible for keeping the codec mode in
> sync with the route setting. And the soc_card driver needs to know the
> setting also to do its thing.

Which is...

You've still not provided any information about what use this will be
put to.

  parent reply	other threads:[~2010-07-22 12:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22  9:38 [PATCH v2 0/1] *** SUBJECT HERE *** Matti J. Aaltonen
2010-07-22  9:38 ` [PATCH v2 1/1] ASoC: TI WL1273 FM Radio Codec Matti J. Aaltonen
2010-07-22  9:48 ` [PATCH v2 0/1] *** SUBJECT HERE *** Mark Brown
2010-07-22 10:57   ` Peter Ujfalusi
2010-07-22 11:02     ` Mark Brown
2010-07-22 11:07     ` Peter Ujfalusi
2010-07-22 11:30       ` Takashi Iwai
2010-07-22 12:04         ` Mark Brown
2010-07-22 11:18   ` matti.j.aaltonen
2010-07-22 11:25     ` Peter Ujfalusi
2010-07-22 11:37       ` matti.j.aaltonen
2010-07-22 12:02     ` Mark Brown [this message]
2010-07-22 12:11       ` matti.j.aaltonen
2010-07-22 13:05         ` Mark Brown
2010-07-22 14:13           ` Matti J. Aaltonen

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=20100722120208.GF4737@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=matti.j.aaltonen@nokia.com \
    --cc=peter.ujfalusi@nokia.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.