public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Igor Stoppa <igor.stoppa@nokia.com>
Cc: me@felipebalbi.com, Eduardo Valentin <edubezval@gmail.com>,
	linux-omap@vger.kernel.org,
	Eduardo Valentin <eduardo.valentin@indt.org.br>,
	ext Chandra shekhar <x0044955@ti.com>
Subject: Re: [PATCH 0/5] Updates on mcbsp driver
Date: Thu, 24 Apr 2008 14:45:46 -0700	[thread overview]
Message-ID: <20080424214544.GP16834@atomide.com> (raw)
In-Reply-To: <1209071583.30582.186.camel@mort>

* Igor Stoppa <igor.stoppa@nokia.com> [080424 14:20]:
> On Fri, 2008-04-25 at 00:10 +0300, ext Felipe Balbi wrote:
> > On Thu, Apr 24, 2008 at 11:54:20AM -0400, Eduardo Valentin wrote:
> > > From: Eduardo Valentin <eduardo.valentin@indt.org.br>
> > > 
> > > This patch series updates mcbsp driver by transforming it into
> > > a platform driver. This is a very initial implementation.
> > > Basically it moves machine specific code to their correct place
> > > and creates the platform driver necessary structures.
> > > 
> > > It must be working for previous boards. For omap34xx it should
> > > work for mcbsp 1 and 2.
> > > 
> > > In order to do not break other places, I tryied to do not change
> > > previous API. But future improvements are needed.
> > > 
> > > Clock definitions for  mcbsp 1 and 2 were also modified to add
> > > correct support for omap34xx.
> > > 
> > > Comments are wellcome.
> > 
> > checkpatch doesn't complain, although i didn't really test it.
> 
> However I'd prefer see this patchset being merged with
> 
> [RFC/PATCH  1/1] McBSP support for 2430/34XX
> 
> and only later considered for integration.

Yeah, Chandra and Eduardo, can you guys put together a merged series
of patches?

Tony

  reply	other threads:[~2008-04-24 21:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 15:54 [PATCH 0/5] Updates on mcbsp driver Eduardo Valentin
2008-04-24 15:54 ` [PATCH 1/5] PLAT-OMAP: MCBSP: Tranform into platform driver Eduardo Valentin
2008-04-24 15:54   ` [PATCH 2/5] MACH-OMAP1: MCBSP: Add support for mcbsp on mach-omap1 Eduardo Valentin
2008-04-24 15:54     ` [PATCH 3/5] Fix mcbsp clock definition on clock34xx.h Eduardo Valentin
2008-04-24 15:54       ` [PATCH 4/5] OMAP3xx: Add DMA and IRQ definition for McBSP 1 and 2 Eduardo Valentin
2008-04-24 15:54         ` [PATCH 5/5] MACH-OMAP2: MCBSP: Add support for mcbsp on mach-omap2 Eduardo Valentin
2008-04-24 21:46         ` [PATCH 4/5] OMAP3xx: Add DMA and IRQ definition for McBSP 1 and 2 Tony Lindgren
2008-04-25  5:11         ` Gadiyar, Anand
2008-04-25  5:26           ` Eduardo Valentin
2008-04-25  5:46             ` Gadiyar, Anand
2008-04-25  6:13               ` Syed Mohammed, Khasim
2008-04-25 16:48                 ` Tony Lindgren
2008-04-25 16:46           ` Tony Lindgren
2008-04-25 18:10             ` Gadiyar, Anand
2008-04-25 18:13               ` Tony Lindgren
2008-04-24 21:10 ` [PATCH 0/5] Updates on mcbsp driver Felipe Balbi
2008-04-24 21:13   ` Igor Stoppa
2008-04-24 21:45     ` Tony Lindgren [this message]
2008-04-25  5:30       ` Eduardo Valentin

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=20080424214544.GP16834@atomide.com \
    --to=tony@atomide.com \
    --cc=eduardo.valentin@indt.org.br \
    --cc=edubezval@gmail.com \
    --cc=igor.stoppa@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=me@felipebalbi.com \
    --cc=x0044955@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