From: Kevin Hilman <khilman@ti.com>
To: Omar Ramirez Luna <omar.ramirez@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
Benoit Cousson <b-cousson@ti.com>,
Russell King <linux@arm.linux.org.uk>,
lo <linux-omap@vger.kernel.org>,
lak <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 0/5] omap: mailbox: hwmod support
Date: Tue, 08 Feb 2011 15:44:24 -0800 [thread overview]
Message-ID: <87ei7igkh3.fsf@ti.com> (raw)
In-Reply-To: <1296674843-12718-1-git-send-email-omar.ramirez@ti.com> (Omar Ramirez Luna's message of "Wed, 2 Feb 2011 13:27:18 -0600")
Omar Ramirez Luna <omar.ramirez@ti.com> writes:
> Mailbox hwmod support for OMAP 2,3,4.
>
> This was tested on OMAP3 (3430, 3630), minor testing
> was made on OMAP4.
>
> No testing on OMAP2 since I don't have the hardware.
Reviewed-by: Kevin Hilman <khilman@ti.com>
But still needs sanity testing on OMAP2.
Kevin
> Highlights from v5 include the comments received from
> previous version v4[1].
>
> Benoit Cousson (1):
> OMAP4: hwmod data: add mailbox data
>
> Felipe Contreras (2):
> OMAP3: hwmod data: add mailbox data
> OMAP: mailbox: build device using omap_device/omap_hwmod
>
> Omar Ramirez Luna (1):
> OMAP: mailbox: use runtime pm for clk and sysc handling
>
> omar ramirez (1):
> OMAP2: hwmod data: add mailbox data
>
> arch/arm/mach-omap2/devices.c | 98 +++++-----------------------
> arch/arm/mach-omap2/mailbox.c | 67 ++-----------------
> arch/arm/mach-omap2/omap_hwmod_2420_data.c | 74 +++++++++++++++++++++
> arch/arm/mach-omap2/omap_hwmod_2430_data.c | 73 +++++++++++++++++++++
> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 72 ++++++++++++++++++++
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 67 +++++++++++++++++++
> 6 files changed, 308 insertions(+), 143 deletions(-)
>
> ---
> [1] http://bit.ly/gfLaIs
> --
> 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
next prev parent reply other threads:[~2011-02-08 23:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 19:27 [PATCH v5 0/5] omap: mailbox: hwmod support Omar Ramirez Luna
2011-02-02 19:27 ` [PATCH v5 1/5] OMAP2: hwmod data: add mailbox data Omar Ramirez Luna
2011-02-02 19:27 ` [PATCH v5 2/5] OMAP3: " Omar Ramirez Luna
2011-02-02 19:27 ` [PATCH v5 3/5] OMAP4: " Omar Ramirez Luna
2011-02-14 15:00 ` Cousson, Benoit
2011-02-15 21:55 ` Ramirez Luna, Omar
2011-02-15 22:05 ` Cousson, Benoit
2011-02-16 0:13 ` Ramirez Luna, Omar
2011-02-17 23:39 ` Tony Lindgren
2011-02-18 0:24 ` Ramirez Luna, Omar
2011-02-02 19:27 ` [PATCH v5 4/5] OMAP: mailbox: build device using omap_device/omap_hwmod Omar Ramirez Luna
2011-02-02 19:27 ` [PATCH v5 5/5] OMAP: mailbox: use runtime pm for clk and sysc handling Omar Ramirez Luna
2011-02-08 23:44 ` Kevin Hilman [this message]
2011-02-09 18:32 ` [PATCH v5 0/5] omap: mailbox: hwmod support Tony Lindgren
2011-02-10 6:01 ` Hiroshi DOYU
2011-02-11 16:37 ` Kevin Hilman
2011-02-10 5:34 ` Poddar, Sourav
2011-02-10 21:12 ` Kevin Hilman
2011-02-11 23:01 ` Kevin Hilman
2011-02-15 20:56 ` Ramirez Luna, Omar
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=87ei7igkh3.fsf@ti.com \
--to=khilman@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=omar.ramirez@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).