From: "Prakash, Prashanth" <pprakash@codeaurora.org>
To: George Cherian <george.cherian@cavium.com>,
devel@acpica.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Cc: lv.zheng@intel.com, robert.moore@intel.com,
jassisinghbrar@gmail.com, lenb@kernel.org, rjw@rjwysocki.net
Subject: Re: [PATCH v5 2/2] ACPI / CPPC: Make cppc acpi driver aware of pcc subspace ids
Date: Thu, 26 Oct 2017 15:19:32 -0600 [thread overview]
Message-ID: <fa1e72aa-086c-152b-af63-ad25cf87e2fe@codeaurora.org> (raw)
In-Reply-To: <1507712098-13035-3-git-send-email-george.cherian@cavium.com>
On 10/11/2017 2:54 AM, George Cherian wrote:
> Based on ACPI 6.2 Section 8.4.7.1.9 If the PCC register space is used,
> all PCC registers, for all processors in the same performance
> domain (as defined by _PSD), must be defined to be in the same subspace.
> Based on Section 14.1 of ACPI specification, it is possible to have a
> maximum of 256 PCC subspace ids. Add support of multiple PCC subspace id
> instead of using a single global pcc_data structure.
>
> While at that fix the time_delta check in send_pcc_cmd() so that last_mpar_reset
> and mpar_count is initialized properly.
>
> Signed-off-by: George Cherian <george.cherian@cavium.com>
Reviewed-by: Prashanth Prakash <pprakash@codeaurora.org>
--
Thanks,
Prashanth
prev parent reply other threads:[~2017-10-26 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 8:54 [PATCH v5 0/2] Make cppc acpi driver aware of pcc subspace ids George Cherian
2017-10-11 8:54 ` [PATCH v5 1/2] mailbox: PCC: Move the MAX_PCC_SUBSPACES definition to header file George Cherian
2017-10-26 21:19 ` Prakash, Prashanth
2017-10-11 8:54 ` [PATCH v5 2/2] ACPI / CPPC: Make cppc acpi driver aware of pcc subspace ids George Cherian
2017-10-26 21:19 ` Prakash, Prashanth [this message]
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=fa1e72aa-086c-152b-af63-ad25cf87e2fe@codeaurora.org \
--to=pprakash@codeaurora.org \
--cc=devel@acpica.org \
--cc=george.cherian@cavium.com \
--cc=jassisinghbrar@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.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).