[PATCH] ACPI: FAN: Update fps count debug print

Sumeet Pawnikar posted 1 patch 3 months, 2 weeks ago
There is a newer version of this series
drivers/acpi/fan_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[PATCH] ACPI: FAN: Update fps count debug print
Posted by Sumeet Pawnikar 3 months, 2 weeks ago
Update invalid value returned debug print with fps_count
instead of control value for checking fan fps count condition.

Signed-off-by: Sumeet Pawnikar <sumeet4linux@gmail.com>
---
 drivers/acpi/fan_core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/acpi/fan_core.c b/drivers/acpi/fan_core.c
index 8ad12ad3aaaf..9f2696a1928c 100644
--- a/drivers/acpi/fan_core.c
+++ b/drivers/acpi/fan_core.c
@@ -102,7 +102,7 @@ static int fan_get_state_acpi4(struct acpi_device *device, unsigned long *state)
 			break;
 	}
 	if (i == fan->fps_count) {
-		dev_dbg(&device->dev, "Invalid control value returned\n");
+		dev_dbg(&device->dev, "Invalid fps_count value returned\n");
 		return -EINVAL;
 	}
 
-- 
2.43.0
Re: [PATCH] ACPI: FAN: Update fps count debug print
Posted by Rafael J. Wysocki 3 months, 1 week ago
On Sat, Jun 21, 2025 at 7:17 AM Sumeet Pawnikar <sumeet4linux@gmail.com> wrote:
>
> Update invalid value returned debug print with fps_count
> instead of control value for checking fan fps count condition.
>
> Signed-off-by: Sumeet Pawnikar <sumeet4linux@gmail.com>
> ---
>  drivers/acpi/fan_core.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/fan_core.c b/drivers/acpi/fan_core.c
> index 8ad12ad3aaaf..9f2696a1928c 100644
> --- a/drivers/acpi/fan_core.c
> +++ b/drivers/acpi/fan_core.c
> @@ -102,7 +102,7 @@ static int fan_get_state_acpi4(struct acpi_device *device, unsigned long *state)
>                         break;
>         }
>         if (i == fan->fps_count) {
> -               dev_dbg(&device->dev, "Invalid control value returned\n");
> +               dev_dbg(&device->dev, "Invalid fps_count value returned\n");

I guess this should be "fps" instead of "fps_count" because the latter
is just the array size, isn't it?

But I don't see why it should not be "control" either.

>                 return -EINVAL;
>         }
>
> --