From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Suman Anna <s-anna@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Omar Ramirez Luna <omar.ramirez@copitl.com>,
Jassi Brar <jaswinder.singh@linaro.org>,
Loic Pallardy <loic.pallardy@st.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 7/7] mailbox/omap: move the OMAP mailbox framework to drivers
Date: Sat, 8 Jun 2013 21:01:35 -0700 [thread overview]
Message-ID: <20130609040135.GA1730@kroah.com> (raw)
In-Reply-To: <1370656692-41425-1-git-send-email-s-anna@ti.com>
On Fri, Jun 07, 2013 at 08:58:12PM -0500, Suman Anna wrote:
> 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.
>
> The OMAP mailbox framework/driver code is moved to be under
> drivers/mailbox, in preparation for adapting to a common mailbox
> driver framework. This allows the build for OMAP mailbox to be
> enabled (it was disabled during the multi-platform support).
>
> As part of the migration from plat and mach code:
> - Kconfig symbols have been renamed to build OMAP1 or OMAP2+ drivers.
> - mailbox.h under plat-omap/plat/include has been split into a public
> and private header files. The public header has only the API related
> functions and types.
> - The module name mailbox.ko from plat-omap is changed to
> omap-mailbox.ko
> - The module name mailbox_mach.ko from mach-omapX is changed as
> mailbox_omap1.ko for OMAP1
> mailbox_omap2.ko for OMAP2+
>
> Cc: Tony Lindgren <tony@atomide.com>
> Signed-off-by: Omar Ramirez Luna <omar.ramirez@copitl.com>
> Signed-off-by: Suman Anna <s-anna@ti.com>
Staging part:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/7] mailbox/omap: move the OMAP mailbox framework to drivers
Date: Sat, 8 Jun 2013 21:01:35 -0700 [thread overview]
Message-ID: <20130609040135.GA1730@kroah.com> (raw)
In-Reply-To: <1370656692-41425-1-git-send-email-s-anna@ti.com>
On Fri, Jun 07, 2013 at 08:58:12PM -0500, Suman Anna wrote:
> 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.
>
> The OMAP mailbox framework/driver code is moved to be under
> drivers/mailbox, in preparation for adapting to a common mailbox
> driver framework. This allows the build for OMAP mailbox to be
> enabled (it was disabled during the multi-platform support).
>
> As part of the migration from plat and mach code:
> - Kconfig symbols have been renamed to build OMAP1 or OMAP2+ drivers.
> - mailbox.h under plat-omap/plat/include has been split into a public
> and private header files. The public header has only the API related
> functions and types.
> - The module name mailbox.ko from plat-omap is changed to
> omap-mailbox.ko
> - The module name mailbox_mach.ko from mach-omapX is changed as
> mailbox_omap1.ko for OMAP1
> mailbox_omap2.ko for OMAP2+
>
> Cc: Tony Lindgren <tony@atomide.com>
> Signed-off-by: Omar Ramirez Luna <omar.ramirez@copitl.com>
> Signed-off-by: Suman Anna <s-anna@ti.com>
Staging part:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2013-06-09 4:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 1:58 [PATCH 7/7] mailbox/omap: move the OMAP mailbox framework to drivers Suman Anna
2013-06-08 1:58 ` Suman Anna
2013-06-09 4:01 ` Greg Kroah-Hartman [this message]
2013-06-09 4:01 ` Greg Kroah-Hartman
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=20130609040135.GA1730@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=loic.pallardy@st.com \
--cc=ohad@wizery.com \
--cc=omar.ramirez@copitl.com \
--cc=s-anna@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.