Commit 1a14703d authored by Jesse Barnes's avatar Jesse Barnes Committed by Matthew Garrett

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: default avatarJesse Barnes <jbarnes@virtuousgeek.org>
Signed-off-by: default avatarMatthew Garrett <mjg@redhat.com>
parent 5aa06930
...@@ -607,7 +607,7 @@ static bool mcp_exceeded(struct ips_driver *ips) ...@@ -607,7 +607,7 @@ static bool mcp_exceeded(struct ips_driver *ips)
spin_unlock_irqrestore(&ips->turbo_status_lock, flags); spin_unlock_irqrestore(&ips->turbo_status_lock, flags);
if (ret) if (ret)
dev_warn(&ips->dev->dev, dev_info(&ips->dev->dev,
"MCP power or thermal limit exceeded\n"); "MCP power or thermal limit exceeded\n");
return ret; return ret;
...@@ -635,7 +635,7 @@ static bool cpu_exceeded(struct ips_driver *ips, int cpu) ...@@ -635,7 +635,7 @@ static bool cpu_exceeded(struct ips_driver *ips, int cpu)
spin_unlock_irqrestore(&ips->turbo_status_lock, flags); spin_unlock_irqrestore(&ips->turbo_status_lock, flags);
if (ret) if (ret)
dev_warn(&ips->dev->dev, dev_info(&ips->dev->dev,
"CPU power or thermal limit exceeded\n"); "CPU power or thermal limit exceeded\n");
return ret; return ret;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment