linux-toradex.git/drivers/video/backlight, branch v4.14-rc5

dmi: Mark all struct dmi_system_id instances const

2017-09-14T09:59:30+00:00

... and __initconst if applicable.

Based on similar work for an older kernel in the Grsecurity patch.

[JD: fix toshiba-wmi build]
[JD: add htcpen]
[JD: move __initconst where checkscript wants it]

Signed-off-by: Christoph Hellwig 
Signed-off-by: Jean Delvare

Merge tag 'backlight-next-4.14' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight

2017-09-07T20:55:16+00:00

Pull backlight updates from Lee Jones:
 "Fix-ups:
   - Constification; pwm_bl
   - Use new GPIO API; gpio_backlight
   - Remove unused functionality; gpio_backlight

  Bug Fixes:
   - Fix artificial MAXREG limit; lm3630a_bl"

* tag 'backlight-next-4.14' of git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight:
  backlight: gpio_backlight: Delete pdata inversion
  backlight: gpio_backlight: Convert to use GPIO descriptor
  backlight: pwm_bl: Make of_device_ids const
  backlight: lm3630a: Bump REG_MAX value to 0x50 instead of 0x1F

mfd: twl: Move header file out of I2C realm

2017-09-04T13:41:02+00:00

include/linux/i2c is not for client devices. Move the header file to a
more appropriate location.

Signed-off-by: Wolfram Sang 
Acked-by: Greg Kroah-Hartman 
Acked-by: Alexandre Belloni 
Acked-by: Mark Brown 
Acked-by: Sebastian Reichel 
Acked-by: Jonathan Cameron 
Acked-by: Dmitry Torokhov 
Acked-by: Kishon Vijay Abraham I 
Acked-by: Bartlomiej Zolnierkiewicz 
Acked-by: Thierry Reding 
Acked-by: Tony Lindgren 
Acked-by: Daniel Thompson 
Acked-by: Linus Walleij 
Acked-by: Guenter Roeck 
Signed-off-by: Lee Jones

backlight: gpio_backlight: Delete pdata inversion

2017-08-07T16:11:28+00:00

The option to invert the output of the GPIO (active low) is
not used by the only platform still using platform data to
set up a GPIO backlight (one SH board). Delete the option
as we do not expect to expand the use of board files for
this driver, and GPIO descriptors intrinsically keep track
of any signal inversion.

Signed-off-by: Linus Walleij 
Acked-by: Daniel Thompson 
Reviewed-by: Laurent Pinchart 
Signed-off-by: Lee Jones

backlight: gpio_backlight: Convert to use GPIO descriptor

2017-08-07T16:04:32+00:00

This driver is predominantly used by device tree systems, all
of which can deal with modern GPIO descriptors. The legacy
GPIO API is only used by one SH board so make the GPIO
descriptor the default way to deal with it.

As an intended side effect we do not need to look around in
the device tree for the inversion flag since the GPIO
descriptors will intrinsically deal with this.

Signed-off-by: Linus Walleij 
Acked-by: Daniel Thompson 
Reviewed-by: Laurent Pinchart 
Signed-off-by: Lee Jones

backlight: pwm_bl: Make of_device_ids const

2017-08-07T16:04:18+00:00

of_device_ids are not supposed to change at runtime. All functions
working with of_device_ids provided by  work with const
of_device_ids. So mark the non-const structs as const.

Signed-off-by: Arvind Yadav 
Acked-by: Thierry Reding 
Acked-by: Daniel Thompson 
Reviewed-by: Laurent Pinchart 
Signed-off-by: Lee Jones

backlight: lm3630a: Bump REG_MAX value to 0x50 instead of 0x1F

2017-07-17T12:27:06+00:00

In the lm3630a_chip_init we try to write to 0x50 register, which is
higher value then the max_register value, this resulted in regmap_write
return -EIO.

Fix this by bumping REG_MAX value to 0x50.

This code was introduced with the chip revision in commit 28e64a68a2ef,
however setting filter strength was failing silently because it used
unsigned int for storing and comparing the return values. Bug related to
signedness was fixed in 2a0c316bf3cc, which made it error out correctly
instead of failing silently.

I found this issue by using this driver on LGE Nexus 5 (hammerhead).
After this commit lm3630a_chip_init succeeds instead of failing with
-EIO.

Fixes: 28e64a68a2ef ("backlight: lm3630: apply chip revision")
Fixes: 2a0c316bf3cc ("drivers/video/backlight/lm3630a_bl.c: fix
signedness bug in lm3630a_chip_init()")

Suggested-by: Bjorn Andersson 
Signed-off-by: Bhushan Shah 
Acked-by: Daniel Thompson 
Signed-off-by: Lee Jones

video: adp8870: move header file out of I2C realm

2017-07-06T07:58:39+00:00

include/linux/i2c is not for client devices. Move the header file to a
more appropriate location.

Signed-off-by: Wolfram Sang 
Acked-by: Daniel Thompson 
Acked-by: Bartlomiej Zolnierkiewicz 
Signed-off-by: Lee Jones

backlight: adp8860: Move header file out of I2C realm

2017-07-06T07:56:08+00:00

include/linux/i2c is not for client devices.

Move the header file to a more appropriate location.

Signed-off-by: Wolfram Sang 
Acked-by: Daniel Thompson 
Acked-by: Michael Hennerich 
Signed-off-by: Lee Jones

backlight: Report error on failure

2017-05-30T08:27:53+00:00

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 
Acked-by: Daniel Thompson 
Signed-off-by: Lee Jones