devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jassi Brar <jassisinghbrar@gmail.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
	"Devicetree List" <devicetree@vger.kernel.org>,
	"André Przywara" <andre.przywara@arm.com>,
	"Chen-Yu Tsai" <wens@csie.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	linux-sunxi@googlegroups.com, "Rob Herring" <robh+dt@kernel.org>,
	"Icenowy Zheng" <icenowy@aosc.xyz>,
	"Maxime Ripard" <maxime.ripard@free-electrons.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/8] mailbox: introduce ARM SMC based mailbox
Date: Mon, 24 Jul 2017 23:22:41 +0530	[thread overview]
Message-ID: <CABb+yY0LYagAOet-KgP+PB__t26LdCSCnxtH6h_X+T37sq_5Wg@mail.gmail.com> (raw)
In-Reply-To: <0aaba7fb-2183-2d4d-ba04-64b30cd0ae10@arm.com>

On Mon, Jul 24, 2017 at 11:08 PM, Sudeep Holla <sudeep.holla@arm.com> wrote:
> On 24/07/17 18:20, Jassi Brar wrote:

>>
>>> I see that the SCPI firmware driver (as the user of the mailbox API) is
>>> expecting the return value from a0 as returned above, translating the
>>> firmware error codes into Linux' ones.
>>>
>> I am afraid, SCPI driver is not the golden example for client drivers
>> to follow. It is supposed to work only with MHU, and then, it is
>> likely to break if some other protocol is running parallel to it.
>>
>
> Not sure why do you say it works only with ARM MHU ? AmLogic uses it
> with their mailbox driver. However they followed an interim version of
> the SCPI spec which is termed "legacy" in the driver.
>
Screw coding... Just tell me what stuff do you smoke? Must be really good!

  reply	other threads:[~2017-07-24 17:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-30  9:56 [PATCH 0/8] mailbox: arm/arm64: introduce smc triggered mailbox Andre Przywara
     [not found] ` <20170630095608.24943-1-andre.przywara-5wv7dgnIgG8@public.gmane.org>
2017-06-30  9:56   ` [PATCH 1/8] mailbox: introduce ARM SMC based mailbox Andre Przywara
2017-07-02  5:55     ` Jassi Brar
     [not found]       ` <CABb+yY18Aye3wr2A9-+jemqc=VSRyUA+xzKGo9s0G4KCt1ovyA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-23 23:20         ` André Przywara
2017-07-24 17:20           ` Jassi Brar
2017-07-24 17:38             ` Sudeep Holla
2017-07-24 17:52               ` Jassi Brar [this message]
2017-06-30  9:56   ` [PATCH 2/8] dt-bindings: mailbox: add binding doc for the ARM SMC mailbox Andre Przywara
     [not found]     ` <20170630095608.24943-3-andre.przywara-5wv7dgnIgG8@public.gmane.org>
2017-07-07 13:53       ` Rob Herring
2017-07-07 14:35       ` Mark Rutland
2017-07-07 16:06         ` Andre Przywara
2017-06-30  9:56   ` [PATCH 3/8] mailbox: Kconfig: enable ARM SMC mailbox on 64-bit Allwinner SoCs Andre Przywara
2017-06-30  9:56   ` [PATCH 4/8] arm64: dts: allwinner: a64: add SCPI support Andre Przywara
2017-06-30  9:56   ` [PATCH 5/8] arm64: dts: allwinner: a64: add SCPI DVFS nodes Andre Przywara
2017-06-30  9:56   ` [PATCH 6/8] arm64: dts: allwinner: a64: add SCPI sensors support Andre Przywara
2017-06-30  9:56   ` [PATCH 7/8] arm64: dts: allwinner: a64: add SCPI power domain support Andre Przywara
2017-06-30  9:56   ` [PATCH 8/8] arm64: dts: allwinner: a64: add (unused) MMC clock node Andre Przywara
2017-06-30 12:25   ` [PATCH 0/8] mailbox: arm/arm64: introduce smc triggered mailbox Maxime Ripard
2017-06-30 12:56     ` Andre Przywara
     [not found]       ` <7a58855c-7481-320e-19f0-83bd113ef2c0-5wv7dgnIgG8@public.gmane.org>
2017-07-05  6:55         ` Maxime Ripard

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+yY0LYagAOet-KgP+PB__t26LdCSCnxtH6h_X+T37sq_5Wg@mail.gmail.com \
    --to=jassisinghbrar@gmail.com \
    --cc=andre.przywara@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=icenowy@aosc.xyz \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=robh+dt@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=wens@csie.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).