Charles Keepax 6f108dd70d i2c: Clear client->irq in i2c_device_remove ... The IRQ will be mapped in i2c_device_probe only if client->irq is zero and i2c_device_remove does not clear this. When rebinding an I2C device, whos IRQ provider has also been rebound this means that an IRQ mapping will never be created, causing the I2C device to fail to acquire its IRQ. Fix this issue by clearing client->irq in i2c_device_remove, forcing i2c_device_probe to lookup the mapping again. Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com> Reviewed-by: Benjamin Tissoires <benjamin.tissoires@redhat.com> Signed-off-by: Wolfram Sang <wsa@the-dreams.de>		2018-10-31 23:33:34 +00:00
..
algos
busses	More ACPI updates for 4.20-rc1	2018-10-30 09:15:31 -07:00
muxes	Merge branch 'i2c/for-4.20' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux	2018-10-29 14:44:03 -07:00
i2c-boardinfo.c
i2c-core-acpi.c
i2c-core-base.c	i2c: Clear client->irq in i2c_device_remove	2018-10-31 23:33:34 +00:00
i2c-core-of.c
i2c-core-slave.c
i2c-core-smbus.c
i2c-core.h
i2c-dev.c
i2c-mux.c
i2c-slave-eeprom.c
i2c-smbus.c
i2c-stub.c
Kconfig
Makefile