From: Robin Murphy <robin.murphy@arm.com>
To: webgeek1234@gmail.com, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] iommu/arm: Allow disabling Qualcomm support in arm_smmu_v3
Date: Mon, 10 Mar 2025 12:42:10 +0000 [thread overview]
Message-ID: <6f5f2047-b315-440b-b57d-2ed0dd7395f6@arm.com> (raw)
In-Reply-To: <20250310-b4-qcom-smmu-v1-1-733a1398ff85@gmail.com>
On 2025-03-10 6:11 am, Aaron Kling via B4 Relay wrote:
> From: Aaron Kling <webgeek1234@gmail.com>
>
> If ARCH_QCOM is enabled when building arm_smmu_v3,
This has nothing to do with SMMUv3, though?
> a dependency on
> qcom-scm is added, which currently cannot be disabled. Add a prompt to
> ARM_SMMU_QCOM to allow disabling this dependency.
Why is that an issue - what problem arises from having the SCM driver
enabled? AFAICS it's also selected by plenty of other drivers including
pretty fundamental ones like pinctrl. If it is somehow important to
exclude the SCM driver, then I can't really imagine what the use-case
would be for building a kernel which won't work on most Qualcomm
platforms but not simply disabling ARCH_QCOM...
Thanks,
Robin.
> Fixes: 0f0f80d9d5db ("iommu/arm: fix ARM_SMMU_QCOM compilation")
> Cc: stable@vger.kernel.org
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---
> drivers/iommu/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig
> index ec1b5e32b9725bc1104d10e5d7a32af7b211b50a..cca0825551959e3f37cc2ea41aeae526fdb73312 100644
> --- a/drivers/iommu/Kconfig
> +++ b/drivers/iommu/Kconfig
> @@ -381,6 +381,7 @@ config ARM_SMMU_MMU_500_CPRE_ERRATA
>
> config ARM_SMMU_QCOM
> def_tristate y
> + prompt "Qualcomm SMMUv3 Support"
> depends on ARM_SMMU && ARCH_QCOM
> select QCOM_SCM
> help
>
> ---
> base-commit: 1110ce6a1e34fe1fdc1bfe4ad52405f327d5083b
> change-id: 20250310-b4-qcom-smmu-d4ccaf66a1ce
>
> Best regards,
next prev parent reply other threads:[~2025-03-10 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 6:11 Aaron Kling via B4 Relay
2025-03-10 12:42 ` Robin Murphy [this message]
2025-03-10 16:45 ` Aaron Kling
2025-03-10 19:52 ` Robin Murphy
2025-03-10 20:15 ` Aaron Kling
2025-03-11 17:29 ` Robin Murphy
2025-03-11 17:55 ` Daniel Mentz
2025-03-11 18:17 ` Aaron Kling
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=6f5f2047-b315-440b-b57d-2ed0dd7395f6@arm.com \
--to=robin.murphy@arm.com \
--cc=arnd@arndb.de \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=webgeek1234@gmail.com \
--cc=will@kernel.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
all inboxes | Powered by JetHome®