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
Signed-off-by: Yong Li
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
Signed-off-by: Yong Li
Dear Maintainers,
This patch fixes the “incorrect IIO device name” issue.
Please merge it into standard/base branch for linux-yocto-4.4 if this looks
okay.
Thanks
Yong Li
Yong Li (2):
iio: tmp006: Set correct iio name
iio: si7020: Set correct iio name
drivers/iio/humidity/si7020.c|
This reverts commit 1c4353d569cb037064fdb378d3be9ac7e4bc08d1.
Restrict standard/intel visibility to meta-intel i.e. don't touch
common-pc*.
---
bsp/common-pc-64/common-pc-64-standard.scc | 1 -
bsp/common-pc/common-pc-standard.scc | 1 -
2 files changed, 2 deletions(-)
diff --git
I got a little overzealous with moving BSPs to standard/intel - we
should have started with meta-intel only and not touched genericX86 or
anything else.
This reverts the common-pc* changes that did that (and should also get
rid of the new warnings for qemux86*).
The following changes since
I got a little overzealous with moving BSPs to standard/intel - we
should have started with meta-intel only and not touched genericX86 or
anything else.
This reverts the common-pc* changes that did that (and should also get
rid of the new warnings for qemux86*).
The following changes since
On 2016-05-24 5:49 PM, Tom Zanussi wrote:
In order to provide more timely support for Intel platforms, this
patchset makes use of a set of dedicated */intel branches to be
created for the linux-yocto 4.4 kernel.
These branches and the corresponding kernel metadata branches provide
a place to
