From: Sudeep Holla <sudeep.holla@arm.com>
To: Jolly Shah <JOLLYS@xilinx.com>,
"michal.simek@xilinx.com" <michal.simek@xilinx.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"sboyd@codeaurora.org" <sboyd@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH 0/2] drivers: clk: Add ZynqMP clock driver support
Date: Fri, 12 Jan 2018 11:47:08 +0000 [thread overview]
Message-ID: <bb8d1c16-f10e-5e5e-8a7b-54851e5d9de7@arm.com> (raw)
In-Reply-To: <DM2PR0201MB0767E1E08918BED4CB06DB20B8160@DM2PR0201MB0767.namprd02.prod.outlook.com>
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
next prev parent reply other threads:[~2018-01-12 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 22:16 [RFC PATCH 0/2] drivers: clk: Add ZynqMP clock driver support Jolly Shah
2018-01-08 22:16 ` [RFC PATCH 1/2] drivers: clk: Add clk_get_children support Jolly Shah
2018-01-08 22:16 ` [RFC PATCH 2/2] drivers: clk: Add ZynqMP clock driver Jolly Shah
2018-01-09 12:52 ` Philippe Ombredanne
2018-01-10 20:06 ` Jolly Shah
2018-01-10 20:15 ` Jolly Shah
2018-01-11 10:54 ` [RFC PATCH 0/2] drivers: clk: Add ZynqMP clock driver support Sudeep Holla
2018-01-11 20:29 ` Jolly Shah
2018-01-12 11:47 ` Sudeep Holla [this message]
2018-01-12 23:52 ` Jolly Shah
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=bb8d1c16-f10e-5e5e-8a7b-54851e5d9de7@arm.com \
--to=sudeep.holla@arm.com \
--cc=JOLLYS@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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