public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Christopher Covington <cov@codeaurora.org>,
	ACPI List <linux-acpi@vger.kernel.org>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Prashanth Prakash <pprakash@codeaurora.org>,
	Al Stone <al.stone@linaro.org>,
	Vikas Sajjan <vikas.cha.sajjan@hpe.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	LKML <linux-kernel@vger.kernel.org>,
	Ashwin Chaugule <ashwin.chaugule@linaro.org>,
	Sudeep Holla <sudeep.holla@arm.com>,
	ALKML <linux-arm-kernel@lists.infradead.org>,
	Sunil <sunil.vl@hpe.com>
Subject: Re: [PATCH v10 7/7] ACPI : enable ACPI_PROCESSOR_IDLE on ARM64
Date: Tue, 2 Aug 2016 14:00:16 +0100	[thread overview]
Message-ID: <4963f55a-d014-ec7b-2d9d-471fb3f29204@arm.com> (raw)
In-Reply-To: <579BA8DE.3050802@codeaurora.org>



On 29/07/16 20:05, Christopher Covington wrote:
> Hi Sudeep,
>
> On 07/19/2016 01:52 PM, Sudeep Holla wrote:
>> Now that ACPI processor idle driver supports LPI(Low Power Idle), lets
>> enable ACPI_PROCESSOR_IDLE for ARM64 too.
>>
>> This patch just removes the IA64 and X86 dependency on ACPI_PROCESSOR_IDLE
>>
>> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
>> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
>> ---
>>  drivers/acpi/Kconfig | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
>> index 1358fb7d7a68..d74275c0f374 100644
>> --- a/drivers/acpi/Kconfig
>> +++ b/drivers/acpi/Kconfig
>> @@ -238,7 +238,7 @@ config ACPI_CPPC_LIB
>>  config ACPI_PROCESSOR
>>  	tristate "Processor"
>>  	depends on X86 || IA64 || ARM64
>> -	select ACPI_PROCESSOR_IDLE if X86 || IA64
>> +	select ACPI_PROCESSOR_IDLE
>>  	select ACPI_CPU_FREQ_PSS if X86 || IA64
>>  	default y
>>  	help
>>
>
> This causes a boot hang on QDF2432. cpuidle.off=1 works around the
> problem. I understand you're working on a fix to the problem in GICv3
> code. If there's anything I can do to help, please let me know.

Sorry for the late response, I was away. Yes it's to do with GICv3 and
retention states. I exchanged mails with QCOM guys in private. To summarize:

We don't need any additional support in Linux to support that. Infact we
need to remove disabling the redistributor in the powerdown path. PSCI
implementation also do the same for Group0(aka secure/EL3 interrupts)
and we currently do that for Group1(aka EL1N interrupts) in Linux. The
plan was to move that to EL3 code, to align with GICv2 code.

Hence the changes in Linux is just removal of the GICv3 PM notifier
partially. I will need to check with Trusted Firmware team and do some
testing before I post that change. I will plan to do that later this week.

-- 
Regards,
Sudeep

  reply	other threads:[~2016-08-02 13:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 17:52 [PATCH v10 0/7] ACPI / processor_idle: Add ACPI v6.0 LPI support Sudeep Holla
2016-07-19 17:52 ` [PATCH v10 1/7] ACPI / processor_idle: introduce ACPI_PROCESSOR_CSTATE Sudeep Holla
2016-07-19 17:52 ` [PATCH v10 2/7] ACPI / processor_idle: Add support for Low Power Idle(LPI) states Sudeep Holla
2016-07-21 13:34   ` Rafael J. Wysocki
2016-07-21 15:55     ` Sudeep Holla
2016-07-21 16:18   ` Sudeep Holla
2016-07-19 17:52 ` [PATCH v10 3/7] arm64: cpuidle: drop __init section marker to arm_cpuidle_init Sudeep Holla
2016-07-19 17:52 ` [PATCH v10 4/7] cpuidle: introduce CPU_PM_CPU_IDLE_ENTER macro for ARM{32,64} Sudeep Holla
2016-07-19 17:52 ` [PATCH v10 5/7] drivers: firmware: psci: initialise idle states using ACPI LPI Sudeep Holla
2016-07-19 17:52 ` [PATCH v10 6/7] arm64: add support for ACPI Low Power Idle(LPI) Sudeep Holla
2016-07-19 17:52 ` [PATCH v10 7/7] ACPI : enable ACPI_PROCESSOR_IDLE on ARM64 Sudeep Holla
2016-07-29 19:05   ` Christopher Covington
2016-08-02 13:00     ` Sudeep Holla [this message]
2016-08-15 14:47       ` Christopher Covington
2016-08-15 14:51         ` 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=4963f55a-d014-ec7b-2d9d-471fb3f29204@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=al.stone@linaro.org \
    --cc=ashwin.chaugule@linaro.org \
    --cc=cov@codeaurora.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=pprakash@codeaurora.org \
    --cc=rjw@rjwysocki.net \
    --cc=sunil.vl@hpe.com \
    --cc=vikas.cha.sajjan@hpe.com \
    /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