Messages in this thread | | | From | Jolly Shah <> | Subject | RE: [RFC PATCH 0/2] drivers: clk: Add ZynqMP clock driver support | Date | Fri, 12 Jan 2018 23:52:22 +0000 |
| |
Hi Sudeep,
> -----Original Message----- > From: Sudeep Holla [mailto:sudeep.holla@arm.com] > Sent: Friday, January 12, 2018 3:47 AM > To: Jolly Shah <JOLLYS@xilinx.com>; michal.simek@xilinx.com; linux- > clk@vger.kernel.org > Cc: Sudeep Holla <sudeep.holla@arm.com>; mturquette@baylibre.com; > sboyd@codeaurora.org; linux-kernel@vger.kernel.org; linux-arm- > kernel@lists.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
I am not sure if I get you correctly. Yes, EEMI uses SMC interface to communicate to PMU. Do you suggest to use Andre's SMC mailbox driver as transport for EEMI?
Thanks, Jolly Shah
| |