From: Jassi Brar <jassisinghbrar@gmail.com>
To: Leo Yan <leo.yan@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Bintian Wang <bintian.wang@huawei.com>,
Yiping Xu <xuyiping@hisilicon.com>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
Wei Xu <xuwei5@hisilicon.com>,
Devicetree List <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 2/4] mailbox: Hi6220: add mailbox driver
Date: Fri, 16 Oct 2015 10:43:00 +0530 [thread overview]
Message-ID: <CABb+yY2uJZFgDeviRzz8ghVhNzy5d6jf+=fpTAUez01m+O0ttw@mail.gmail.com> (raw)
In-Reply-To: <1444667535-16948-3-git-send-email-leo.yan@linaro.org>
On Mon, Oct 12, 2015 at 10:02 PM, Leo Yan <leo.yan@linaro.org> wrote:
> +
> +#define MBOX_CHAN_MAX 32
> +#define MBOX_CHAN_NUM 2
> +
You mean the hardware has 32 channels but this driver can not manage
more than 2 ?
OR, there are 32 interfaces but only 2 physical 'floating' links, so
no more than 2 interfaces can be active at any time?
next prev parent reply other threads:[~2015-10-16 5:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 16:32 [PATCH v4 0/4] mailbox: hisilicon: add Hi6220 " Leo Yan
2015-10-12 16:32 ` [PATCH v4 1/4] dt-bindings: mailbox: Document " Leo Yan
2015-10-16 4:56 ` Jassi Brar
2015-10-16 5:23 ` Leo Yan
2015-10-12 16:32 ` [PATCH v4 2/4] mailbox: Hi6220: add " Leo Yan
2015-10-16 5:13 ` Jassi Brar [this message]
2015-10-16 5:29 ` Leo Yan
2015-10-16 5:47 ` Jassi Brar
2015-10-16 6:08 ` Leo Yan
2015-10-16 6:12 ` Jassi Brar
2015-10-16 6:18 ` Leo Yan
2015-10-12 16:32 ` [PATCH v4 3/4] arm64: dts: add mailbox node for Hi6220 Leo Yan
2015-10-12 16:32 ` [PATCH v4 4/4] arm64: dts: add Hi6220's stub clock node 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='CABb+yY2uJZFgDeviRzz8ghVhNzy5d6jf+=fpTAUez01m+O0ttw@mail.gmail.com' \
--to=jassisinghbrar@gmail.com \
--cc=bintian.wang@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=haojian.zhuang@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.com \
--cc=xuyiping@hisilicon.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
all inboxes | Powered by JetHome®