linux-kernel - Re: [PATCH V4 1/2] dt-bindings: spi: tegra: Document IOMMU property for Tegra234 QSPI

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 for Android: free password hash cracker in your pocket

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

Message-Id: <174730846801.345421.6379001926087017421.b4-ty@kernel.org>
Date: Thu, 15 May 2025 13:27:48 +0200
From: Mark Brown <broonie@...nel.org>
To: krzk@...nel.org, robh@...nel.org, krzk+dt@...nel.org, 
 conor+dt@...nel.org, thierry.reding@...il.com, jonathanh@...dia.com, 
 skomatineni@...dia.com, ldewangan@...dia.com, kyarlagadda@...dia.com, 
 smangipudi@...dia.com, bgriffis@...dia.com, linux-spi@...r.kernel.org, 
 devicetree@...r.kernel.org, linux-tegra@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Vishwaroop A <va@...dia.com>
Subject: Re: [PATCH V4 1/2] dt-bindings: spi: tegra: Document IOMMU
 property for Tegra234 QSPI

On Tue, 13 May 2025 20:00:42 +0000, Vishwaroop A wrote:
> Add the 'iommus' property to the Tegra QSPI device tree binding.
> The property is needed for Tegra234 when using the internal DMA
> controller, and is not supported on other Tegra chips, as DMA is
> handled by an external controller.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/2] dt-bindings: spi: tegra: Document IOMMU property for Tegra234 QSPI
      commit: 4614fd6342ab69feebb067d5db84a9bfb9aada9f
[2/2] spi: tegra210-quad: Add support for internal DMA
      commit: 017f1b0bae08e8b456cf35cbdaae93ec19b50f0a

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark