linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Prakash, Prashanth" <pprakash@codeaurora.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>, Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH] ACPI / Processor: add sysfs support for low power idle
Date: Mon, 10 Jul 2017 16:47:00 -0600	[thread overview]
Message-ID: <9ab90c21-6bae-c586-8755-88714f0339f7@codeaurora.org> (raw)
In-Reply-To: <CAJZ5v0is=AjNUfMdD4MgoSttgZh_jU80Cm9FPJBo8QqryOdKJw@mail.gmail.com>

Hi Rafael,

On 6/27/2017 5:59 PM, Rafael J. Wysocki wrote:
> On Fri, May 19, 2017 at 9:19 PM, Prashanth Prakash
> <pprakash@codeaurora.org> wrote:
>> Add support to expose idle statistics maintained by platform to
>> userspace via sysfs in addition to other data of interest from
>> each LPI(Low Power Idle) state.
>>
>> LPI described in section 8.4.4 of ACPI spec 6.1 provides different
>> methods to obtain idle statistics maintained by the platform. These
>> show a granular view of how each of the LPI state is being used at
>> different level of hierarchy. sysfs data is exposed at each level in
>> the hierarchy by creating a directory named 'lpi' at each level and
>> the LPI state information is presented under it. Below is the
>> representation of LPI information at one such level in the hierarchy
>>
>> .../ACPI00XX: XX/lpi
>>         |-> state0
>>         |       |-> desc
>>         |       |-> time
>>         |       |-> usage
>>         |       |-> latency
>>         |       |-> min_residency
>>         |
>>         <<more states>>
>>
>> ACPI00XX can be ACPI0007(processor) or ACPI0010(processor container)
>>
>> stateX contains information related to a specific LPI state defined
>> in the LPI ACPI tables.
> That needs to be documented under Documentation/ABI/.
Sure, I will create a patch updating the ABI documentation.
>> diff --git a/include/acpi/processor.h b/include/acpi/processor.h
>> index c1ba00f..b99b84b 100644
>> --- a/include/acpi/processor.h
>> +++ b/include/acpi/processor.h
>> @@ -79,6 +79,19 @@ struct acpi_lpi_state {
>>         u8 index;
>>         u8 entry_method;
>>         char desc[ACPI_CX_DESC_LEN];
>> +       struct acpi_generic_address res_cntr;
>> +       struct acpi_generic_address usage_cntr;
> Is there any reason why these two cannot be of type struct acpi_power_register?
acpi_read() API required reference to acpi_generic_address (our only use case is to read the
register), so keeping this data in acpi_generic_address makes the code little simpler.

--
Thanks,
Prashanth

  reply	other threads:[~2017-07-10 22:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19 19:19 [PATCH] ACPI / Processor: add sysfs support for low power idle Prashanth Prakash
2017-06-27 23:59 ` Rafael J. Wysocki
2017-07-10 22:47   ` Prakash, Prashanth [this message]
2017-07-12 21:21     ` Rafael J. Wysocki

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=9ab90c21-6bae-c586-8755-88714f0339f7@codeaurora.org \
    --to=pprakash@codeaurora.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).