Re: [linux-yocto] [PATCH 0/2] iio: Set correct iio name
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 Soletta framrwork, we have tested/verified more more than 30 different I2C devices(https://ostroproject.org/documentation/hardware/sensors.html). But only the two devices have incorrect device names(the IIO name does not match the I2C device name). QA team think it is a bug Thanks, Yong 2016-05-27 23:51 GMT+08:00 Saul Wold : > On Fri, 2016-05-27 at 10:24 -0400, Bruce Ashfield wrote: >> On 2016-05-27 12:58 AM, Yong Li wrote: >> > >> > 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. >> The change looks technically correct, just a question about if these >> are also going upstream to the mainline kernel. >> > Bruce, > > These are possibly candidates for the standard/intel branch, > they where proposed upstream and deemed correct, but not merge-able due > to creating incompatible names. > > Yong Li, > What is requiring the name change in Ostro, why can't Ostro > use the existing incorrect, but compatible name? > > Sau! >> Bruce >> >> > >> > >> > Thanks >> > Yong Li >> > >> > Yong Li (2): >> >iio: tmp006: Set correct iio name >> >iio: si7020: Set correct iio name >> > >> > drivers/iio/humidity/si7020.c| 2 +- >> > drivers/iio/temperature/tmp006.c | 2 +- >> > 2 files changed, 2 insertions(+), 2 deletions(-) >> > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH] meta: add efi-ext into common-pc-64.scc
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 cache once it is accepted. Basic test done with sato and lsb-sdk images on Fido. meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc b/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc index 82f0f27..d9a4cfe 100644 --- a/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc +++ b/meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc @@ -4,6 +4,8 @@ kconf hardware bsp/common-pc/common-pc-eth.cfg kconf hardware bsp/common-pc/common-pc-gfx.cfg kconf hardware bsp/common-pc/common-pc-wifi.cfg +include cfg/efi-ext.scc + include cfg/x86_64.scc include features/usb/ehci-hcd.scc include features/usb/uhci-hcd.scc -- 1.9.1 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PULL REQUEST] Broxton related backports for linux-yocto-4.4
On Wed, 2016-05-25 at 12:17 -0400, Bruce Ashfield wrote: > On 2016-05-24 4:19 PM, California Sullivan wrote: > > > > Hi Bruce, > > > > This is a set of backports from upstream. I have tested > > allyesconfig, > > allnoconfig, and standard builds and can't find anything wrong > > there. > > I have also tested running the kernel on MinnowBoard Max and there > > are > > no new errors or warnings. > > > > Let me know if I need to make any modifications and send out a V2. > No need for a v2. They look fine to me, and I've staged them on > the kernel repo and have adjusted the SRCREVs. I'll send out the > update in a day or so. > Did you actually push them to the linux-yocto-4.4 repo yet? Or are they staged on your machine? Sau! > Bruce > > > > > > > Thanks, > > Cal Sullivan > > > > > > he following changes since commit > > 628bf627561c6285d99fb978e11d4c15fc29324b: > > > > Merge tag 'v4.4.11' into standard/base (2016-05-19 09:02:42 > > -0400) > > > > are available in the git repository at: > > > > git://git.yoctoproject.org/linux-yocto-contrib > > clsulliv/standard/base > > > > for you to fetch changes up to > > 53e84104c5e68eb468823dd0d262a64623d01a55: > > > > mmc: mmc: Fix partition switch timeout for some eMMCs (2016-05-19 > > 17:15:25 -0700) > > > > > > Adrian Hunter (3): > > mmc: sdhci: Remove SDHCI_SDR104_NEEDS_TUNING > > mmc: mmc: Attempt to flush cache before reset > > mmc: mmc: Fix partition switch timeout for some eMMCs > > > > Andy Shevchenko (12): > > device property: always check for fwnode type > > device property: rename helper functions > > device property: refactor built-in properties support > > device property: keep single value inplace > > device property: improve readability of macros > > device property: return -EINVAL when property isn't found in > > ACPI > > device property: Fallback to secondary fwnode if primary > > misses the property > > mfd: core: propagate device properties to sub devices drivers > > mfd: intel-lpss: Pass HSUART configuration via properties > > device property: avoid allocations of 0 length > > lib/string: introduce match_string() helper > > device property: convert to use match_string() helper > > > > Bamvor Jian Zhang (1): > > gpiolib: do not allow to insert an empty gpiochip > > > > Christophe RICARD (2): > > ACPI: Rename acpi_gsi_get_irq_type to acpi_dev_get_irq_type > > and export symbol > > ACPI / gpio: Add irq_type when a GPIO is used as an interrupt > > > > Dasaratharaman Chandramouli (1): > > intel_idle: Support for Intel Xeon Phi Processor x200 Product > > Family > > > > Gwendal Grignou (1): > > mmc: core: Do regular power cycle when lacking eMMC HW reset > > support > > > > Heikki Krogerus (4): > > device property: helper macros for property entry creation > > device property: the secondary fwnode needs to depend on the > > primary > > device property: fwnode->secondary may contain ERR_PTR(- > > ENODEV) > > device property: fix for a case of use-after-free > > > > Len Brown (2): > > intel_idle: Add SKX support > > intel_idle: add BXT support > > > > Linus Walleij (1): > > Revert "gpio: revert get() to non-errorprogating behaviour" > > > > Mika Westerberg (7): > > pwm: lpss: Remove ->free() callback > > pwm: lpss: Rework the sequence of programming PWM_SW_UPDATE > > device property: Take a copy of the property set > > driver core: platform: Add support for built-in device > > properties > > mfd: intel-lpss: Add support for passing device properties > > mfd: intel-lpss: Pass SDA hold time to I2C host controller > > driver > > mfd: intel-lpss: Pass I2C configuration via properties on BXT > > > > Qipeng Zha (1): > > pinctrl: intel: make the high level interrupt working > > > > Richard Cochran (10): > > intel_idle: remove useless return from void function. > > intel_idle: Fix a helper function's return value. > > intel_idle: Remove redundant initialization calls. > > intel_idle: Fix deallocation order on the driver exit path. > > intel_idle: Fix dangling registration on error path. > > intel_idle: Avoid a double free of the per-CPU data. > > intel_idle: Setup the timer broadcast only on successful > > driver load. > > intel_idle: Don't overreact to a cpuidle registration > > failure. > > intel_idle: Propagate hot plug errors. > > intel_idle: Clean up all registered devices on exit. > > > > Wolfram Sang (1): > > mmc: make MAN_BKOPS_EN message a debug > > > > qipeng.zha (1): > > pwm: lpss: Update PWM setting for Broxton > > > > arch/x86/include/asm/msr-index.h | 8 + > > drivers/acpi/gsi.c| 21 +- > > drivers/acpi/property.c | 10 +- > > d
Re: [linux-yocto] [PATCH 0/2] iio: Set correct iio name
On Fri, 2016-05-27 at 10:24 -0400, Bruce Ashfield wrote: > On 2016-05-27 12:58 AM, Yong Li wrote: > > > > 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. > The change looks technically correct, just a question about if these > are also going upstream to the mainline kernel. > Bruce, These are possibly candidates for the standard/intel branch, they where proposed upstream and deemed correct, but not merge-able due to creating incompatible names. Yong Li, What is requiring the name change in Ostro, why can't Ostro use the existing incorrect, but compatible name? Sau! > Bruce > > > > > > > Thanks > > Yong Li > > > > Yong Li (2): > > iio: tmp006: Set correct iio name > > iio: si7020: Set correct iio name > > > > drivers/iio/humidity/si7020.c| 2 +- > > drivers/iio/temperature/tmp006.c | 2 +- > > 2 files changed, 2 insertions(+), 2 deletions(-) > > -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/2] iio: Set correct iio name
On 2016-05-27 12:58 AM, Yong Li wrote: 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. The change looks technically correct, just a question about if these are also going upstream to the mainline kernel. Bruce Thanks Yong Li Yong Li (2): iio: tmp006: Set correct iio name iio: si7020: Set correct iio name drivers/iio/humidity/si7020.c| 2 +- drivers/iio/temperature/tmp006.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
