Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • linux
  • Repository
You need to sign in or sign up before continuing.
  • linux
  • drivers
  • acpi
  • cppc_acpi.c
Find file BlameHistoryPermalink
  • Prakash, Prashanth's avatar
    ACPI / CPPC: use MRTT/MPAR to decide if/when a req can be sent · f387e5b9
    Prakash, Prashanth authored Feb 17, 2016
    
    
    The ACPI spec defines Minimum Request Turnaround Time(MRTT) and
    Maximum Periodic Access Rate(MPAR) to prevent the OSPM from sending
    too many requests than the platform can handle. For further details
    on these parameters please refer to section 14.1.3 of ACPI 6.0 spec.
    
    This patch includes MRTT/MPAR in deciding if or when a CPPC request
    can be sent to the platform to make sure CPPC implementation is
    compliant to the spec.
    
    Signed-off-by: default avatarPrashanth Prakash <pprakash@codeaurora.org>
    Acked-by: default avatarAshwin Chaugule <ashwin.chaugule@linaro.org>
    Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
    f387e5b9
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7