Skip to contentSkip to conversation

linux-yocto/4.4: updated pull request

PATCH New Bruce Ashfield 1 participant 4 messages Mar 8, 2016

lore
Share & tools
lore
#0 lore raw

cover linux-yocto/4.4: updated pull request

Hi all,

Ross pointed out that the AB found some issues with lttng when the refactored kernel types change was included (missing modules).

I previously sent patch [linux-yocto/kernel-meta: ktype refactoring: move DEBUG_KERNEL, EXPERT and EMBEDDED], and I've included it in this updated pull
request, but it is unchanged.

The new parts are a backport for wilwifi stability, and a patch that fixes up the tracing configuration of the "production" kernel type.

I thought about squashing the ftrace fixup, with the refactored patch, but keeping them separate is better in the history .. since it highlights some of the issues when we rely on default/selected values.

Cheers,

Bruce

The following changes since commit 5ac3dc76a5afc2ed35b1abfc8e330e0c580eadf0:

image.bbclass: fix incomplete .rootfs customization (2016-03-07 22:10:54 +0000)

are available in the git repository at:

git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (3):
linux-yocto/kernel-meta: ktype refactoring: move DEBUG_KERNEL, EXPERT and EMBEDDED linux-yocto/4.4: iwlwifi: mvm: don't allow sched scans without matches to be started linux-yocto/4.4: explicitly enable ftrace in tracing fragment

 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_4.4.bb      | 18 +++++++++---------
 3 files changed, 13 insertions(+), 13 deletions(-)
Signature · 1 line
2.5.0
#1 lore raw

PATCH 1/3 linux-yocto/kernel-meta: ktype refactoring: move DEBUG_KERNEL, EXPERT and EMBEDDED

Integrating the folliwing patch series from Cal:

This patch series refactors the ktypes so that base and standard ktypes do not enable EMBEDDED, EXPERT, or DEBUG_KERNEL. The reason this decision was made is because production platforms likely do not want DEBUG_KERNEL enabled, and EMBEDDED selects EXPERT which selects DEBUG_KERNEL.

A new ktype called "developer" was also created. This ktype enables the options now missing from standard and base, making it easy to maintain the functionality of a BSP through simply swapping the ktype from standard to developer. The preempt-rt ktype is now based off of developer in order to maintain its functionality.

The new standard ktype does not include EMBEDDED, EXPERT, or DEBUG_KERNEL. Without DEBUG_KERNEL it loses a number of debug features that are selected by default. Without EXPERT it gains RFKILL_INPUT and DEBUG_MEMORY_INIT, while losing VMSPLIT_3G. These are only available to configure with CONFIG_EXPERT=y and default to EXPERT or !EXPERT. Not selecting EMBEDDED has no apparent impacts.

Some coordination is required for this change, as existing BSPs WILL be affected, and will either need to accept the changes in the standard ktype or move to the developer ktype.

California Sullivan (12):
features/debug: add debug-kernel feature
ktypes: add developer ktype
ktypes/base: Disable EMBEDDED and DEBUG_KERNEL
CONFIG_PROCESSOR_SELECT: do not enable intel-common-drivers.scc: move profiling and latencytop to a new file romley.scc remove profiling and latencytop features bsp/intel-common: add intel-core* developer BSPs preempt-rt.scc: include developer ktype instead of standard
intel-common: add intel-developer-drivers.scc to preempt-rt BSPs
CONFIG_I2C_I801: set option to yes in intel-core* BSPs
bsp: add developer common-pc BSPs
bsp: remove profiling and latencytop from non-developer common-pc BSPs

---
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.4.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb +1 -1
index 7251c07fce81..41619d7296a3 100644
@@ -3,7 +3,7 @@ KBRANCH ?= "standard/preempt-rt"
 require recipes-kernel/linux/linux-yocto.inc
 
 SRCREV_machine ?= "853991833cc5140ca25450e81bf6b822d537a6ac"
