public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Cherian <gcherian@caviumnetworks.com>
To: George Cherian <george.cherian@cavium.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	devel@acpica.org
Cc: rjw@rjwysocki.net, lenb@kernel.org, jassisinghbrar@gmail.com,
	robert.moore@intel.com, lv.zheng@intel.com
Subject: Re: [PATCH-internal 0/2] Make cppc acpi driver aware of pcc subspace ids
Date: Tue, 13 Jun 2017 19:46:03 +0530	[thread overview]
Message-ID: <593FF3A3.9060006@caviumnetworks.com> (raw)
In-Reply-To: <1497363313-9936-1-git-send-email-george.cherian@cavium.com>

Sorry Ignore this series!!!

On 06/13/2017 07:45 PM, 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.
>
> As per ACPI 6.2 spec  all PCC registers, for all processors in the same
> performance domain (as defined by _PSD), must be defined to be in the same
> subspace. The series tries to address the same by making cppc acpi driver
> aware of multiple possible pcc subspace ids.
>
> Patch 1 : In preparation to share the MAX_PCC_SUBSPACE definition with cppc acpi
>            driver
> Patch 2 : Make the cppc acpi driver aware of multiple pcc subspace ids.
>
>
> George Cherian (2):
>    mailbox: PCC: Move the MAX_PCC_SUBSPACES definition to header file
>    ACPI / CPPC: Make cppc acpi driver aware of pcc subspace ids
>
>   drivers/acpi/cppc_acpi.c | 179 +++++++++++++++++++++++++----------------------
>   drivers/mailbox/pcc.c    |   1 -
>   include/acpi/pcc.h       |   1 +
>   3 files changed, 97 insertions(+), 84 deletions(-)
>

      parent reply	other threads:[~2017-06-13 14:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 14:15 [PATCH-internal 0/2] Make cppc acpi driver aware of pcc subspace ids George Cherian
2017-06-13 14:15 ` [PATCH-internal 1/2] mailbox: PCC: Move the MAX_PCC_SUBSPACES definition to header file George Cherian
2017-06-13 14:20   ` George Cherian
2017-06-13 14:16 ` George Cherian [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=593FF3A3.9060006@caviumnetworks.com \
    --to=gcherian@caviumnetworks.com \
    --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