ips driver: make it less chatty

We don't need a dev_warn when we exceed a thermal or power limit as
we'll handle it appropriately by clamping down on the CPU, GPU or both
as needed.

Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: Matthew Garrett <mjg@redhat.com>

diff --git a/drivers/platform/x86/intel_ips.c b/drivers/platform/x86/intel_ips.c
index 03448224aedb3570fc8dc13ed2df03ab60cc34c8..afe82e50dfea1b03bf53820cf9f9d2edb76e6355 100644 (file)
--- a/drivers/platform/x86/intel_ips.c
+++ b/drivers/platform/x86/intel_ips.c
@@ -607,7 +607,7 @@ static bool mcp_exceeded(struct ips_driver *ips)
        spin_unlock_irqrestore(&ips->turbo_status_lock, flags);
 
        if (ret)
-               dev_warn(&ips->dev->dev,
+               dev_info(&ips->dev->dev,
                         "MCP power or thermal limit exceeded\n");
 
        return ret;
@@ -635,7 +635,7 @@ static bool cpu_exceeded(struct ips_driver *ips, int cpu)
        spin_unlock_irqrestore(&ips->turbo_status_lock, flags);
 
        if (ret)
-               dev_warn(&ips->dev->dev,
+               dev_info(&ips->dev->dev,
                         "CPU power or thermal limit exceeded\n");
 
        return ret;