-SRCREV_meta ?= "8b6a7d80344837fd64163008521a31a6f891313e"
+SRCREV_meta ?= "da47accec6c17c22cecf064be1da29b5bf3d7583"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.4.git;branch=${KBRANCH};name=machine \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb +1 -1
index 0d35bc3ce8b0..5a0884a48706 100644
@@ -10,7 +10,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "ff4c4ef15b51f45b9106d71bf1f62fe7c02e63c2"
-SRCREV_meta ?= "8b6a7d80344837fd64163008521a31a6f891313e"
+SRCREV_meta ?= "da47accec6c17c22cecf064be1da29b5bf3d7583"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
meta/recipes-kernel/linux/linux-yocto_4.4.bb +1 -1
index c5f160d78691..9c3fe7f1dedb 100644
@@ -19,7 +19,7 @@ SRCREV_machine_qemux86 ?= "ff4c4ef15b51f45b9106d71bf1f62fe7c02e63c2"
 SRCREV_machine_qemux86-64 ?= "ff4c4ef15b51f45b9106d71bf1f62fe7c02e63c2"
 SRCREV_machine_qemumips64 ?= "8bbcb369cf605d1ada384f4b950da2abc5d1f4cc"
 SRCREV_machine ?= "ff4c4ef15b51f45b9106d71bf1f62fe7c02e63c2"
-SRCREV_meta ?= "8b6a7d80344837fd64163008521a31a6f891313e"
+SRCREV_meta ?= "da47accec6c17c22cecf064be1da29b5bf3d7583"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.4.git;name=machine;branch=${KBRANCH}; \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
Signature · 1 line
2.5.0
#2 lore raw

PATCH 2/3 linux-yocto/4.4: iwlwifi: mvm: don't allow sched scans without matches to be started

In reply to Bruce Ashfield

Integrating the following commit for improved iwlwifi support:

iwlwifi: mvm: don't allow sched scans without matches to be started

commit 5e56276e7555b34550d51459a801ff75eca8b907 upstream.

The firmware can perform a scheduled scan with not matchsets passed, but it can't send notification that results were found. Since the userspace then cannot know when we got new results and the firmware wouldn't trigger a wake in case we are sleeping, it's better not to allow scans without matchsets.

This fixes https://bugzilla.kernel.org/show_bug.cgi?id=110831

---
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb |  2 +-
 meta/recipes-kernel/linux/linux-yocto_4.4.bb      | 16 ++++++++--------
 3 files changed, 10 insertions(+), 10 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb +1 -1
index 41619d7296a3..d24c119973d7 100644
@@ -2,7 +2,7 @@ KBRANCH ?= "standard/preempt-rt"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-SRCREV_machine ?= "853991833cc5140ca25450e81bf6b822d537a6ac"
+SRCREV_machine ?= "19e3ed348aefd0802dc8747cc143bea1155edc12"
 SRCREV_meta ?= "da47accec6c17c22cecf064be1da29b5bf3d7583"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.4.git;branch=${KBRANCH};name=machine \
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb +1 -1
index 5a0884a48706..c31f637155b2 100644
@@ -9,7 +9,7 @@ LINUX_VERSION ?= "4.4.3"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "ff4c4ef15b51f45b9106d71bf1f62fe7c02e63c2"
+SRCREV_machine ?= "dadb4369046246d7788db1f3cdf0a34298e35b4b"
 SRCREV_meta ?= "da47accec6c17c22cecf064be1da29b5bf3d7583"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
meta/recipes-kernel/linux/linux-yocto_4.4.bb +8 -8
index 9c3fe7f1dedb..ba39bb48dbf5 100644
@@ -11,14 +11,14 @@ KBRANCH_qemux86  ?= "standard/base"
 KBRANCH_qemux86-64 ?= "standard/base"
 KBRANCH_qemumips64 ?= "standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "fa6a2f888d8adfe03b24ef32654be470960aed41"
