From: Sudeep Holla <sudeep.holla@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Ashwin Chaugule <ashwin.chaugule@linaro.org>,
"jaswinder.singh@linaro.org" <jaswinder.singh@linaro.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"patches@linaro.org" <patches@linaro.org>,
"linaro-acpi@lists.linaro.org" <linaro-acpi@lists.linaro.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"lv.zheng@intel.com" <lv.zheng@intel.com>
Subject: Re: [PATCH v10 1/1] Mailbox: Add support for Platform Communication Channel
Date: Tue, 11 Nov 2014 18:07:03 +0000 [thread overview]
Message-ID: <54625047.2000103@arm.com> (raw)
In-Reply-To: <20141111172955.GA3815@sirena.org.uk>
Hi Mark,
On 11/11/14 17:29, Mark Brown wrote:
> On Tue, Nov 11, 2014 at 10:30:32AM +0000, Sudeep Holla wrote:
>> On 07/11/14 14:52, Ashwin Chaugule wrote:
>
>>> +config PCC
>>> + bool "Platform Communication Channel Driver"
>>> + depends on ACPI
>
>> I am bit confused here, though I prefer PCC to depend on ACPI, I have
>> seen discussion in this thread about using PCC without ACPI, how will
>> that work ?
>
> We can always remove the dependency when someone adds the code to talk
> to non-ACPI PCC devices.
>
Agreed, Ashwin clarified that, I had not followed previous versions
closely and was speaking only in the context of this patch.
Regards,
Sudeep
next prev parent reply other threads:[~2014-11-11 18:06 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 14:52 [PATCH v10 0/1] PCC: Platform Communication Channel Ashwin Chaugule
2014-11-07 14:52 ` [PATCH v10 1/1] Mailbox: Add support for " Ashwin Chaugule
2014-11-09 13:48 ` Jassi Brar
2014-11-09 15:20 ` Ashwin Chaugule
2014-11-09 16:18 ` Jassi Brar
2014-11-09 17:22 ` Ashwin Chaugule
2014-11-10 4:13 ` Jassi Brar
2014-11-10 12:57 ` Ashwin Chaugule
2014-11-10 13:39 ` Jassi Brar
2014-11-10 13:53 ` Ashwin Chaugule
2014-11-10 14:16 ` Jassi Brar
2014-11-10 14:47 ` Ashwin Chaugule
2014-11-10 17:44 ` Jassi Brar
2014-11-10 20:13 ` Mark Brown
2014-11-10 20:29 ` [Linaro-acpi] " Arnd Bergmann
2014-11-11 4:31 ` Jassi Brar
2014-11-11 4:04 ` Jassi Brar
2014-11-11 13:02 ` Ashwin Chaugule
2014-11-11 13:57 ` Jassi Brar
2014-11-11 16:33 ` [Linaro-acpi] " Arnd Bergmann
2014-11-11 17:39 ` Jassi Brar
2014-11-11 17:54 ` Arnd Bergmann
2014-11-11 19:08 ` Jassi Brar
2014-11-11 19:22 ` Ashwin Chaugule
2014-11-11 20:38 ` Arnd Bergmann
2014-11-11 17:53 ` Mark Brown
2014-11-11 10:30 ` Sudeep Holla
2014-11-11 13:18 ` Ashwin Chaugule
2014-11-11 15:01 ` Sudeep Holla
2014-11-11 20:25 ` Arnd Bergmann
2014-11-12 13:32 ` Sudeep Holla
2014-11-12 13:48 ` Ashwin Chaugule
2014-11-12 14:03 ` Sudeep Holla
2014-11-12 18:25 ` [Linaro-acpi] " Ashwin Chaugule
2014-11-12 18:26 ` Mark Brown
2014-11-12 19:04 ` Jassi Brar
2014-11-12 19:16 ` Ashwin Chaugule
2014-11-11 17:29 ` Mark Brown
2014-11-11 18:07 ` Sudeep Holla [this message]
2014-11-11 15:12 ` Jassi Brar
2014-11-11 15:19 ` Ashwin Chaugule
2014-11-11 15:25 ` Jassi Brar
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=54625047.2000103@arm.com \
--to=sudeep.holla@arm.com \
--cc=arnd@arndb.de \
--cc=ashwin.chaugule@linaro.org \
--cc=broonie@kernel.org \
--cc=jaswinder.singh@linaro.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=patches@linaro.org \
--cc=rjw@rjwysocki.net \
/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 NNTP newsgroup(s).