public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Lopez Cruz, Misael" <x0052729@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Nagalla, Hari" <hnagalla@ti.com>
Subject: Re: [PATCH 3/3] ASoC: TWL6030: Handle power-up seq completion thru audio interrupt
Date: Mon, 14 Sep 2009 18:33:28 +0100	[thread overview]
Message-ID: <20090914173327.GC2481@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <67059DBF19D7214F9C66BB0EA91BA90E90432709@dlee04.ent.ti.com>

On Mon, Sep 14, 2009 at 12:00:42PM -0500, Lopez Cruz, Misael wrote:

> CODEC driver starts a wait_for_completion just after calling
> external power-up callback. It's signaled as complete when
> servicing READYINT interrupt.

When you convert to registering as a normal driver you should do this
waiting before registering the CODEC and DAI with the core - that will
stop the ASoC card coming up before the CODEC is ready and means that
you don't need to have a thread sitting blocked on the startup
completing.

> MACHINE drivers should request IRQ line used in corresponding
> hardware platform and initialize workqueue and completion structs
> of twl6030_setup_data as well.

I worry what will happen when someone builds a machine which doesn't
bother hooking up the interrupt line - is it possible to poll for
completion of startup if no interrupt is provided?  If they aren't using
the jack and accessory detect functionality I can see someone not
bothering to hook it up.  OTOH that could always be added later on if
required.

      reply	other threads:[~2009-09-14 17:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 17:00 [PATCH 3/3] ASoC: TWL6030: Handle power-up seq completion thru audio interrupt Lopez Cruz, Misael
2009-09-14 17:33 ` Mark Brown [this message]

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=20090914173327.GC2481@rakim.wolfsonmicro.main \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=hnagalla@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=x0052729@ti.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