From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: Paul Walmsley <paul@pwsan.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
Benoit Cousson <b-cousson@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
Russell King <linux@arm.linux.org.uk>,
Omar Ramirez Luna <omar.ramirez@ti.com>,
Charulatha V <charu@ti.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/5] omap: mailbox: hwmod support
Date: Fri, 10 Dec 2010 19:51:01 -0600 [thread overview]
Message-ID: <1292032266-29460-1-git-send-email-omar.ramirez@ti.com> (raw)
Tested on 3430, based of pm-core branch. It may require rebase once
the mailbox git pull is made.
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg39719.html
** v3 **
- Taken mailbox hwmod as is from Benoit original branch.
- Put back numbers for irq, addresses instead of considering them
as magic numbers.
- Follow the declaration layout for omap4 hwmods.
- Using pm_runtime to enable the clocks.
TBD: Cleanup, once omap_device_get_rt_va can be called by drivers
using pdev and the proper omap_device_reset API is submitted.
** v2 **
- Added omap4 hwmod support.
- Moved "mailbox_ick" from hwmod to hwmod_if (omap 2/3)
- Declared sysc classes for omap 2/3
** v1 **
1. omap: mailbox: initial hwmod support for omap3
Changes were made to:
- Rebase to latest code.
- Detect the hwmod by filling prcm union for omap2, without
this it was unable to build the hwmod at runtime.
- Replace magic number for defines.
- Use ioremap again instead of relying on the one made by hwmod,
as noted in http://patchwork.kernel.org/patch/101661/
2. omap: mailbox: initial hwmod support for omap2
Was only compiled tested!! Unfortunately I don't have the HW for it.
Benoit Cousson (1):
OMAP4: hwmod data: add mailbox data
Felipe Contreras (3):
OMAP3: hwmod data: add mailbox data
OMAP: mailbox: build device using omap_device/omap_hwmod
OMAP: mailbox: add omap_device latency information
omar ramirez (1):
OMAP2: hwmod data: add mailbox data
arch/arm/mach-omap2/devices.c | 102 ++++++----------------------
arch/arm/mach-omap2/mailbox.c | 18 ++---
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 73 ++++++++++++++++++++
arch/arm/mach-omap2/omap_hwmod_2430_data.c | 72 +++++++++++++++++++
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 71 +++++++++++++++++++
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 68 ++++++++++++++++++
6 files changed, 310 insertions(+), 94 deletions(-)
next reply other threads:[~2010-12-11 2:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-11 1:51 Omar Ramirez Luna [this message]
2010-12-11 1:51 ` [PATCH v3 1/5] OMAP2: hwmod data: add mailbox data Omar Ramirez Luna
2010-12-11 1:51 ` [PATCH v3 2/5] OMAP3: " Omar Ramirez Luna
2010-12-11 1:51 ` [PATCH v3 3/5] OMAP4: " Omar Ramirez Luna
2010-12-11 1:51 ` [PATCH v3 4/5] OMAP: mailbox: build device using omap_device/omap_hwmod Omar Ramirez Luna
2010-12-11 1:51 ` [PATCH v3 5/5] OMAP: mailbox: add omap_device latency information Omar Ramirez Luna
2010-12-11 15:25 ` Ramirez Luna, Omar
2010-12-13 8:45 ` Cousson, Benoit
2010-12-13 18:28 ` Kanigeri, Hari
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=1292032266-29460-1-git-send-email-omar.ramirez@ti.com \
--to=omar.ramirez@ti.com \
--cc=b-cousson@ti.com \
--cc=charu@ti.com \
--cc=felipe.contreras@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=paul@pwsan.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