linux-kernel - Re: [PATCH] spi: tegra114: Preserve SPI mode bits in def_command1

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] [day] [month] [year] [list]

Message-Id: <177033714083.233295.17808462615832612540.b4-ty@kernel.org>
Date: Fri, 06 Feb 2026 00:19:00 +0000
From: Mark Brown <broonie@...nel.org>
To: Vishwaroop A <va@...dia.com>
Cc: Laxman Dewangan <ldewangan@...dia.com>, 
 Thierry Reding <thierry.reding@...il.com>, 
 Jonathan Hunter <jonathanh@...dia.com>, linux-spi@...r.kernel.org, 
 linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: tegra114: Preserve SPI mode bits in
 def_command1_reg

On Wed, 04 Feb 2026 14:12:12 +0000, Vishwaroop A wrote:
> The COMMAND1 register bits [29:28] set the SPI mode, which controls
> the clock idle level. When a transfer ends, tegra_spi_transfer_end()
> writes def_command1_reg back to restore the default state, but this
> register value currently lacks the mode bits. This results in the
> clock always being configured as idle low, breaking devices that
> need it high.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: tegra114: Preserve SPI mode bits in def_command1_reg
      commit: a0a75b40c919b9f6d3a0b6c978e6ccf344c1be5a

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