linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
Cc: alsa-devel@alsa-project.org, "Cousson, Benoit" <b-cousson@ti.com>,
	Brown <broonie@opensource.wolfsonmicro.com>,
	"Guiriec, Sebastien" <s-guiriec@ti.com>,
	"Lopez Cruz, Misael" <misael.lopez@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Girdwood, Liam" <lrg@ti.com>
Subject: Re: Re: [alsa-devel] [PATCH 0/4] ASoC: OMAP4: McPDM: Fix legacy support
Date: Fri, 19 Aug 2011 16:04:20 +0300	[thread overview]
Message-ID: <20110819130420.GF4996@atomide.com> (raw)
In-Reply-To: <2097801.ze7cveM5xx@barack>

* Péter Ujfalusi <peter.ujfalusi@ti.com> [110815 13:56]:
> Hi Tony,
> 
> On Tuesday 09 August 2011 09:27:17 Ujfalusi, Peter wrote:
> > Hi Tony,
> > 
> > On Tuesday 02 August 2011 13:34:13 Ujfalusi, Peter wrote:
> > > Hello,
> > > 
> > > The OMAP4 McPDM driver in upstream has been broken for some time...
> > > This series fixes that, and enables basic audio playback/capture over
> > > the
> > > mcpdm interface.
> > 
> > Would you have time to look at this series?
> > Specially patch 1 (maybe 2 as well).
> > We are planning to send this series through audio for 3.1.
> 
> Do you have time to look at this series.
> Currently the mcpdm (omap4 audio) is broken in upstream without this series, 
> and I'd like to have it fixed in time for 3.1.

It seems OK to me. But for the -rc cycle it has potential for
"fixes for features that never worked" flame bait. If you guys
are OK to deal with that then go ahead.

Regards,

Tony
--
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-08-19 13:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02 11:34 [PATCH 0/4] ASoC: OMAP4: McPDM: Fix legacy support Peter Ujfalusi
2011-08-02 11:34 ` [PATCH 1/4] OMAP: McPDM: Convert McPDM device to omap_device Peter Ujfalusi
2011-08-19 13:02   ` Tony Lindgren
2011-08-02 11:34 ` [PATCH 2/4] OMAP4: hwmod: enable mcpdm hwmod device Peter Ujfalusi
2011-08-19 13:02   ` Tony Lindgren
2011-08-02 11:34 ` [PATCH 3/4] ASoC: omap-mcpdm: Fix threshold and dma configuration Peter Ujfalusi
2011-08-02 15:50   ` Mark Brown
2011-08-02 11:34 ` [PATCH 4/4] ASoC: OMAP4: McPDM: Convert to hwmod/omap_device Peter Ujfalusi
2011-08-02 16:07   ` Mark Brown
2011-08-03  7:58   ` [alsa-devel] " Péter Ujfalusi
2011-08-09  7:27 ` [alsa-devel] [PATCH 0/4] ASoC: OMAP4: McPDM: Fix legacy support Péter Ujfalusi
2011-08-15 11:28   ` Péter Ujfalusi
2011-08-19 13:04     ` Tony Lindgren [this message]
2011-08-22  7:13       ` Re: Re: [alsa-devel] " Péter Ujfalusi
2011-08-22  7:38         ` Liam Girdwood

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=20110819130420.GF4996@atomide.com \
    --to=tony@atomide.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=peter.ujfalusi@ti.com \
    --cc=s-guiriec@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;
as well as URLs for NNTP newsgroup(s).