[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170308233748.54706-1-briannorris@chromium.org>
Date: Wed, 8 Mar 2017 15:37:46 -0800
From: Brian Norris <briannorris@...omium.org>
To: Bjorn Helgaas <bhelgaas@...gle.com>
Cc: <linux-kernel@...r.kernel.org>,
Brian Norris <computersforpeace@...il.com>,
Shawn Lin <shawn.lin@...k-chips.com>,
Jeffy Chen <jeffy.chen@...k-chips.com>,
Wenrui Li <wenrui.li@...k-chips.com>,
linux-pci@...r.kernel.org, linux-rockchip@...ts.infradead.org,
Brian Norris <briannorris@...omium.org>
Subject: [PATCH 1/3] PCI: rockchip: fix sign issues for current limits
The regulator framework can return negative error codes via
regulator_get_current_limit() for regulators that don't provide current
information. The subsequent check for postive values isn't very useful,
if the variable is unsigned.
Let's just match the signedness of the return value.
Prevents error messages like this, seen on Samsung Chromebook Plus:
[ 1.069372] rockchip-pcie f8000000.pcie: invalid power supply
Fixes: 4816c4c7b82b ("PCI: rockchip: Provide captured slot power limit and scale")
Signed-off-by: Brian Norris <briannorris@...omium.org>
---
v4.11 candidate?
drivers/pci/host/pcie-rockchip.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/pci/host/pcie-rockchip.c b/drivers/pci/host/pcie-rockchip.c
index 26ddd3535272..d785f64ec03b 100644
--- a/drivers/pci/host/pcie-rockchip.c
+++ b/drivers/pci/host/pcie-rockchip.c
@@ -425,7 +425,8 @@ static struct pci_ops rockchip_pcie_ops = {
static void rockchip_pcie_set_power_limit(struct rockchip_pcie *rockchip)
{
- u32 status, curr, scale, power;
+ int curr;
+ u32 status, scale, power;
if (IS_ERR(rockchip->vpcie3v3))
return;
--
2.12.0.246.ga2ecc84866-goog
Powered by blists - more mailing lists