Searched hist:"00 f0ea70" (Results 1 – 1 of 1) sorted by relevance
| /openbmc/linux/drivers/misc/eeprom/ |
| H A D | at24.c | 00f0ea70 Fri Aug 12 06:32:57 CDT 2016 Bartosz Golaszewski <bgolaszewski@baylibre.com> eeprom: at24: check if the chip is functional in probe()
The at24 driver doesn't check if the chip is functional in its probe
function. This leads to instantiating devices that are not physically
present. For example the cape EEPROMs for BeagleBone Black are defined
in the device tree at four addresses on i2c2, but normally only one of
them is present.
If the userspace doesn't know the location in advance, it will need to
check if reading the nvmem attributes fails to determine which EEPROM
is actually there.
Try to read a single byte in probe() and bail-out with -ENODEV if the
read fails.
Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
00f0ea70 Fri Aug 12 06:32:57 CDT 2016 Bartosz Golaszewski <bgolaszewski@baylibre.com> eeprom: at24: check if the chip is functional in probe()
The at24 driver doesn't check if the chip is functional in its probe
function. This leads to instantiating devices that are not physically
present. For example the cape EEPROMs for BeagleBone Black are defined
in the device tree at four addresses on i2c2, but normally only one of
them is present.
If the userspace doesn't know the location in advance, it will need to
check if reading the nvmem attributes fails to determine which EEPROM
is actually there.
Try to read a single byte in probe() and bail-out with -ENODEV if the
read fails.
Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
|