[linux-yocto] [PATCH 1/3] features/i2c: Support I2C_MUX by default
Some drivers (e.g. INV_MPU6050_I2C) rely on this, and in most cases this gets selected automatically, but in some cases its not and it causes a configcheck warning. Signed-off-by: California Sullivan --- features/i2c/i2c.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/features/i2c/i2c.cfg b/features/i2c/i2c.cfg index bcd08a3..be41f4b 100644 --- a/features/i2c/i2c.cfg +++ b/features/i2c/i2c.cfg @@ -1,2 +1,3 @@ CONFIG_I2C=y CONFIG_I2C_HELPER_AUTO=y +CONFIG_I2C_MUX=y -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 3/3] leds.cfg: Remove CONFIG_LEDS_TRIGGER_CPU
This is incompatible with preempt-rt and would be a mess to fix any other way. If we were to move CONFIG_LEDS_TRIGGER_CPU to a new feature such as leds-full, it would require us to add leds-full to every non-rt BSP wanting leds support, and -rt BSPs would need the feature without it. Setting "# CONFIG_LEDS_TRIGGER_CPU is not set" also doesn't work, as it depends on !PREEMPT_RT_BASE, making it completely unavailable for setting and still giving us a warning in kernel_configcheck. All this option does is allow CPUs to trigger LEDs based on their usage, so it is not a major loss anyway. Signed-off-by: California Sullivan --- features/leds/leds.cfg | 2 -- 1 file changed, 2 deletions(-) diff --git a/features/leds/leds.cfg b/features/leds/leds.cfg index 77f5209..78bb13b 100644 --- a/features/leds/leds.cfg +++ b/features/leds/leds.cfg @@ -2,8 +2,6 @@ CONFIG_NEW_LEDS=y CONFIG_LEDS_CLASS=y CONFIG_LEDS_TRIGGERS=y -CONFIG_LEDS_TRIGGER_CPU=y - CONFIG_LEDS_TRIGGER_TIMER=y CONFIG_LEDS_TRIGGER_ONESHOT=y CONFIG_LEDS_TRIGGER_HEARTBEAT=y -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 2/3] bsp/intel-quark: Remove bosch-pressure-sensor-i2c
The newer BMP280 IIO driver appears to support the BMP085 chip as well, and the old BMP085 driver cannot be enabled at the same time, giving us configcheck warnings if we try. Signed-off-by: California Sullivan --- bsp/intel-common/intel-quark.scc | 3 --- 1 file changed, 3 deletions(-) diff --git a/bsp/intel-common/intel-quark.scc b/bsp/intel-common/intel-quark.scc index 573d412..8ca5ef9 100644 --- a/bsp/intel-common/intel-quark.scc +++ b/bsp/intel-common/intel-quark.scc @@ -13,9 +13,6 @@ include cfg/timer/hz_100.scc include features/soc/x1000/x1000.scc include features/usb/serial-all.scc -# Add misc drivers for IoT support -include features/misc/bosch-pressure-sensor-i2c.scc - # This line comes last as it has the final word on # CONFIG values. kconf hardware intel-quark.cfg -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [yocto-kernel-cache][PATCH 0/3] Fix remaining kernel_configcheck warnings in Intel BSPs
These are fairly minor changes, but I could use some feedback on the third patch. Although it would be extremely messy, it is possible to keep LEDS_TRIGGER_CPU only for non-preempt-rt BSPs. I just don't know if its worthwhile for such a small functionality that likely goes unused. Patches are targetted for both yocto-4.4 and yocto-4.8. California Sullivan (3): features/i2c: Support I2C_MUX by default bsp/intel-quark: Remove bosch-pressure-sensor-i2c leds.cfg: Remove CONFIG_LEDS_TRIGGER_CPU bsp/intel-common/intel-quark.scc | 3 --- features/i2c/i2c.cfg | 1 + features/leds/leds.cfg | 2 -- 3 files changed, 1 insertion(+), 5 deletions(-) -- 2.5.5 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
