mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
To: Mark Brown <broonie@kernel.org>
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: Fri, 4 Apr 2025 19:23:40 +0530	[thread overview]
Message-ID: <e7b19ae8-9619-412c-8aec-fb822c44384d@quicinc.com> (raw)
In-Reply-To: <f3115251-8fa9-4019-8fb0-145daf32cfa2@sirena.org.uk>

Thanks Mark !

On 3/27/2025 7:37 PM, Mark Brown wrote:
> On Thu, Mar 27, 2025 at 03:33:15PM +0530, Mukesh Kumar Savaliya wrote:
> 
>> IIUC, It comes to the point of first identifying if it's in context of QSPI
>> controller or SPI controller right ?
> 
>> Identify if SPI/QSPI controller has this capability using dtr_caps =
>> true/false. Then check if it's supporting SDR/DDR mode. Can we then
>> introduce below struct to first mark capability as true/false and then
>> process dtr_mode ?
> 
>> if not supported (dtr_caps = false), then don't care dtr_mode.
> 
> We should complain if the device requsted anything the controller can't
> support.
> 
Yes, makes sense. i have added dtr_caps into controller data structure 
and validating it inside the __spi_validate().
>> struct spi_caps {
>> 	bool dtr_mode;
>> 	bool dtr_caps;
>> };
> 
> The controller capabilities are currently mainly advertised via the
> SPI_CONTROLLER_ flags but adding some bools also works, some things
> already do use that.  I'm not sure we need to wrap things in a further
> struct though.
Uploaded Patch V2. Please help review and suggest next. it may require 
still some fine stunning.


  reply	other threads:[~2025-04-04 13:53 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
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 [this message]
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=e7b19ae8-9619-412c-8aec-fb822c44384d@quicinc.com \
    --to=quic_msavaliy@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=broonie@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    /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®