From: Sasha Levin <sashal@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Sumit Garg <sumit.garg@oss.qualcomm.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
kernel test robot <lkp@intel.com>,
Abel Vesa <abelvesa@kernel.org>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bartosz Golaszewski <brgl@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware: qcom: scm: Hide QCOM_SCM instead of depending on ARCH_QCOM
Date: Sun, 22 Nov 2026 10:28:50 -0500 [thread overview]
Message-ID: <20261122152850.1113916-1-sashal@kernel.org> (raw)
In-Reply-To: <20261122051636.GA2630332@ax162>
On Sat, Nov 21, 2026 at 10:16:36PM -0700, Nathan Chancellor wrote:
> This now allows
>
> # CONFIG_ARCH_QCOM is not set
> CONFIG_QCOM_SCM=m
> CONFIG_QCOM_TZMEM=m
> # CONFIG_QCOM_TZMEM_MODE_GENERIC is not set
> CONFIG_QCOM_TZMEM_MODE_SHMBRIDGE=y
>
> which breaks the build (or install if depmod is postponed until then)
> for me.
This is older than this patch. v7.3 gives the same config from your
allno.config and depmod fails the same way.
With SHM Bridge enabled, qcom_scm and qcom_tzmem call each other, so
they can't be two separate modules. That goes back to f86c61498a57
("firmware: qcom: tzmem: enable SHM Bridge support"), and it happens
with ARCH_QCOM=y too.
I sent a patch that builds qcom_tzmem into the qcom-scm module:
[PATCH] firmware: qcom: Build the TrustZone memory allocator into qcom-scm
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-22 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 17:30 Sasha Levin
2026-09-14 7:36 ` Geert Uytterhoeven
2026-09-25 16:43 ` Bjorn Andersson
2026-11-22 5:16 ` Nathan Chancellor
2026-11-22 15:28 ` Sasha Levin [this message]
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=20261122152850.1113916-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=brgl@kernel.org \
--cc=geert+renesas@glider.be \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nathan@kernel.org \
--cc=sumit.garg@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®