From: Tony Lindgren <tony@atomide.com>
To: Eduardo Valentin <edubezval@gmail.com>,
Chandra shekhar <x0044955@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/4] Updates on mcbsp driver (take #2)
Date: Fri, 16 May 2008 08:54:13 -0700 [thread overview]
Message-ID: <20080516155413.GF23002@atomide.com> (raw)
In-Reply-To: <1210022587-7756-1-git-send-email-edubezval@gmail.com>
Hi,
* Eduardo Valentin <edubezval@gmail.com> [080505 14:24]:
> From: Eduardo Valentin <eduardo.valentin@indt.org.br>
>
> Hi Tony,
>
> Here is the updated version of my previous patches.
> DMA and IRQ definitions were left as they are. Chandra is going
> to send his work on top of this series.
>
> 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.
Chandra, do these patches look OK to you from your patches point of
view?
Tony
>
> Cheers,
>
>
> Eduardo Valentin (4):
> PLAT-OMAP: MCBSP: Tranform into platform driver
> MACH-OMAP1: MCBSP: Add support for mcbsp on mach-omap1
> Fix mcbsp clock definition on clock34xx.h
> MACH-OMAP2: MCBSP: Add support for mcbsp on mach-omap2
>
> arch/arm/mach-omap1/Makefile | 2 +
> arch/arm/mach-omap1/mcbsp.c | 165 +++++++++
> arch/arm/mach-omap2/Makefile | 2 +
> arch/arm/mach-omap2/clock34xx.h | 30 ++-
> arch/arm/mach-omap2/mcbsp.c | 105 ++++++
> arch/arm/plat-omap/devices.c | 45 +++
> arch/arm/plat-omap/mcbsp.c | 660 ++++++++++++++-----------------------
> include/asm-arm/arch-omap/mcbsp.h | 73 ++++-
> 8 files changed, 661 insertions(+), 421 deletions(-)
> create mode 100644 arch/arm/mach-omap1/mcbsp.c
> create mode 100644 arch/arm/mach-omap2/mcbsp.c
>
next prev parent reply other threads:[~2008-05-16 15:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 21:23 [PATCH 0/4] Updates on mcbsp driver (take #2) Eduardo Valentin
2008-05-05 21:23 ` [PATCH 1/4] PLAT-OMAP: MCBSP: Tranform into platform driver Eduardo Valentin
2008-05-05 21:23 ` [PATCH 2/4] MACH-OMAP1: MCBSP: Add support for mcbsp on mach-omap1 Eduardo Valentin
2008-05-05 21:23 ` [PATCH 3/4] Fix mcbsp clock definition on clock34xx.h Eduardo Valentin
2008-05-05 21:23 ` [PATCH 4/4] MACH-OMAP2: MCBSP: Add support for mcbsp on mach-omap2 Eduardo Valentin
2008-05-08 11:23 ` [PATCH 1/4] PLAT-OMAP: MCBSP: Tranform into platform driver Trilok Soni
2008-05-08 12:13 ` Eduardo Valentin
2008-05-20 23:44 ` Tony Lindgren
2008-05-29 15:30 ` Eduardo Valentin
2008-05-16 15:54 ` Tony Lindgren [this message]
2008-05-19 14:26 ` [PATCH 0/4] Updates on mcbsp driver (take #2) Steve Sakoman
2008-05-19 15:09 ` Eduardo Valentin
2008-05-20 11:21 ` Jarkko Nikula
2008-06-12 19:14 ` Steve Sakoman
2008-06-13 6:31 ` Jarkko Nikula
2008-05-20 6:47 ` Chandra shekhar
2008-05-20 18:27 ` Koen Kooi
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=20080516155413.GF23002@atomide.com \
--to=tony@atomide.com \
--cc=edubezval@gmail.com \
--cc=linux-omap@vger.kernel.org \
--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