public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [meta][PATCH 02/11] linux-yocto/6.18: genericarm64: fix configuration audit warning
Date: Mon, 23 Mar 2026 09:50:48 -0400	[thread overview]
Message-ID: <20260323135057.1605923-3-bruce.ashfield@gmail.com> (raw)
In-Reply-To: <20260323135057.1605923-1-bruce.ashfield@gmail.com>

From: Bruce Ashfield <bruce.ashfield@gmail.com>

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 <krzysztof.kozlowski@oss.qualcomm.com>
      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 <krzysztof.kozlowski@oss.qualcomm.com>
          Reviewed-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
          Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
          Signed-off-by: Linus Walleij <linusw@kernel.org>
          Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

    And is causing an audit warning, so we drop our assignement

    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_6.18.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.18.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_6.18.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

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 <version>/base branch, which is pure upstream -stable, and the same
-- 
2.43.0



  parent reply	other threads:[~2026-03-23 13:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 13:50 [PATCH 0/11] linux-yocto: consolidated pull request bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 01/11] linux-yocto/6.18: genericarm64: enable additional qcom drivers bruce.ashfield
2026-03-23 13:50 ` bruce.ashfield [this message]
2026-03-23 13:50 ` [meta][PATCH 03/11] linux-yocto/6.18: update to v6.18.16 bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 04/11] linux-yocto/6.18: update CVE exclusions (6.18.16) bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 05/11] linux-yocto/6.18: update to v6.18.18 bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 06/11] linux-yocto/6.18: update CVE exclusions (6.18.18) bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 07/11] linux-yocto-dev: bump to v7.0 bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 08/11] linux-yocto/6.18: update to v6.18.19 bruce.ashfield
2026-03-23 22:15   ` Richard Purdie
2026-03-24  0:25     ` Bruce Ashfield
2026-03-23 13:50 ` [meta][PATCH 09/11] linux-yocto/6.18: update CVE exclusions (6.18.19) bruce.ashfield
2026-03-23 13:50 ` [meta-yocto-bsp][PATCH 10/11] yocto-bsps: update to v6.18.18 bruce.ashfield
2026-03-23 14:01   ` Patchtest results for " patchtest
2026-03-23 13:50 ` [meta-yocto-bsp][PATCH 11/11] yocto-bsps: update to v6.18.19 bruce.ashfield
2026-03-23 14:01   ` Patchtest results for " patchtest

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260323135057.1605923-3-bruce.ashfield@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox