From: Sudeep Holla <sudeep.holla@arm.com>
To: Ashwin Chaugule <ashwin.chaugule@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"jaswinder.singh@linaro.org" <jaswinder.singh@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linaro-acpi@lists.linaro.org" <linaro-acpi@lists.linaro.org>,
"patches@linaro.org" <patches@linaro.org>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>
Subject: Re: [PATCH v7 3/8] ACPI: Decouple ACPI idle and ACPI processor drivers
Date: Tue, 04 Aug 2015 18:00:19 +0100 [thread overview]
Message-ID: <55C0EFA3.2040006@arm.com> (raw)
In-Reply-To: <CAJ5Y-eZo07qVMS37eo=OShCLcgpURfyRA=dOQhtF0Y6_fvR=1Q@mail.gmail.com>
On 04/08/15 16:44, Ashwin Chaugule wrote:
> On 4 August 2015 at 11:18, Sudeep Holla <sudeep.holla@arm.com> wrote:
>>
>>
>> On 04/08/15 15:58, Ashwin Chaugule wrote:
>>>
>>> On 4 August 2015 at 10:51, Sudeep Holla <sudeep.holla@arm.com> wrote:
>>>>
>>>> On 03/08/15 18:40, Ashwin Chaugule wrote:
>>>>>
>>>>>
>>>>> On 20 July 2015 at 10:21, Sudeep Holla <sudeep.holla@arm.com> wrote:
>>>>>>
>>>>>> On 09/07/15 19:04, Ashwin Chaugule wrote:
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> In general, you need to split this series so that initially few patches
>>>>>> deal with all the existing Kconfig fix-ups and then introduce
>>>>>> PCC/PSS/CPPC related stuffs. That would help me rebase and test _LPI
>>>>>> support.
>>>>>
>>>>>
>>>>>
>>>>> Hm. I tried to maintain bisectability and make it easier for you to
>>>>> rebase LPI patchwork too. Let me see if I can revisit now that I'm
>>>>> back from vacation. :)
>>>>>
>>>>
>>>> How about you just drop any idle related changes so that I will handle
>>>> that to keep it simple.
>>>
>>>
>>> Unfortunately I can't skip idle changes completely since it is tightly
>>> coupled with the acpi_processor driver as well.
>>>
>>
>> True, but only for ARM64 where we haven't enabled ACPI_PROCESSOR yet in
>> mainline. So from that perspective, it should not cause any issue for
>> keeping changes bisectable on x86/ia64. You can keep these idle changes
>> locally for your testing. Trying to get everything at once will
>> definitely be problematic IMO.
>
> Bisectability aside, without the idle changes to decouple it from
> ACPI_PROCESSOR, the CPPC code will be non-functional. CPPC code has
> been around for review publicly for almost a year and we need it to be
> mainlined soon. So, given that we've converged on a solution for new
> Kconfigs for Idle and PSS and that they're separate patches, why not
> let it progress forwards as part of this series?
>
Sorry, I didn't mean to block this series in anyway. I was just thinking
on how to post the preparatory changes to introduce _LPI. I prefer to
base it on mainline rather than this patch series and hence I made that
request.
Regards,
Sudeep
next prev parent reply other threads:[~2015-08-04 17:00 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 18:04 [PATCH v7 0/8] CPUFreq driver using CPPC methods Ashwin Chaugule
2015-07-09 18:04 ` [PATCH v7 1/8] PCC: Initialize PCC Mailbox earlier at boot Ashwin Chaugule
2015-07-20 14:20 ` Sudeep Holla
2015-08-03 17:37 ` Ashwin Chaugule
2015-07-09 18:04 ` [PATCH v7 2/8] ACPI: Split out ACPI PSS from ACPI Processor driver Ashwin Chaugule
2015-07-18 0:01 ` Rafael J. Wysocki
2015-07-18 0:03 ` Rafael J. Wysocki
2015-08-03 17:26 ` Ashwin Chaugule
2015-08-03 17:24 ` Ashwin Chaugule
2015-07-20 14:20 ` Sudeep Holla
2015-07-20 21:59 ` Rafael J. Wysocki
2015-08-03 17:49 ` Ashwin Chaugule
2015-08-03 17:29 ` Ashwin Chaugule
2015-08-04 14:50 ` Sudeep Holla
2015-07-09 18:04 ` [PATCH v7 3/8] ACPI: Decouple ACPI idle and ACPI processor drivers Ashwin Chaugule
2015-07-20 14:21 ` Sudeep Holla
2015-08-03 17:40 ` Ashwin Chaugule
2015-08-04 14:51 ` Sudeep Holla
2015-08-04 14:58 ` Ashwin Chaugule
2015-08-04 15:18 ` Sudeep Holla
2015-08-04 15:44 ` Ashwin Chaugule
2015-08-04 17:00 ` Sudeep Holla [this message]
2015-08-05 13:47 ` Ashwin Chaugule
2015-07-09 18:04 ` [PATCH v7 4/8] ACPI: Introduce CPU performance controls using CPPC Ashwin Chaugule
2015-08-04 15:06 ` Sudeep Holla
2015-08-04 15:38 ` Ashwin Chaugule
2015-08-04 16:02 ` Sudeep Holla
2015-07-09 18:04 ` [PATCH v7 5/8] CPPC: Add a CPUFreq driver for use with CPPC Ashwin Chaugule
2015-07-20 14:22 ` Sudeep Holla
2015-07-20 22:07 ` Rafael J. Wysocki
2015-07-21 8:52 ` Sudeep Holla
2015-07-21 14:27 ` Rafael J. Wysocki
2015-07-21 15:32 ` Sudeep Holla
2015-07-09 18:04 ` [PATCH v7 6/8] ACPI: Add weak routines for ACPI CPU Hotplug Ashwin Chaugule
2015-07-09 18:04 ` [PATCH v7 7/8] CPPC: Probe for CPPC tables for each ACPI Processor object Ashwin Chaugule
2015-07-20 14:22 ` Sudeep Holla
2015-07-09 18:04 ` [PATCH v7 8/8] PCC: Enable PCC only when needed Ashwin Chaugule
2015-07-20 14:22 ` Sudeep Holla
2015-07-20 22:04 ` Rafael J. Wysocki
2015-07-21 9:23 ` Sudeep Holla
2015-07-21 14:34 ` Rafael J. Wysocki
2015-07-21 15:28 ` Sudeep Holla
2015-07-22 1:28 ` Rafael J. Wysocki
2015-07-22 8:59 ` Sudeep Holla
2015-08-03 17:35 ` Ashwin Chaugule
2015-08-04 14:53 ` 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=55C0EFA3.2040006@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=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 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).