From: Mark Brown <broonie@kernel.org>
To: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
andersson@kernel.org, konradybcio@kernel.org
Subject: Re: [PATCH V1] spi: Add support for Double Transfer Rate (DTR) mode
Date: Wed, 26 Mar 2025 13:04:26 +0000 [thread overview]
Message-ID: <40db39ef-7ef3-4720-9c85-ccfe1c11c299@sirena.org.uk> (raw)
In-Reply-To: <20250326083954.3338597-1-quic_msavaliy@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
On Wed, Mar 26, 2025 at 02:09:54PM +0530, Mukesh Kumar Savaliya wrote:
> This change introduces 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.
> The QSPI controller driver uses this flag and configures single or double
> transfer rate using the controller register.
We should have a flag in the controller indicating if it supports this,
and code in the core which returns an error if a driver attempts to use
it when the controller doesn't support it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-03-26 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 8:39 Mukesh Kumar Savaliya
2025-03-26 9:21 ` Jyothi Kumar Seerapu
2025-03-26 12:55 ` Konrad Dybcio
2025-03-26 13:04 ` Mark Brown [this message]
2025-03-26 14:25 ` Mukesh Kumar Savaliya
2025-03-26 14:42 ` Mark Brown
2025-03-27 10:03 ` Mukesh Kumar Savaliya
2025-03-27 14:07 ` Mark Brown
2025-04-04 13:53 ` Mukesh Kumar Savaliya
2025-03-26 14:48 ` Tudor Ambarus
2025-03-27 10:10 ` Mukesh Kumar Savaliya
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=40db39ef-7ef3-4720-9c85-ccfe1c11c299@sirena.org.uk \
--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 \
/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®