All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Matti J. Aaltonen" <matti.j.aaltonen@nokia.com>
Cc: alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Re: [PATCH v2 0/1] *** SUBJECT HERE ***
Date: Thu, 22 Jul 2010 10:48:32 +0100	[thread overview]
Message-ID: <20100722094832.GC4737@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1279791534-20028-1-git-send-email-matti.j.aaltonen@nokia.com>

On Thu, Jul 22, 2010 at 12:38:53PM +0300, Matti J. Aaltonen wrote:

> > My major comment about this driver is that it'd probably make sense to
> > redo it on top of Liam's multi-component branch, though it shouldn't be
> > a pressing concern for merge.

> I didn't do this yet. But could you give me the git URL and then I'll resend?

git://git.kernel.org/pub/scm/linux/kernel/git/lrg/sound-2.6.git

> > Wouldn't it be nicer to do this stuff with the ALSA constraint APIs
> > rather than futzing with the constant data?

> I principle I of course agree. But it seems - also discussed with the local
> ALSA specialist - that using static constraints does not work here.
> HALF_DUPLEX is not one of the SNDRV_PCM_HW_PARAM_'s... or something like that.
> As a ALSA non-specialist I'd be willing to this leave as it is...

Could you please get whoever the expert is to get involved in this
thread?  If this is not currently possible it should probably be.

> >> +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.

> >> +enum wl1273_mode wl1273_get_codec_mode(struct snd_soc_codec *codec)
> >> +{
> >> +     struct wl1273_priv *wl1273 = snd_soc_codec_get_drvdata(codec);
> >> +     return wl1273->mode;
> >> +}
> >> +EXPORT_SYMBOL_GPL(wl1273_get_codec_mode);

> > Why is this being exported?

> This is because the soc_card driver needs to know the codec mode and accessing
> the internals of the codec struct is ugly.

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

  parent reply	other threads:[~2010-07-22  9:48 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 ` Mark Brown [this message]
2010-07-22 10:57   ` [PATCH v2 0/1] *** SUBJECT HERE *** 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
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=20100722094832.GC4737@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 \
    /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.