-SRCREV_machine_qemuarm64 ?= "ff4c4ef15b51f45b9106d71bf1f62fe7c02e63c2"
-SRCREV_machine_qemumips ?= "a23b6eb1c5bca3bde2a9f94d9059274fff7da281"
-SRCREV_machine_qemuppc ?= "ff4c4ef15b51f45b9106d71bf1f62fe7c02e63c2"
-SRCREV_machine_qemux86 ?= "ff4c4ef15b51f45b9106d71bf1f62fe7c02e63c2"
-SRCREV_machine_qemux86-64 ?= "ff4c4ef15b51f45b9106d71bf1f62fe7c02e63c2"
-SRCREV_machine_qemumips64 ?= "8bbcb369cf605d1ada384f4b950da2abc5d1f4cc"
-SRCREV_machine ?= "ff4c4ef15b51f45b9106d71bf1f62fe7c02e63c2"
+SRCREV_machine_qemuarm ?= "d3ce63d0c83f579605b308f83c62a49e5dbf73e6"
+SRCREV_machine_qemuarm64 ?= "dadb4369046246d7788db1f3cdf0a34298e35b4b"
+SRCREV_machine_qemumips ?= "06c34af69f436c8dca8ff23a30a7d1f834e1d07c"
+SRCREV_machine_qemuppc ?= "dadb4369046246d7788db1f3cdf0a34298e35b4b"
+SRCREV_machine_qemux86 ?= "dadb4369046246d7788db1f3cdf0a34298e35b4b"
+SRCREV_machine_qemux86-64 ?= "dadb4369046246d7788db1f3cdf0a34298e35b4b"
+SRCREV_machine_qemumips64 ?= "79b496614c5d0b4862796928ef9890f2eb375a3b"
+SRCREV_machine ?= "dadb4369046246d7788db1f3cdf0a34298e35b4b"
 SRCREV_meta ?= "da47accec6c17c22cecf064be1da29b5bf3d7583"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.4.git;name=machine;branch=${KBRANCH}; \
Signature · 1 line
2.5.0
#3 lore raw

PATCH 3/3 linux-yocto/4.4: explicitly enable ftrace in tracing fragment

In reply to Bruce Ashfield

The recent split/factoring between production and development kernel configurations, EXPERT, EMBEDDED and DEBUG_KERNEL are no longer selected for all kernel types. This means that ftrace is no longer selected by default in in standard BSPs, causing breakage in things that relied on it.

---
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_4.4.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb +1 -1
index d24c119973d7..eeca178f616f 100644
@@ -3,7 +3,7 @@ KBRANCH ?= "standard/preempt-rt"
 require recipes-kernel/linux/linux-yocto.inc
 
 SRCREV_machine ?= "19e3ed348aefd0802dc8747cc143bea1155edc12"
-SRCREV_meta ?= "da47accec6c17c22cecf064be1da29b5bf3d7583"
+SRCREV_meta ?= "89419d8b902aa81cb4c52f9dd12a6c9e083ce198"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.4.git;branch=${KBRANCH};name=machine \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb +1 -1
index c31f637155b2..b14eeaf1980b 100644
@@ -10,7 +10,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "dadb4369046246d7788db1f3cdf0a34298e35b4b"
-SRCREV_meta ?= "da47accec6c17c22cecf064be1da29b5bf3d7583"
+SRCREV_meta ?= "89419d8b902aa81cb4c52f9dd12a6c9e083ce198"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
meta/recipes-kernel/linux/linux-yocto_4.4.bb +1 -1
index ba39bb48dbf5..d9138688eda6 100644
@@ -19,7 +19,7 @@ SRCREV_machine_qemux86 ?= "dadb4369046246d7788db1f3cdf0a34298e35b4b"
 SRCREV_machine_qemux86-64 ?= "dadb4369046246d7788db1f3cdf0a34298e35b4b"
 SRCREV_machine_qemumips64 ?= "79b496614c5d0b4862796928ef9890f2eb375a3b"
 SRCREV_machine ?= "dadb4369046246d7788db1f3cdf0a34298e35b4b"
-SRCREV_meta ?= "da47accec6c17c22cecf064be1da29b5bf3d7583"
+SRCREV_meta ?= "89419d8b902aa81cb4c52f9dd12a6c9e083ce198"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.4.git;name=machine;branch=${KBRANCH}; \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.4;destsuffix=${KMETA}"
Signature · 1 line
2.5.0