linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: omar.ramirez@ti.com (Omar Ramirez Luna)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/7] OMAP: mailbox: removing static declarations
Date: Fri, 24 Jun 2011 20:17:36 -0500	[thread overview]
Message-ID: <1308964663-5669-1-git-send-email-omar.ramirez@ti.com> (raw)

Hi,

This is the first attempt in making the omap mailbox framework generic
enough to support other mailbox drivers, in this series the way the mailbox
are defined and registered is changed to support requests of mailboxes through
an id. So far, the mailbox static declarations have been removed allowing
a dynamic mailbox configuration.

The next steps would involve removing omap references in the code and omap
specific fields (like "type" embedded in the operations structure) along with
a trivial cleanup.

The end goal would be moving the mailbox driver into drivers folder and also
converting other mailbox drivers to reuse this code, the first candidate being
ux-500 mailbox driver (arch/arm/mach-ux500/mbox-db5500.c).

Tested using one patch on top of Kevin Hilman mailbox loopback test, can be
found at: https://gitorious.org/~or.rmz/omap-test/mbox-test-clone

If accepted patches 5 to 7 should be a single patch, to avoid compilation issues.

I'll appreciate any comments or suggestions.

Omar Ramirez Luna (7):
  OMAP2+: hwmod_data: define number of mailboxes
  OMAP2+: devices: get the number of supported mailboxes
  OMAP: mailbox: use OMAP's naming convention for devices
  OMAP: mailbox: move framework functions under header file
  OMAP: mailbox: implement dynamic mailbox configuration
  OMAP1: mailbox: adapt to dynamic mailbox requests
  OMAP2+: mailbox: remove mailbox static declarations

 arch/arm/mach-omap1/mailbox.c              |   94 +++++----
 arch/arm/mach-omap2/devices.c              |    8 +-
 arch/arm/mach-omap2/mailbox.c              |  212 +++++---------------
 arch/arm/mach-omap2/omap_hwmod_2420_data.c |    6 +
 arch/arm/mach-omap2/omap_hwmod_2430_data.c |    6 +
 arch/arm/mach-omap2/omap_hwmod_3xxx_data.c |    6 +
 arch/arm/mach-omap2/omap_hwmod_44xx_data.c |    6 +
 arch/arm/plat-omap/include/plat/mailbox.h  |   62 +++----
 arch/arm/plat-omap/mailbox.c               |  298 ++++++++++++++++++----------
 9 files changed, 364 insertions(+), 334 deletions(-)

Regards,

Omar

             reply	other threads:[~2011-06-25  1:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-25  1:17 Omar Ramirez Luna [this message]
2011-06-25  1:17 ` [RFC PATCH 1/7] OMAP2+: hwmod_data: define number of mailboxes Omar Ramirez Luna
2011-06-25  1:17 ` [RFC PATCH 2/7] OMAP2+: devices: get the number of supported mailboxes Omar Ramirez Luna
2011-06-25  1:17 ` [RFC PATCH 3/7] OMAP: mailbox: use OMAP's naming convention for devices Omar Ramirez Luna
2011-06-25  1:17 ` [RFC PATCH 4/7] OMAP: mailbox: move framework functions under header file Omar Ramirez Luna
2011-06-25  1:17 ` [RFC PATCH 5/7] OMAP: mailbox: implement dynamic mailbox configuration Omar Ramirez Luna
2011-06-25  1:17 ` [RFC PATCH 6/7] OMAP1: mailbox: adapt to dynamic mailbox requests Omar Ramirez Luna
2011-06-25  1:17 ` [RFC PATCH 7/7] OMAP2+: mailbox: remove mailbox static declarations Omar Ramirez Luna

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=1308964663-5669-1-git-send-email-omar.ramirez@ti.com \
    --to=omar.ramirez@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).