Searched hist:"1695 c52a1260aee2a33e29add1adca6433d5eac7" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/drivers/iio/adc/ |
| H A D | ltc2497.h | diff 1695c52a1260aee2a33e29add1adca6433d5eac7 Fri Sep 16 09:09:22 CDT 2022 Ciprian Regus <ciprian.regus@analog.com> drivers: iio: adc: ltc2497: Rename the LTC2499 iio device
Set the iio device's name based on the chip used for the
LTC2499 only. The most common way for IIO clients to interact
with a device is to address it based on it's name. By using
the dev_name() function, the name will be set based on a
i2c_client's kobj name, which has the format i2c_instance-i2c_address
(1-0076 for example). This is not ideal, since it makes a
requirement for userspace to have knowledge about the hardware
connections of the device.
The name field is set to NULL for the LTC2497 and LTC2496, so
that the old name can kept as it is, since changing it will
result in an ABI breakage.
Signed-off-by: Ciprian Regus <ciprian.regus@analog.com>
Link: https://lore.kernel.org/r/20220916140922.2506248-6-ciprian.regus@analog.com
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
|
| H A D | ltc2496.c | diff 1695c52a1260aee2a33e29add1adca6433d5eac7 Fri Sep 16 09:09:22 CDT 2022 Ciprian Regus <ciprian.regus@analog.com> drivers: iio: adc: ltc2497: Rename the LTC2499 iio device
Set the iio device's name based on the chip used for the
LTC2499 only. The most common way for IIO clients to interact
with a device is to address it based on it's name. By using
the dev_name() function, the name will be set based on a
i2c_client's kobj name, which has the format i2c_instance-i2c_address
(1-0076 for example). This is not ideal, since it makes a
requirement for userspace to have knowledge about the hardware
connections of the device.
The name field is set to NULL for the LTC2497 and LTC2496, so
that the old name can kept as it is, since changing it will
result in an ABI breakage.
Signed-off-by: Ciprian Regus <ciprian.regus@analog.com>
Link: https://lore.kernel.org/r/20220916140922.2506248-6-ciprian.regus@analog.com
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
|
| H A D | ltc2497-core.c | diff 1695c52a1260aee2a33e29add1adca6433d5eac7 Fri Sep 16 09:09:22 CDT 2022 Ciprian Regus <ciprian.regus@analog.com> drivers: iio: adc: ltc2497: Rename the LTC2499 iio device
Set the iio device's name based on the chip used for the
LTC2499 only. The most common way for IIO clients to interact
with a device is to address it based on it's name. By using
the dev_name() function, the name will be set based on a
i2c_client's kobj name, which has the format i2c_instance-i2c_address
(1-0076 for example). This is not ideal, since it makes a
requirement for userspace to have knowledge about the hardware
connections of the device.
The name field is set to NULL for the LTC2497 and LTC2496, so
that the old name can kept as it is, since changing it will
result in an ABI breakage.
Signed-off-by: Ciprian Regus <ciprian.regus@analog.com>
Link: https://lore.kernel.org/r/20220916140922.2506248-6-ciprian.regus@analog.com
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
|
| H A D | ltc2497.c | diff 1695c52a1260aee2a33e29add1adca6433d5eac7 Fri Sep 16 09:09:22 CDT 2022 Ciprian Regus <ciprian.regus@analog.com> drivers: iio: adc: ltc2497: Rename the LTC2499 iio device
Set the iio device's name based on the chip used for the
LTC2499 only. The most common way for IIO clients to interact
with a device is to address it based on it's name. By using
the dev_name() function, the name will be set based on a
i2c_client's kobj name, which has the format i2c_instance-i2c_address
(1-0076 for example). This is not ideal, since it makes a
requirement for userspace to have knowledge about the hardware
connections of the device.
The name field is set to NULL for the LTC2497 and LTC2496, so
that the old name can kept as it is, since changing it will
result in an ABI breakage.
Signed-off-by: Ciprian Regus <ciprian.regus@analog.com>
Link: https://lore.kernel.org/r/20220916140922.2506248-6-ciprian.regus@analog.com
Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
|