From: "Prakash, Prashanth" <pprakash@codeaurora.org>
To: George Cherian <george.cherian@cavium.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
devel@acpica.org
Cc: ashwin.chaugule@linaro.org, rjw@rjwysocki.net, lenb@kernel.org,
jassisinghbrar@gmail.com, robert.moore@intel.com,
lv.zheng@intel.com
Subject: Re: [PATCH 0/2] Make cppc acpi driver aware of pcc subspace ids
Date: Mon, 3 Apr 2017 10:44:29 -0600 [thread overview]
Message-ID: <ccc72eec-4a43-b976-0195-49a7c0029641@codeaurora.org> (raw)
In-Reply-To: <1490941442-11954-1-git-send-email-george.cherian@cavium.com>
Hi George,
On 3/31/2017 12:24 AM, George Cherian wrote:
> The current cppc acpi driver works with only one pcc subspace id.
> It maintains and registers only one pcc channel even if the acpi table has
> different pcc subspace ids. The series tries to address the same by making
> cppc acpi driver aware of multiple possible pcc subspace ids.
The current ACPI 6.1 spec restricts the CPPC to a single PCC subspace. See section:
8.4.7.1.9 Using PCC Registers, which states "If the PCC register space is used, all PCC
registers must be defined to be in the same subspace."
--
Thanks,
Prashanth
next prev parent reply other threads:[~2017-04-03 16:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 6:24 [PATCH 0/2] Make cppc acpi driver aware of pcc subspace ids George Cherian
2017-03-31 6:24 ` [PATCH 1/2] mailbox: PCC: Move the MAX_PCC_SUBSPACES definition to header file George Cherian
2017-03-31 6:24 ` [PATCH 2/2] ACPI / CPPC: Make cppc acpi driver aware of pcc subspace ids George Cherian
2017-04-03 17:37 ` Alexey Klimov
2017-04-04 10:51 ` George Cherian
2017-04-04 17:18 ` Alexey Klimov
2017-04-13 9:27 ` [ACPI / CPPC] 3e95abd02e: BUG:unable_to_handle_kernel kernel test robot
2017-04-03 16:44 ` Prakash, Prashanth [this message]
2017-04-03 17:50 ` [PATCH 0/2] Make cppc acpi driver aware of pcc subspace ids Hoan Tran
2017-04-04 10:53 ` George Cherian
2017-06-13 14:17 George Cherian
2017-06-28 21:20 ` Rafael J. Wysocki
2017-07-10 22:07 ` Prakash, Prashanth
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=ccc72eec-4a43-b976-0195-49a7c0029641@codeaurora.org \
--to=pprakash@codeaurora.org \
--cc=ashwin.chaugule@linaro.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).