From: leo.yan@linaro.org (Leo Yan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/4] mailbox: Hi6220: add mailbox driver
Date: Fri, 16 Oct 2015 14:18:24 +0800 [thread overview]
Message-ID: <20151016061824.GD3226@leoy-linaro> (raw)
In-Reply-To: <CAJe_ZhejrJZZA=zVJvfrtmj7oBfTCd1NddoEmrJG1SEo5TvbNw@mail.gmail.com>
On Fri, Oct 16, 2015 at 11:42:54AM +0530, Jassi Brar wrote:
> On 16 October 2015 at 11:38, Leo Yan <leo.yan@linaro.org> wrote:
> > On Fri, Oct 16, 2015 at 11:17:32AM +0530, Jassi Brar wrote:
> >> On Fri, Oct 16, 2015 at 10:59 AM, Leo Yan <leo.yan@linaro.org> wrote:
> >> > On Fri, Oct 16, 2015 at 10:43:00AM +0530, Jassi Brar wrote:
> >> >> 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?
> >> >
> >> > For the later case.
> >> Former is a s/w limitation and latter is h/w limitation. From what you
> >> write below, it seems former to be the case.
> >
> > Sorry, i misunderstood the question. It's a s/w limitation.
> >
> >> > Mailbox also can be used by other modules, such
> >> > like audio hifi; later need add links for them if want to enable
> >> > audio. But so far only uses first 2 channels.
> >> >
> >> You mean every time your platform needs another channel, you'll update
> >> the driver? Not sure about that. It should be simpler to assign which
> >> ever and as many channels as the client asks via DT.
> >
> > For hi6220, every channel is fixed to specific purpose;
> on different platform the purposes may be different, so ....
>
> > so i can
> > register all of them in driver, such like hifi related channels;
> > Though i cannot test them currently, but this will avoid extra
> > efforts for enabling channels anymore, do you think this is okay?
> > Or you prefer to bind with DT?
> >
> .... DT please.
Ok, will do this.
Thansk,
Leo Yan
next prev parent reply other threads:[~2015-10-16 6:18 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 mailbox driver 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
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 [this message]
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=20151016061824.GD3226@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