From: Suman Anna <s-anna@ti.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: <loic.pallardy@st.com>, <arnd@arndb.de>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Jassi Brar <jaswinder.singh@linaro.org>
Subject: Re: [PATCHv2 0/4] mailbox: Common API
Date: Mon, 6 May 2013 19:02:44 -0500 [thread overview]
Message-ID: <518844A4.8040203@ti.com> (raw)
In-Reply-To: <1367824946-6160-1-git-send-email-jaswinder.singh@linaro.org>
Hi Jassi,
On 05/06/2013 02:22 AM, Jassi Brar wrote:
> Hello,
> I have made the implementation look more proper. Also made some changes
> suggested by Suman. Changes since V1:
>
> * Delete timer upon mailbox release
> * Filled in the stub ipc_links_unregister()
> * Check kzalloc return for errors.
> * Add the controller driver for OMAP2 class. I have taken the patch
> for mailbox's hwmod from Suman's. The clients are yet to be converted
> but this should be enough to convey the idea that the API could
> work for OMAP as well. If I had access to STE documentation, I might
> have done some implementation for U8500 as well.
The bug fixes in this series look good in general. I have provided my
design comments in the previous RFC thread [1] still, since the overall
changes here are not that much different from the RFC.
Thanks for prototyping the OMAP portions, it demonstrates the adaptation
to the new API, but I have to take a step approach in moving the current
OMAP mailbox code and making incremental changes on top of it. The
mailbox driver is the bottom-most layer in our IPC stacks, so changes at
this layer are very critical to the functional behavior.
regards
Suman
[1] http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg429678.html
prev parent reply other threads:[~2013-05-07 0:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 7:22 [PATCHv2 0/4] mailbox: Common API Jassi Brar
2013-05-06 7:23 ` [PATCHv2 1/4] mailbox: rename pl320-ipc specific mailbox.h Jassi Brar
2013-05-06 7:24 ` [PATCHv2 2/4] mailbox: Introduce a new common API Jassi Brar
2013-05-09 16:31 ` Suman Anna
2013-05-09 16:41 ` Jassi Brar
2013-05-09 16:40 ` Suman Anna
2013-05-09 17:48 ` Jassi Brar
2013-05-09 18:05 ` Suman Anna
2013-05-09 18:49 ` Jassi Brar
2013-05-09 23:43 ` Suman Anna
2013-05-06 7:24 ` [PATCHv2 3/4] mailbox: pl320: Introduce common API driver Jassi Brar
2013-05-07 1:58 ` Rob Herring
2013-05-07 16:56 ` Jassi Brar
2013-05-06 7:24 ` [PATCHv2 4/4] mailbox: omap2: " Jassi Brar
2013-05-07 0:02 ` Suman Anna [this message]
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=518844A4.8040203@ti.com \
--to=s-anna@ti.com \
--cc=arnd@arndb.de \
--cc=jassisinghbrar@gmail.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.pallardy@st.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