From: Jassi Brar <jassisinghbrar@gmail.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Arnd Bergmann <arnd@arndb.de>, Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Devicetree List <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] dt-bindings: mailbox: add doorbell support to ARM MHU
Date: Wed, 3 Jun 2020 13:42:18 -0500 [thread overview]
Message-ID: <CABb+yY2KXqRnxqHC-Hs8NsosEPtyTYO4v_b1cCGs9Lphpz_X+A@mail.gmail.com> (raw)
In-Reply-To: <20200603183120.GE23722@bogus>
On Wed, Jun 3, 2020 at 1:31 PM Sudeep Holla <sudeep.holla@arm.com> wrote:
>
> > >
> > H/W is actually fine :) Its just that the driver is written to
> > _also_ support a platform (my original) that doesn't have shmem and
> > need to pass data via 32bit registers.
> > Frankly, I am not against the doorbell mode, I am against implementing
> > two modes in a driver. If it really helped (note the past tense) the
> > SCMI, we could implement the driver only in doorbell mode but
> > unfortunately SCMI would still be _broken_ for non-doorbell
> > controllers.
>
> Should be fine as the specification is designed to work with only shmem
> for any data transfer and mailbox is just a signal mechanism. I won't
> be too worried about that.
>
Please clarify how it will work on, say again, rockchip platform with shmem.
thanks.
next prev parent reply other threads:[~2020-06-03 18:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 5:17 [RFC] dt-bindings: mailbox: add doorbell support to ARM MHU Viresh Kumar
2020-05-15 16:46 ` Jassi Brar
2020-05-18 7:35 ` Viresh Kumar
2020-05-19 0:53 ` Jassi Brar
2020-05-19 4:39 ` Viresh Kumar
2020-05-19 1:29 ` Bjorn Andersson
2020-05-19 3:40 ` Viresh Kumar
2020-05-19 4:05 ` Jassi Brar
2020-06-03 18:31 ` Sudeep Holla
2020-06-03 18:42 ` Jassi Brar [this message]
2020-06-03 18:28 ` Sudeep Holla
2020-05-28 19:20 ` Rob Herring
2020-05-29 4:07 ` Viresh Kumar
2020-06-03 18:04 ` Sudeep Holla
2020-06-03 18:17 ` Sudeep Holla
2020-06-04 5:59 ` Viresh Kumar
2020-06-04 8:28 ` Sudeep Holla
2020-06-03 18:32 ` Jassi Brar
2020-06-04 9:20 ` Sudeep Holla
2020-06-04 15:15 ` Jassi Brar
2020-06-05 4:56 ` Sudeep Holla
2020-06-05 6:30 ` Jassi Brar
2020-06-05 8:58 ` Sudeep Holla
2020-06-05 15:42 ` Jassi Brar
2020-06-10 9:33 ` Viresh Kumar
2020-06-11 10:00 ` Sudeep Holla
2020-06-12 0:34 ` Jassi Brar
2020-06-12 5:28 ` Viresh Kumar
2020-09-08 9:14 ` Arnd Bergmann
2020-09-08 9:27 ` Viresh Kumar
2020-09-08 13:26 ` Sudeep Holla
2020-09-09 3:23 ` Jassi Brar
2020-09-09 4:46 ` Viresh Kumar
2020-09-09 9:31 ` Sudeep Holla
2020-05-29 5:20 ` Jassi Brar
2020-05-29 6:27 ` Viresh Kumar
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+yY2KXqRnxqHC-Hs8NsosEPtyTYO4v_b1cCGs9Lphpz_X+A@mail.gmail.com \
--to=jassisinghbrar@gmail.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.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).