From: Bruce Ashfield Date: Mon, 23 Mar 2026 13:50:48 +0000 (-0400) Subject: linux-yocto/6.18: genericarm64: fix configuration audit warning X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=9f892aaa55e47f6c92fcee64ab05923626809fae;p=thirdparty%2Fopenembedded%2Fopenembedded-core.git linux-yocto/6.18: genericarm64: fix configuration audit warning Integrating the following commit(s) to linux-yocto/.: 1/1 [ Author: Bruce Ashfield Email: bruce.ashfield@gmail.com Subject: genericarm64: drop CONFIG_PINCTRL_SM8350_LPASS_LPI Date: Tue, 3 Mar 2026 11:48:55 -0500 It has been removed upstream: commit 112d4978099700bcf5e3a4a7e571cf672188f3bc Author: Krzysztof Kozlowski Date: Thu Jan 8 11:07:22 2026 +0100 pinctrl: qcom: sm8350-lpass-lpi: Merge with SC7280 to fix I2S2 and SWR TX pins commit 1fbe3abb449c5ef2178e1c3e3e8b9a43a7a410ac upstream. Qualcomm SC7280 and SM8350 SoCs have slightly different LPASS audio blocks (v9.4.5 and v9.2), however the LPASS LPI pin controllers are exactly the same. The driver for SM8350 has two issues, which can be fixed by simply moving over to SC7280 driver which has them correct: 1. "i2s2_data_groups" listed twice GPIO12, but should have both GPIO12 and GPIO13, 2. "swr_tx_data_groups" contained GPIO5 for "swr_tx_data2" function, but that function is also available on GPIO14, thus listing it twice is not necessary. OTOH, GPIO5 has also "swr_rx_data1", so selecting swr_rx_data function should not block the TX one. Fixes: be9f6d56381d ("pinctrl: qcom: sm8350-lpass-lpi: add SM8350 LPASS TLMM") Cc: stable@vger.kernel.org Signed-off-by: Krzysztof Kozlowski Reviewed-by: Bartosz Golaszewski Reviewed-by: Konrad Dybcio Signed-off-by: Linus Walleij Signed-off-by: Greg Kroah-Hartman And is causing an audit warning, so we drop our assignement Signed-off-by: Bruce Ashfield ] Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie --- diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_6.18.bb b/meta/recipes-kernel/linux/linux-yocto-rt_6.18.bb index 1b0eb015fe..ae06d6ed0d 100644 --- a/meta/recipes-kernel/linux/linux-yocto-rt_6.18.bb +++ b/meta/recipes-kernel/linux/linux-yocto-rt_6.18.bb @@ -16,7 +16,7 @@ python () { } SRCREV_machine ?= "9bd60c36af4be5a5905bb5408325961475e66880" -SRCREV_meta ?= "0b1ea0e509501b1bd4ba5ea8ccb2f3daf525ddec" +SRCREV_meta ?= "9b173d3a50825b8bffbb62ac6e504a7a56312e2e" SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine;protocol=https \ git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.18;destsuffix=${KMETA};protocol=https" diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_6.18.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_6.18.bb index 6782de4950..619fc8a59c 100644 --- a/meta/recipes-kernel/linux/linux-yocto-tiny_6.18.bb +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_6.18.bb @@ -19,7 +19,7 @@ KMETA = "kernel-meta" KCONF_BSP_AUDIT_LEVEL = "2" SRCREV_machine ?= "c9dde4c9d33d3635d3c6604a1bb0c62ea01b0f44" -SRCREV_meta ?= "0b1ea0e509501b1bd4ba5ea8ccb2f3daf525ddec" +SRCREV_meta ?= "9b173d3a50825b8bffbb62ac6e504a7a56312e2e" PV = "${LINUX_VERSION}+git" diff --git a/meta/recipes-kernel/linux/linux-yocto_6.18.bb b/meta/recipes-kernel/linux/linux-yocto_6.18.bb index a74520fcaa..f5ad28780e 100644 --- a/meta/recipes-kernel/linux/linux-yocto_6.18.bb +++ b/meta/recipes-kernel/linux/linux-yocto_6.18.bb @@ -29,7 +29,7 @@ SRCREV_machine:qemux86 ?= "c9dde4c9d33d3635d3c6604a1bb0c62ea01b0f44" SRCREV_machine:qemux86-64 ?= "c9dde4c9d33d3635d3c6604a1bb0c62ea01b0f44" SRCREV_machine:qemumips64 ?= "9fb4ff0187c85426f21fd40d4c61b742800f65c4" SRCREV_machine ?= "c9dde4c9d33d3635d3c6604a1bb0c62ea01b0f44" -SRCREV_meta ?= "0b1ea0e509501b1bd4ba5ea8ccb2f3daf525ddec" +SRCREV_meta ?= "9b173d3a50825b8bffbb62ac6e504a7a56312e2e" # set your preferred provider of linux-yocto to 'linux-yocto-upstream', and you'll # get the /base branch, which is pure upstream -stable, and the same