linux-kernel - Re: [PATCH v2] spi: Add support for Double Transfer Rate (DTR) mode

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: <174462501993.12165.4079866099404006000.b4-ty@kernel.org>
Date: Mon, 14 Apr 2025 11:03:39 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>
Cc: quic_tdas@...cinc.com, andersson@...nel.org, konradybcio@...nel.org
Subject: Re: [PATCH v2] spi: Add support for Double Transfer Rate (DTR)
 mode

On Fri, 04 Apr 2025 19:24:27 +0530, Mukesh Kumar Savaliya wrote:
> Introduce support for protocol drivers to specify whether a transfer
> should use single or dual transfer mode. Currently, the SPI controller
> cannot determine this information from the user, leading to potential
> limitations in transfer capabilities.
> 
> Add a new field `dtr_mode` in the `spi_transfer` structure. The `dtr_mode`
> field allows protocol drivers to indicate if Double Transfer Rate (DTR)
> mode is supported for a given transfer. When `dtr_mode` is set to true,
> the SPI controller will use DTR mode; otherwise, it will default to single
> transfer mode.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: Add support for Double Transfer Rate (DTR) mode
      commit: 88113e09ada52be28968aacf4af7b3d667832f00

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