I2C functions never return an error

[gamer-cndg]

Calls to functions like i2c_writeBytes or i2c_readRaw never return an error value (EXIT_FAILURE), although no device is connected to the bus. When using i2c_readRaw, the function fills the receive buffer with all 0xff and returns EXIT_SUCCESS when no device is present. Thus a userspace program cannot determine if the returned data is really 0xff or if the device just isn't there.

Feature request: The function should return an error value of the I2C subsystem doesn't read the ACK bit in any read/write operation.