[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ffabbe33-5edd-4642-6038-5b48c87ad372@suse.de>
Date: Tue, 1 Aug 2017 12:50:58 +0200
From: Alexander Graf <agraf@...e.de>
To: Andre Przywara <andre.przywara@....com>,
Jassi Brar <jassisinghbrar@...il.com>,
Sudeep Holla <sudeep.holla@....com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-sunxi@...glegroups.com,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
Chen-Yu Tsai <wens@...e.org>, Icenowy Zheng <icenowy@...c.xyz>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org, Michal Simek <michal.simek@...inx.com>
Subject: Re: [PATCH v2 0/3] mailbox: arm: introduce smc triggered mailbox
Hi Andre,
On 24.07.17 01:23, Andre Przywara wrote:
> This is a reworked version of my previous post. It addresses Jassi's
> comments on the driver and also tries to cover Rob's and Mark's comments
> on the binding documentation.
> I dropped the more example-like DT changes from v1, as they are actually
> not meant to be merged into the Linux tree, but instead are provided as
> part of some firmware actually implementing this functionality.
>
> Please let me know what you think.
Could you please quickly explain what it would take to provide SCMI on
top of this instead of SCPI?
https://lkml.org/lkml/2017/6/7/624
I can certainly see that SCPI is an easier target because it's already
upstream and widely spread. But wouldn't it make sense to jump on the
SCMI train while it's taking steam?
Thanks,
Alex
Powered by blists - more mailing lists