All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Ashwin Chaugule <ashwin.chaugule@linaro.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Jaswinder Singh <jaswinder.singh@linaro.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Linaro ACPI Mailman List <linaro-acpi@lists.linaro.org>,
	Patch Tracking <patches@linaro.org>,
	linux acpi <linux-acpi@vger.kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH v6 2/7] ACPI: Make ACPI processor driver more extensible
Date: Thu, 09 Jul 2015 10:06:34 +0100	[thread overview]
Message-ID: <559E399A.7000003@arm.com> (raw)
In-Reply-To: <CAJ5Y-eaGmF6pRKuapzQo8ruMt0FX4kVrdyu-os6maVaS7WO-Pw@mail.gmail.com>

Hi,

On 08/07/15 21:28, Ashwin Chaugule wrote:
> On 8 July 2015 at 16:05, Ashwin Chaugule <ashwin.chaugule@linaro.org> wrote:
>> On 8 July 2015 at 15:55, Rafael J. Wysocki <rafael@kernel.org> wrote:
>>> Hi Ashwin,

[...]

>>>
>>> Can you please just send the new version of the $subject patch alone for now?
>>
>> Attached below. (hope that worked.)
>>
>>>
>>> Also I'm still unsure what the connection between _CST and CPPC is.
>>>
>>
>> There isnt. But I'm missing where I've implied the dependency?
>
> Perhaps the confusion is coming from the introduction of ACPI_CST in
> this file. I could leave it as it is and just separate out the
> ACPI_PSS bits. But I figured, while I'm at it, I'd introduce ACPI_CST,
> since we know the LPI stuff is coming up soon as a CST alternative
> anyway. So if you prefer, I can drop the CST bits and maybe Sudeep can
> address that as part of his LPI patchset?
>

Correct, I will handle it as a prerequisite for introducing _LPI
support. I had posted an RFC long back, will revive those patches and
repost them soon.

It's better to enable ACPI_PROCESSOR on ARM64 only after we have all
these dependencies resolved. Until then we need to carry some patches
locally for testing.

Regards,
Sudeep


  parent reply	other threads:[~2015-07-09  9:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 20:09 [PATCH v6 0/7] CPUFreq driver using CPPC methods Ashwin Chaugule
2015-06-15 20:09 ` [PATCH v6 1/7] PCC: Initialize PCC Mailbox earlier at boot Ashwin Chaugule
2015-06-15 20:09 ` [PATCH v6 2/7] ACPI: Make ACPI processor driver more extensible Ashwin Chaugule
2015-07-08  1:07   ` Rafael J. Wysocki
2015-07-08  1:27     ` Ashwin Chaugule
2015-07-08 13:34       ` Rafael J. Wysocki
2015-07-08 13:42         ` Ashwin Chaugule
2015-07-08 19:16         ` Ashwin Chaugule
2015-07-08 19:55           ` Rafael J. Wysocki
2015-07-08 20:05             ` Ashwin Chaugule
2015-07-08 20:28               ` Ashwin Chaugule
2015-07-08 20:46                 ` Rafael J. Wysocki
2015-07-08 21:46                   ` Ashwin Chaugule
2015-07-08 22:21                     ` Rafael J. Wysocki
2015-07-08 21:57                       ` Ashwin Chaugule
2015-07-08 23:29                         ` Rafael J. Wysocki
2015-07-08 23:33                           ` Rafael J. Wysocki
2015-07-09  9:11                     ` Sudeep Holla
2015-07-09  9:06                 ` Sudeep Holla [this message]
2015-07-09 12:25                   ` Ashwin Chaugule
2015-07-09 13:18                     ` Sudeep Holla
2015-07-08 13:43       ` Sudeep Holla
2015-07-08 13:56         ` Ashwin Chaugule
2015-07-08 14:20           ` Sudeep Holla
2015-06-15 20:09 ` [PATCH v6 3/7] ACPI: Introduce CPU performance controls using CPPC Ashwin Chaugule
2015-06-15 20:09 ` [PATCH v6 4/7] CPPC: Add a CPUFreq driver for use with CPPC Ashwin Chaugule
2015-06-15 20:09 ` [PATCH v6 5/7] CPPC: Probe for CPPC tables for each ACPI Processor object Ashwin Chaugule
2015-06-15 20:09 ` [PATCH v6 6/7] PCC: Enable PCC only when needed Ashwin Chaugule
2015-06-15 20:09 ` [PATCH v6 7/7] ACPI: Add weak routines for ACPI CPU Hotplug Ashwin Chaugule
2015-06-29 17:23 ` [PATCH v6 0/7] CPUFreq driver using CPPC methods Ashwin Chaugule

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=559E399A.7000003@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=ashwin.chaugule@linaro.org \
    --cc=jaswinder.singh@linaro.org \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=viresh.kumar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.