[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bb8d1c16-f10e-5e5e-8a7b-54851e5d9de7@arm.com>
Date: Fri, 12 Jan 2018 11:47:08 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Jolly Shah <JOLLYS@...inx.com>,
"michal.simek@...inx.com" <michal.simek@...inx.com>,
"linux-clk@...r.kernel.org" <linux-clk@...r.kernel.org>
Cc: Sudeep Holla <sudeep.holla@....com>,
"mturquette@...libre.com" <mturquette@...libre.com>,
"sboyd@...eaurora.org" <sboyd@...eaurora.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RFC PATCH 0/2] drivers: clk: Add ZynqMP clock driver support
On 11/01/18 20:29, Jolly Shah wrote:
> Hi Sudeep,
>
> There are 3 things:
>
> 1> IPI mailbox transport - series is already posted
> https://patchwork.kernel.org/patch/10145795/
> 2> EEMI - Posted by me below
> https://patchwork.kernel.org/patch/10150665/
> 3> EEMI Users
> Currently posted as RFC as they are dependent on #2.
> OK, can #2 and #3 can be put together until initial review ?
> #2 doesn’t use mailbox so it is a posted as a separate series.
OK, does it use smc ? If so, the point is treat it as smc mailbox
so that smc is just a transport and EEMI can be still used with other
transport technically.
--
Regards,
Sudeep
Powered by blists - more mailing lists