All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jarkko Nikula <jhnikula@gmail.com>
Cc: alsa-devel@alsa-project.org,
	Peter Ujfalusi <peter.ujfalusi@nokia.com>,
	Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: omap: rx51: Add stereo output support to audio jack
Date: Wed, 5 Jan 2011 16:39:00 +0000	[thread overview]
Message-ID: <20110105163900.GD746@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110105182924.cf90b12c.jhnikula@gmail.com>

On Wed, Jan 05, 2011 at 06:29:24PM +0200, Jarkko Nikula wrote:
> Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:

> > Having thought about it for at least a second I think we should have a
> > DAPM context in the cards for all the board-level stuff - does that seem
> > resonable?  The patch itself looks good:

> I don't know. Probably it would be good if machine widgets are in own
> context. Like having own debugfs/sysfs directory for them etc.

Yes, exactly.

> In this case it would be just enough if the tpa6130 is a codec driver
> having DAPM widgets. Then machine driver wouldn't need any these
> exported special tpa6130a2_ functions and soc-dapm could take care of
> power changes according to audio map and other info.

> But as far as I understood there's no any better way to get rid of pops
> in tpa6130a2.

As far as I remember from the previous discussion that had been that
making it a CODEC driver would be the simplest thing.  Peter said in
reply to my mail saying this:

| At least with my device I need to add some delay before enabling the amp, so
| anyway I need to ahve the DAPM_HP in the machine driver.

but it'd seem that the amp driver could do this just as well, possibly
based off platform data?

  reply	other threads:[~2011-01-05 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05 15:46 [PATCH] ASoC: omap: rx51: Add stereo output support to audio jack Jarkko Nikula
2011-01-05 15:55 ` Mark Brown
2011-01-05 16:29   ` Jarkko Nikula
2011-01-05 16:39     ` Mark Brown [this message]
2011-01-05 18:12       ` peter.ujfalusi

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=20110105163900.GD746@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jhnikula@gmail.com \
    --cc=lrg@slimlogic.co.uk \
    --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.