From: leo.yan@linaro.org (Leo Yan)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/3] mailbox: hisilicon: add mailbox driver
Date: Thu, 6 Aug 2015 07:17:43 +0800 [thread overview]
Message-ID: <20150805231743.GB6880@leoy-linaro> (raw)
In-Reply-To: <CABb+yY0-RQ80q92EBsuBoYpjxW5zR=nXr+j3zCXw3wKkCf33OQ@mail.gmail.com>
Hi Jassi,
Thanks for review.
On Wed, Aug 05, 2015 at 04:22:01PM +0530, Jassi Brar wrote:
> On Mon, Aug 3, 2015 at 6:43 AM, Leo Yan <leo.yan@linaro.org> wrote:
[...]
> > For easily extending for Hisilicon series SoCs (SoCs may have difference
> > for register's definition with each other), so firstly implement common
> > mailbox driver; this common mailbox driver provides three mainly
> > functionality:
> >
> > - help register channels into framework;
> > - hook low level callback functions for register's operations;
> > - Enhance rx channel's message queue, which is based on the code in
> > drivers/mailbox/omap-mailbox.c.
> >
> Not cool.
> Please don't reinvent the wheel by having platform specific
> implementation of the mailbox api. Which vendor doesn't plan to roll
> out new SoCs, and hence variations of mailbox controllers? The OMAP
> stack predates the common api, and was actually supposed to be
> converted over eventually. Please implement just the
> drivers/mailbox/hi6220-mailbox.c (preferably by the name of the
> mailbox controller, if any)
Understood. Here i have one question, the rx channel's message queue is
looks like a common mechanism and can be added into framework file
mailbox.c, then Soc driver file can _ONLY_ focus on register level's
operations. If so, the common driver in this patch also is unnecessary.
Do you suggest to use upper method to rework patches? Or just think
it's okay to implement rx channel's message queue in hi6220-mailbox.c?
Thanks,
Leo Yan
next prev parent reply other threads:[~2015-08-05 23:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 1:13 [RFC PATCH 0/3] mailbox: hisilicon: add mailbox driver Leo Yan
2015-08-03 1:13 ` [RFC PATCH 1/3] dt-bindings: mailbox: Document Hisilicon " Leo Yan
2015-08-03 1:13 ` [RFC PATCH 2/3] mailbox: Hisilicon: add " Leo Yan
2015-08-04 8:30 ` Paul Bolle
2015-08-04 8:49 ` Leo Yan
2015-08-04 9:00 ` Leo Yan
2015-08-04 9:17 ` Paul Bolle
2015-08-04 9:56 ` Leo Yan
2015-08-03 1:13 ` [RFC PATCH 3/3] arm64: dts: add Hi6220 mailbox node Leo Yan
2015-08-05 10:52 ` [RFC PATCH 0/3] mailbox: hisilicon: add mailbox driver Jassi Brar
2015-08-05 23:17 ` Leo Yan [this message]
2015-08-10 7:02 ` Jassi Brar
2015-08-10 8:52 ` Leo Yan
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=20150805231743.GB6880@leoy-linaro \
--to=leo.yan@linaro.org \
--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