From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/9] mailbox: OMAP: introduce mailbox framework
Date: Tue, 18 Dec 2012 08:59:09 -0800 [thread overview]
Message-ID: <20121218165909.GF4989@atomide.com> (raw)
In-Reply-To: <1355836212-17956-2-git-send-email-loic.pallardy-ext@stericsson.com>
* Loic Pallardy <loic.pallardy-ext@stericsson.com> [121218 05:15]:
> Actually moving it from plat-omap, as this framework/driver code is
> supposed to be under drivers/ folder. The framework should work with
> the current supported OMAP processors (OMAP1+) that have mailbox and
> can be used as a method of interprocessor communication.
>
> The mailbox hardware (in OMAP) uses a queued mailbox-interrupt mechanism
> that provides a communication channel between processors through a set of
> registers and their associated interrupt signals by sending and receiving
> messages.
>
> As part of the migration from plat and mach code:
> - Kconfig symbols have been renamed to build OMAP1 or OMAP2+ drivers.
> - mailbox.h has been changed from plat to a dedicated drivers/ folder.
> - soc.h has been changed for plat/cpu.h, since there are dependencies in
> the cpu_is_XXXX() macro.
>
> Module names have changed too, instead of mailbox_mach:
> - OMAP1: mailbox-omap1.ko
> - OMAP2+: mailbox-omap2.ko
>
> Signed-off-by: Omar Ramirez Luna <omar.luna@linaro.org>
AFAIK the first two patches should have:
From: Omar Ramirez Luna <omar.luna@linaro.org>
Once that's fixed, for arch/arm/*omap*/* parts:
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2012-12-18 16:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 13:10 [PATCH 0/9] drivers: mailbox: framework creation Loic Pallardy
2012-12-18 13:10 ` [PATCH 1/9] mailbox: OMAP: introduce mailbox framework Loic Pallardy
2012-12-18 16:59 ` Tony Lindgren [this message]
2012-12-21 8:54 ` Loic PALLARDY
2012-12-21 10:49 ` Bedia, Vaibhav
2012-12-21 10:53 ` Loic PALLARDY
2013-01-09 12:11 ` Bedia, Vaibhav
2013-01-09 12:29 ` Loic PALLARDY
2013-01-09 12:34 ` Bedia, Vaibhav
2013-01-11 13:34 ` Omar Ramirez Luna
2012-12-18 13:10 ` [PATCH 2/9] mailbox: split internal header from API header Loic Pallardy
2012-12-18 13:10 ` [PATCH 3/9] mailbox: rename omap_mbox in mailbox Loic Pallardy
2012-12-20 21:29 ` Ohad Ben-Cohen
2012-12-18 13:10 ` [PATCH 4/9] mailbox: create opened message type Loic Pallardy
2012-12-21 10:28 ` Bedia, Vaibhav
2012-12-21 10:50 ` Loic PALLARDY
2012-12-18 13:10 ` [PATCH 5/9] mailbox: change protection mechanisms Loic Pallardy
2012-12-21 10:28 ` Bedia, Vaibhav
2012-12-21 10:50 ` Loic PALLARDY
2012-12-18 13:10 ` [PATCH 6/9] mailbox: add shared memory mailbox type Loic Pallardy
2012-12-18 13:10 ` [PATCH 7/9] mailbox: add IRQF_NO_SUSPEND flag Loic Pallardy
2012-12-18 13:10 ` [PATCH 8/9] mailbox: add no_irq send message Loic Pallardy
2012-12-18 13:10 ` [PATCH 9/9] mailbox: create dbx500 mailbox driver Loic Pallardy
2012-12-20 18:16 ` [PATCH 0/9] drivers: mailbox: framework creation Linus Walleij
2012-12-20 18:28 ` Tony Lindgren
2012-12-20 19:19 ` Olof Johansson
2012-12-20 19:33 ` Tony Lindgren
2012-12-21 7:31 ` Ohad Ben-Cohen
2012-12-21 8:52 ` Loic PALLARDY
2012-12-21 19:33 ` Omar Ramirez Luna
2012-12-24 15:17 ` Ohad Ben-Cohen
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=20121218165909.GF4989@atomide.com \
--to=tony@atomide.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).