linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: charu@ti.com (Varadarajan, Charulatha)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 4/5] OMAP: mailbox: send message in process context
Date: Wed, 24 Nov 2010 10:56:54 +0530	[thread overview]
Message-ID: <AANLkTimbXXmPu5KQtpxG6jTxaj18ad+Q5dHSPArEtXgr@mail.gmail.com> (raw)
In-Reply-To: <1290547617-16640-5-git-send-email-h-kanigeri2@ti.com>

On Wed, Nov 24, 2010 at 02:56, Hari Kanigeri <h-kanigeri2@ti.com> wrote:
> Schedule the Tasklet to send only when mailbox fifo is full and there are
> pending messages in kifo, else send the message directly in the Process

Typo -> kifo

> context. This would avoid needless scheduling of Tasklet for every message
> transfer
>
> Signed-off-by: Hari Kanigeri <h-kanigeri2@ti.com>
> ---
> ?arch/arm/plat-omap/mailbox.c | ? ?9 +++++++--
> ?1 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/plat-omap/mailbox.c b/arch/arm/plat-omap/mailbox.c
> index 13698ab..f4177df 100644
> --- a/arch/arm/plat-omap/mailbox.c
> +++ b/arch/arm/plat-omap/mailbox.c
> @@ -92,20 +92,25 @@ int omap_mbox_msg_send(struct omap_mbox *mbox, mbox_msg_t msg)
> ? ? ? ?struct omap_mbox_queue *mq = mbox->txq;
> ? ? ? ?int ret = 0, len;
>
> - ? ? ? spin_lock(&mq->lock);
> + ? ? ? spin_lock_bh(&mq->lock);
>
> ? ? ? ?if (kfifo_avail(&mq->fifo) < sizeof(msg)) {
> ? ? ? ? ? ? ? ?ret = -ENOMEM;
> ? ? ? ? ? ? ? ?goto out;
> ? ? ? ?}
>
> + ? ? ? if (kfifo_is_empty(&mq->fifo) && !__mbox_poll_for_space(mbox)) {
> + ? ? ? ? ? ? ? mbox_fifo_write(mbox, msg);
> + ? ? ? ? ? ? ? goto out;
> + ? ? ? }
> +
> ? ? ? ?len = kfifo_in(&mq->fifo, (unsigned char *)&msg, sizeof(msg));
> ? ? ? ?WARN_ON(len != sizeof(msg));
>
> ? ? ? ?tasklet_schedule(&mbox->txq->tasklet);
>
> ?out:
> - ? ? ? spin_unlock(&mq->lock);
> + ? ? ? spin_unlock_bh(&mq->lock);
> ? ? ? ?return ret;
> ?}
> ?EXPORT_SYMBOL(omap_mbox_msg_send);
> --
> 1.7.0

  reply	other threads:[~2010-11-24  5:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 21:26 [PATCH v4 0/5] OMAP: mailbox: fixes and enhancements Hari Kanigeri
2010-11-23 21:26 ` [PATCH v4 1/5] OMAP: mailbox: change full flag per mailbox queue instead of global Hari Kanigeri
2010-11-24  5:21   ` Varadarajan, Charulatha
2010-11-24 12:47     ` Kanigeri, Hari
2010-11-24 13:04       ` Varadarajan, Charulatha
2010-11-23 21:26 ` [PATCH v4 2/5] OMAP: mailbox: fix rx interrupt disable in omap4 Hari Kanigeri
2010-11-24  5:16   ` Varadarajan, Charulatha
2010-11-24  8:22     ` Felipe Balbi
2010-11-24  8:50       ` Varadarajan, Charulatha
2010-11-24  8:53         ` Felipe Balbi
2010-11-24 13:01         ` Kanigeri, Hari
2010-11-25  7:04           ` Varadarajan, Charulatha
2010-11-25 14:03             ` Hari Kanigeri
2010-11-23 21:26 ` [PATCH v4 3/5] OMAP: mailbox: fix checkpatch warnings Hari Kanigeri
2010-11-23 21:26 ` [PATCH v4 4/5] OMAP: mailbox: send message in process context Hari Kanigeri
2010-11-24  5:26   ` Varadarajan, Charulatha [this message]
2010-11-24 13:14     ` Kanigeri, Hari
2010-11-23 21:26 ` [PATCH v4 5/5] OMAP: mailbox: add notification support for multiple readers Hari Kanigeri
2010-11-24  5:29   ` Varadarajan, Charulatha
2010-11-24 13:09     ` Kanigeri, Hari
2010-11-24 13:12       ` Varadarajan, Charulatha
2010-11-24 13:22         ` 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=AANLkTimbXXmPu5KQtpxG6jTxaj18ad+Q5dHSPArEtXgr@mail.gmail.com \
    --to=charu@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).