linux-kernel - Re: [PATCH] iommu/arm: Allow disabling Qualcomm support in arm_smmu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAE2F3rB-ACt2rdVFYSpSap=t_poTi0-PxhgrYGg4vzjfic7vqA@mail.gmail.com>
Date: Tue, 11 Mar 2025 10:55:11 -0700
From: Daniel Mentz <danielmentz@...gle.com>
To: Aaron Kling <webgeek1234@...il.com>
Cc: Robin Murphy <robin.murphy@....com>, Joerg Roedel <joro@...tes.org>, Will Deacon <will@...nel.org>, 
	Arnd Bergmann <arnd@...db.de>, iommu@...ts.linux.dev, linux-kernel@...r.kernel.org, 
	stable@...r.kernel.org
Subject: Re: [PATCH] iommu/arm: Allow disabling Qualcomm support in arm_smmu_v3

On Mon, Mar 10, 2025 at 9:51 AM Aaron Kling <webgeek1234@...il.com> wrote:
> I am working with the android kernel. The more recent setup enables a
> minimal setup of configs in a core kernel that works across all
> supported arch's, then requires further support to all be modules. I
> specifically am working with tegra devices. But as ARCH_QCOM is
> enabled in the core defconfig, when I build smmuv3 as a module, I end
> up with a dependency on qcom-scm which gets built as an additional
> module. And it would be preferable to not require qcom modules to boot
> a tegra device.

If you want to build arm_smmu_v3.ko, you'd have

# CONFIG_ARM_SMMU is not set
CONFIG_ARM_SMMU_V3=m

in your .config. I don't see how this would enable ARM_SMMU_QCOM or QCOM_SCM.