linux-kernel - Re: [PATCH 0/2] Make cppc acpi driver aware of pcc subspace ids

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ccc72eec-4a43-b976-0195-49a7c0029641@codeaurora.org>
Date:   Mon, 3 Apr 2017 10:44:29 -0600
From:   "Prakash, Prashanth" <pprakash@...eaurora.org>
To:     George Cherian <george.cherian@...ium.com>,
        linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
        devel@...ica.org
Cc:     ashwin.chaugule@...aro.org, rjw@...ysocki.net, lenb@...nel.org,
        jassisinghbrar@...il.com, robert.moore@...el.com,
        lv.zheng@...el.com
Subject: Re: [PATCH 0/2] Make cppc acpi driver aware of pcc subspace ids

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