public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "Girdwood, Liam" <lrg@ti.com>, Tony Lindgren <tony@atomide.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Lopez Cruz, Misael" <misael.lopez@ti.com>,
	"Guiriec, Sebastien" <s-guiriec@ti.com>,
	"Cousson, Benoit" <b-cousson@ti.com>
Subject: Re: Re: [PATCH 1/3] ASoC: omap-mcpdm: Replace legacy driver
Date: Fri, 8 Jul 2011 18:02:26 +0300	[thread overview]
Message-ID: <2323058.DqPoNzVktU@barack> (raw)
In-Reply-To: <20110708083733.GA18860@opensource.wolfsonmicro.com>

On Friday 08 July 2011 16:28:05 Mark Brown wrote:
> > It's not that simple in this situation. We also have a PM dependency on
> > the CODEC here too, it supplies our interface clock via the DAI so we
> > have to be very careful how we interact with the ABE and CODEC. The
> > critical thing here is the pop reduction and a subsequent ABE patch will
> > also introduce some hard timing constraints here too.
> 
> This definitely feels like it needs sorting in a better way than just
> inserting random delays into drivers

I agree, there should be a better way to handle this.

> the clocking dependencies are far
> from unique, for example, and would normally be managed by the machine
> drivers with the current infrastructure.

Sort of yes, but as soon as we have more devices, we will need either ways in 
the core, or some common file to handle the clocking, startup, and other 
dependencies between McPDM and the twl6040 - I'm completely ignoring the ABE 
here.
BTW: what infrastructure you are suggesting?

> Right now it's all sounding
> far too fragile due to the lack of any explicit indication of what's
> going on and the fact that things are going to be spread over a bunch of
> different drivers.

Agreed, but... if we handle the McPDM stop start from the outside, will it 
help? I mean we need to keep on eye what the twl6040 is doing, and do things 
accordingly within the McPDM.
 
> If we just insert random delays into the drivers the chances of anyone
> understanding what the code is supposed to be doing in the future seem
> low which isn't going to be nice when people do different designs.

Again: agreed.
Unfortunately this cleanup work has to wait, since at least I'm going for a 
holiday.

Another, not directly related thing is that with this driver in place at least 
one can play audio on OMAP4 with upstream kernel (through McPDM, and without 
ABE).

This area is still work in progress, but I prefer to start from something, 
which shows some sign of life.

-- 
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-07-08 15:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 12:27 [PATCH 0/3] OMAP4/ASoC: New McPDM driver Peter Ujfalusi
2011-07-07 12:27 ` [PATCH 1/3] ASoC: omap-mcpdm: Replace legacy driver Peter Ujfalusi
2011-07-07 15:57   ` Mark Brown
2011-07-07 16:32     ` Liam Girdwood
2011-07-07 16:53       ` Mark Brown
2011-07-07 17:19         ` Péter Ujfalusi
2011-07-07 19:55         ` Liam Girdwood
2011-07-08 14:28           ` Mark Brown
2011-07-08 15:02             ` Péter Ujfalusi [this message]
2011-07-09  1:08               ` Mark Brown
2011-07-12 19:35                 ` Péter Ujfalusi
2011-07-12 23:25                   ` Mark Brown
2011-07-07 12:27 ` [PATCH 2/3] OMAP: McPDM: Convert McPDM device to omap_device Peter Ujfalusi
2011-07-07 15:58   ` Mark Brown
2011-07-07 12:27 ` [PATCH 3/3] OMAP4: hwmod: enable mcpdm hwmod device Peter Ujfalusi
2011-07-07 15:58   ` Mark Brown
2011-07-26 13:46   ` Cousson, Benoit

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=2323058.DqPoNzVktU@barack \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=b-cousson@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=misael.lopez@ti.com \
    --cc=s-guiriec@ti.com \
    --cc=tony@atomide.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