summaryrefslogtreecommitdiffstats
path: root/arch/blackfin
diff options
context:
space:
mode:
authorSudip Mukherjee <sudipm.mukherjee@gmail.com>2017-05-17 22:55:07 +0200
committerLee Jones <lee.jones@linaro.org>2017-05-30 10:27:53 +0200
commit7e715c2d9c27c23f3187454157c58cf292ed103e (patch)
tree245a0835de576c8e101be8eda06eed777c856d99 /arch/blackfin
parentLinux 4.12-rc1 (diff)
downloadlinux-7e715c2d9c27c23f3187454157c58cf292ed103e.tar.xz
linux-7e715c2d9c27c23f3187454157c58cf292ed103e.zip
backlight: Report error on failure
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> Acked-by: Daniel Thompson <daniel.thompson@linaro.org> Signed-off-by: Lee Jones <lee.jones@linaro.org>
Diffstat (limited to 'arch/blackfin')
0 files changed, 0 insertions, 0 deletions