LKML Archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: "Jon Medhurst (Tixy)" <tixy@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Liviu Dudau <Liviu.Dudau@arm.com>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>
Subject: Re: [PATCH 0/4] ARM64: add SCPI mailbox protocol, clock and CPUFreq support
Date: Tue, 28 Apr 2015 09:47:45 +0100	[thread overview]
Message-ID: <553F4931.7030404@arm.com> (raw)
In-Reply-To: <1430158296.2859.31.camel@linaro.org>

Hi Tixy,

On 27/04/15 19:11, Jon Medhurst (Tixy) wrote:
> On Mon, 2015-04-27 at 12:40 +0100, Sudeep Holla wrote:
>> Hi,
>>
>> This patch series adds support for:
>> 	1. SCPI(System Control and Power Interface) mailbox protocol
>> 	   driver.
>
> Is there a public document with the final protocol specification?
> I have spotted an inconsistency between driver and a draft doc I have
> but before commenting on things like that it would be good to have the
> final version of the document instead.
>

Thanks for having a look at the driver. I am already chasing this up
with the concerned team to check when will this be made public. IIUC you
do have a non-confidential (preliminary)version of document. So you can
comment on the inconsistency you have observed and I can check if it's
issue with the code or the document.

Regards,
Sudeep

  reply	other threads:[~2015-04-28  8:47 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 11:40 [PATCH 0/4] ARM64: add SCPI mailbox protocol, clock and CPUFreq support Sudeep Holla
2015-04-27 11:40 ` [PATCH 1/4] mailbox: add support for System Control and Power Interface(SCPI) protocol Sudeep Holla
2015-04-28  7:36   ` Paul Bolle
2015-04-28  8:41     ` Sudeep Holla
2015-04-28 13:54   ` Jon Medhurst (Tixy)
2015-04-29 10:53     ` Sudeep Holla
2015-04-29 11:43       ` Jon Medhurst (Tixy)
2015-04-29 12:25         ` Jon Medhurst (Tixy)
2015-04-29 13:08           ` Sudeep Holla
2015-04-30  8:49           ` Jon Medhurst (Tixy)
2015-04-29 13:01         ` Sudeep Holla
2015-05-13 16:52   ` Jassi Brar
2015-05-13 17:09     ` Sudeep Holla
2015-05-14  7:02       ` Jassi Brar
2015-05-14  7:30         ` Jassi Brar
2015-05-14  8:25           ` Sudeep Holla
2015-04-27 11:40 ` [PATCH 2/4] clk: add support for clocks provided by SCP(System Control Processor) Sudeep Holla
2015-05-07 10:17   ` Lorenzo Pieralisi
2015-05-20 23:43   ` Stephen Boyd
2015-05-26 13:14     ` Sudeep Holla
2015-04-27 11:40 ` [PATCH 3/4] clk: scpi: add support for cpufreq virtual device Sudeep Holla
2015-05-20 23:45   ` Stephen Boyd
2015-05-26 13:25     ` Sudeep Holla
2015-04-27 11:40 ` [PATCH 4/4] cpufreq: arm_big_little: add SCPI interface driver Sudeep Holla
2015-04-29  5:44   ` Viresh Kumar
2015-04-29  9:39     ` Sudeep Holla
2015-05-01 13:19   ` Jon Medhurst (Tixy)
2015-05-01 13:32     ` Sudeep Holla
2015-05-01 14:12       ` Jon Medhurst (Tixy)
2015-05-01 14:15         ` Sudeep Holla
2015-05-01 17:10           ` Jon Medhurst (Tixy)
2015-05-01 17:14             ` Sudeep Holla
2015-04-27 18:11 ` [PATCH 0/4] ARM64: add SCPI mailbox protocol, clock and CPUFreq support Jon Medhurst (Tixy)
2015-04-28  8:47   ` Sudeep Holla [this message]
2015-04-28 14:21   ` Sudeep Holla

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=553F4931.7030404@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=Lorenzo.Pieralisi@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tixy@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).