From: Daniel Thompson <daniel.thompson@linaro.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Lee Jones <lee.jones@linaro.org>,
Jingoo Han <jingoohan1@gmail.com>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] backlight: propagate errors from get_brightness()
Date: Tue, 7 Sep 2021 10:31:49 +0100 [thread overview]
Message-ID: <20210907093149.2sk3d2jsrekearpa@maple.lan> (raw)
In-Reply-To: <20210906215525.15418-1-linux@weissschuh.net>
On Mon, Sep 06, 2021 at 11:55:25PM +0200, Thomas Weißschuh wrote:
> backlight.h documents "struct backlight_ops->get_brightness()" to return
> a negative errno on failure.
> So far these errors have not been handled in the backlight core.
> This leads to negative values being exposed through sysfs although only
> positive values are documented to be reported.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Change looks good overall but I've raised a few quibbles about the new
error message below.
> ---
> drivers/video/backlight/backlight.c | 22 +++++++++++++++++-----
> 1 file changed, 17 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/video/backlight/backlight.c b/drivers/video/backlight/backlight.c
> index 537fe1b376ad..d681962f8509 100644
> --- a/drivers/video/backlight/backlight.c
> +++ b/drivers/video/backlight/backlight.c
> @@ -292,10 +292,13 @@ static ssize_t actual_brightness_show(struct device *dev,
> struct backlight_device *bd = to_backlight_device(dev);
>
> mutex_lock(&bd->ops_lock);
> - if (bd->ops && bd->ops->get_brightness)
> - rc = sprintf(buf, "%d\n", bd->ops->get_brightness(bd));
> - else
> + if (bd->ops && bd->ops->get_brightness) {
> + rc = bd->ops->get_brightness(bd);
> + if (rc >= 0)
> + rc = sprintf(buf, "%d\n", rc);
> + } else {
> rc = sprintf(buf, "%d\n", bd->props.brightness);
> + }
> mutex_unlock(&bd->ops_lock);
>
> return rc;
> @@ -381,9 +384,18 @@ ATTRIBUTE_GROUPS(bl_device);
> void backlight_force_update(struct backlight_device *bd,
> enum backlight_update_reason reason)
> {
> + int brightness;
> +
> mutex_lock(&bd->ops_lock);
> - if (bd->ops && bd->ops->get_brightness)
> - bd->props.brightness = bd->ops->get_brightness(bd);
> + if (bd->ops && bd->ops->get_brightness) {
> + brightness = bd->ops->get_brightness(bd);
> + if (brightness >= 0)
> + bd->props.brightness = brightness;
> + else
> + dev_warn(&bd->dev,
> + "Could not update brightness from device: errno = %d",
> + -brightness);
The format string is missing a \n and should it really be a dev_warn()?
Is dev_err() more appropriate?
Also please print the error symbolically (which is self explaining
meaning we don't need the errno prefix):
"Could not update brightness from device: %pe\n",
ERR_PTR(brightness)
Daniel.
> + }
> mutex_unlock(&bd->ops_lock);
> backlight_generate_event(bd, reason);
> }
>
> base-commit: 79fad92f2e596f5a8dd085788a24f540263ef887
> --
> 2.33.0
>
prev parent reply other threads:[~2021-09-07 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 21:55 [PATCH] backlight: propagate errors from get_brightness() Thomas Weißschuh
2021-09-07 9:31 ` Daniel Thompson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210907093149.2sk3d2jsrekearpa@maple.lan \
--to=daniel.thompson@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).