linux-omap.vger.kernel.org archive mirror
 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: Re: [PATCH 1/3] ASoC: omap-mcpdm: Replace legacy driver
Date: Tue, 12 Jul 2011 22:35:53 +0300	[thread overview]
Message-ID: <4479173.gaSts1MLKP@barack> (raw)
In-Reply-To: <20110709010808.GC18860@opensource.wolfsonmicro.com>

On Saturday 09 July 2011 03:08:10 Mark Brown wrote:
> I've got a few ideas but nothing comprehensive right now; the main thing
> I can think we're missing at the minute is more fine grained hooks
> around stream start in order to allow things to clock off the audio
> stream.  Equally well none of the systems I've had to deal with have had
> a particularly pressing problem here.

Yeah, this is the first system if this kind I've seen as well. Anyway, we have 
these constraints, and these might come back in other designs in the future.
We will be looking for better/cleaner way to handle this.

> If the machine driver controls the system integration (as we're doing
> for everything else) it's at least clear what's going on for this
> particular system.  My main concern here is making the code actually say
> what's going on.

Fair enough.

> Could we split the rewrite out from the delay thing so we can review it
> separately?  This'd also be good from the point of view of documentation
> of what's going on as the changelogs would provide a bit more details.

Just to avoid confusion (in my part): if I split this patch to one big + 
several small incremental patches, which eventually lead to the current 
situation is what you were asking for?
With the patches I can document the reasoning behind the non standard 
workarounds. Probably if we see them spread out, we might be able to find 
better ways for them...

-- 
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-12 19:36 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
2011-07-09  1:08               ` Mark Brown
2011-07-12 19:35                 ` Péter Ujfalusi [this message]
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=4479173.gaSts1MLKP@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;
as well as URLs for NNTP newsgroup(s).