From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
Cc: quic_tdas@quicinc.com, andersson@kernel.org, konradybcio@kernel.org
Subject: Re: [PATCH v2] spi: Add support for Double Transfer Rate (DTR) mode
Date: Mon, 14 Apr 2025 11:03:39 +0100 [thread overview]
Message-ID: <174462501993.12165.4079866099404006000.b4-ty@kernel.org> (raw)
In-Reply-To: <20250404135427.313825-1-quic_msavaliy@quicinc.com>
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
prev parent reply other threads:[~2025-04-14 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 13:54 Mukesh Kumar Savaliya
2025-04-14 10:03 ` Mark Brown [this message]
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=174462501993.12165.4079866099404006000.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=andersson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_tdas@quicinc.com \
/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®