From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Jingoo Han <jingoohan1@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] backlight: report error on failure
Date: Mon, 30 Jan 2017 23:04:34 +0000 [thread overview]
Message-ID: <588FC682.9040503@gmail.com> (raw)
In-Reply-To: <1484774630-4228-1-git-send-email-sudipm.mukherjee@gmail.com>
On Wednesday 18 January 2017 09:23 PM, Sudip Mukherjee wrote:
> It is possible to update the backlight power and the brightness using
> the sysfs and on writing it either returns the count or if the callback
> function does not exist then returns the error code 'ENXIO'.
>
> We have a situation where the userspace client is writing to the sysfs
> to update the power and since the callback function exists the client
> receives the return value as count and considers the operation to be
> successful. That is correct as the write to the sysfs was successful.
> But there is no way to know if the actual operation was done or not.
>
> backlight_update_status() returns the error code if it fails. Pass that
> to the userspace client who is trying to update the power so that the
> client knows that the operation failed.
>
> Signed-off-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
> ---
A gentle ping.
--
Regards
Sudip
> drivers/video/backlight/backlight.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/video/backlight/backlight.c b/drivers/video/backlight/backlight.c
> index 288318a..74b72b5 100644
> --- a/drivers/video/backlight/backlight.c
> +++ b/drivers/video/backlight/backlight.c
> @@ -146,9 +146,9 @@ static ssize_t bl_power_store(struct device *dev, struct device_attribute *attr,
> pr_debug("set power to %lu\n", power);
> if (bd->props.power != power) {
> bd->props.power = power;
> - backlight_update_status(bd);
> + rc = backlight_update_status(bd);
> }
> - rc = count;
> + rc = rc ? rc : count;
> }
> mutex_unlock(&bd->ops_lock);
>
> @@ -176,8 +176,7 @@ int backlight_device_set_brightness(struct backlight_device *bd,
> else {
> pr_debug("set brightness to %lu\n", brightness);
> bd->props.brightness = brightness;
> - backlight_update_status(bd);
> - rc = 0;
> + rc = backlight_update_status(bd);
> }
> }
> mutex_unlock(&bd->ops_lock);
>
next prev parent reply other threads:[~2017-01-30 23:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 21:23 [PATCH] backlight: report error on failure Sudip Mukherjee
2017-01-30 23:04 ` Sudip Mukherjee [this message]
2017-02-18 16:31 ` Sudip Mukherjee
2017-02-19 8:26 ` Daniel Thompson
2017-02-20 20:52 ` Sudip Mukherjee
2017-02-22 8:52 ` Lee Jones
2017-02-22 8:52 ` Lee Jones
2017-02-08 12:54 ` Lee Jones
2017-02-08 12:54 ` Lee Jones
2017-02-19 8:13 ` Daniel Thompson
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=588FC682.9040503@gmail.com \
--to=sudipm.mukherjee@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.