From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933113AbeALLrO (ORCPT + 1 other); Fri, 12 Jan 2018 06:47:14 -0500 Received: from foss.arm.com ([217.140.101.70]:44046 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754403AbeALLrN (ORCPT ); Fri, 12 Jan 2018 06:47:13 -0500 Cc: Sudeep Holla , "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 To: Jolly Shah , "michal.simek@xilinx.com" , "linux-clk@vger.kernel.org" References: <1515449797-5629-1-git-send-email-jollys@xilinx.com> <6004ad81-96f1-34d9-a037-2c355720dc08@arm.com> From: Sudeep Holla Organization: ARM Message-ID: Date: Fri, 12 Jan 2018 11:47:08 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: 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