gpio: acpi: Don't return 0 on acpi_gpio_count()
authorAndy Shevchenko <andriy.shevchenko@linux.intel.com>
Mon, 20 Feb 2017 16:15:46 +0000 (18:15 +0200)
committerLinus Walleij <linus.walleij@linaro.org>
Thu, 16 Mar 2017 20:52:11 +0000 (21:52 +0100)
It's unusual to have error checking like (ret <= 0) in cases when
counting GPIO resources. In case when it's mandatory we propagate the
error (-ENOENT), otherwise we don't use the result.

This makes consistent behaviour across all possible variants called in
gpiod_count().

Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
drivers/gpio/gpiolib-acpi.c

index 108331de440bafd813eca42f0a73f50ad279869c..a5b84d40e60c20db45da5489c30cee1f6cb8189c 100644 (file)
@@ -1098,7 +1098,7 @@ int acpi_gpio_count(struct device *dev, const char *con_id)
                                        break;
                                }
                }
-               if (count >= 0)
+               if (count > 0)
                        break;
        }
 
@@ -1114,7 +1114,7 @@ int acpi_gpio_count(struct device *dev, const char *con_id)
                if (crs_count > 0)
                        count = crs_count;
        }
-       return count;
+       return count ? count : -ENOENT;
 }
 
 struct acpi_crs_lookup {