When load the driver using the below command:
echo tmp006 0x40 > /sys/bus/i2c/devices/i2c-0/new_device
In sysfs, the i2c name is tmp006, however the iio name is 0-0040,
they are inconsistent. With this patch,
the iio name will be the same as the i2c device name
Upstream-status:
When load the driver using the below command:
echo si7020 0x40 > /sys/bus/i2c/devices/i2c-0/new_device
In sysfs, the i2c name is si7020, however the iio name is 0-0040,
they are inconsistent. With this patch,
the iio name will be the same as the i2c device name
Upstream-status: Pending
Dear Maintainers,
This patchset fixes the “incorrect IIO device name” issue.
without this patch, the device I2C name is mismatch with the IIO name(It is I2C
bus related):
root@intel-corei7-64:/sys/bus/i2c/devices/1-0040# cat name
tmp006
root@intel-corei7-64:/sys/bus/i2c/devices/1-0040# cat
On 2016-05-30 11:38 PM, Yong Li wrote:
Hi Bruce,
The
Upstream-Status:Submitted[http://www.spinics.net/lists/linux-iio/msg24331.html]
for more information, please visit
https://github.com/ostroproject/meta-ostro-bsp/pull/34
without this patch, the device I2C name is mismatch with the IIO name:
Hi Bruce,
The
Upstream-Status:Submitted[http://www.spinics.net/lists/linux-iio/msg24331.html]
for more information, please visit
https://github.com/ostroproject/meta-ostro-bsp/pull/34
without this patch, the device I2C name is mismatch with the IIO name:
On 2016-05-28 09:50 PM, Saul Wold wrote:
On Sat, 2016-05-28 at 12:34 +0800, Yong Li wrote:
Hi Bruce Saul,
I had submitted the patches into Kernel mail list, the concern is the
legacy application compatibility:
http://www.spinics.net/lists/linux-iio/index.html#24331
For the Ostro OS, Using
On 2016-05-27 07:51 PM, Jianxun Zhang wrote:
Sync up with 32 bit common-pc variant to bring EFI
framebuffer driver into 64 bit PC config.
[YOCTO #9653]
Signed-off-by: Jianxun Zhang
---
This patch is for Fido (3.14 kernel). We could have another one to
kernel