All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: Joy Chakraborty <joychakr@google.com>,
	Mark Brown <broonie@kernel.org>,
	linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	manugautam@google.com, rohitner@google.com
Subject: Re: [PATCH v5 2/2] spi: dw: Add dma controller capability checks
Date: Tue, 11 Apr 2023 17:49:05 +0300	[thread overview]
Message-ID: <ZDVzYTWlaIN0PlCh@smile.fi.intel.com> (raw)
In-Reply-To: <20230411143758.2rpaxux6esiln26q@mobilestation>

On Tue, Apr 11, 2023 at 05:37:58PM +0300, Serge Semin wrote:
> On Tue, Apr 11, 2023 at 03:18:34PM +0300, Andy Shevchenko wrote:
> > On Thu, Mar 30, 2023 at 06:34:50AM +0000, Joy Chakraborty wrote:

...

> > > +	if (!(tx.directions & BIT(DMA_MEM_TO_DEV) &&
> > > +	      rx.directions & BIT(DMA_DEV_TO_MEM)))
> > > +		return -ENXIO;
> > 
> 
> > What about simplex transfers where we only care about sending or receiving data
> > and using dummy data for the other channel? Doesn't this make a regression for
> > that types of transfers? (Or, if we don't support such, this should be explained
> > in the commit message at least.)
> 
> I don't think the code above is that much relevant for the half-duplex
> transfers. The DW APB SSI-DMA driver requires both Tx and Rx channels
> being specified thus supporting the Full-duplex transfers at least in
> case of the TxRx and Rx-only SPI-transfers (the later case relies on
> having the dummy buffers supplied by the SPI-core). Thus the channels
> must support the corresponding DMA-directions.
> 
> Indeed the Tx-only DMA-based SPI-transfers implementation in the
> driver implies not using the Rx DMA-channel, but even in that case the
> Rx-channel still needs to be specified otherwise the DW APB SSI-DMA
> setup methods will halt with error returned. So unless there are cases
> with dummy Rx DMA-channels (which I very much doubt there is) I don't
> see the suggested update causing a regression. Am I missing something?

Okay, so since it's not a problem, can we explain this in the commit message
then? A summary of the above, perhaps?

...

> Do you still think otherwise?

Answered above.

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2023-04-11 14:49 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30  6:34 [PATCH v5 0/2] spi: dw: DW SPI DMA Driver updates Joy Chakraborty
2023-03-30  6:34 ` [PATCH v5 1/2] spi: dw: Add 32 bpw support to DW DMA Controller Joy Chakraborty
2023-04-11 12:13   ` Andy Shevchenko
2023-04-11 14:11     ` Serge Semin
2023-04-11 14:30       ` Joy Chakraborty
2023-04-11 14:39         ` Serge Semin
2023-04-11 14:46       ` Andy Shevchenko
2023-04-11 15:09         ` Serge Semin
2023-04-11 15:17           ` Andy Shevchenko
2023-04-11 15:18             ` Joy Chakraborty
2023-04-11 16:21               ` Andy Shevchenko
2023-04-11 19:41                 ` Joy Chakraborty
2023-04-12  9:21                   ` Joy Chakraborty
2023-04-12 13:24                     ` Andy Shevchenko
2023-04-13  4:07                       ` Joy Chakraborty
2023-04-13 13:47                         ` Serge Semin
2023-04-13 20:23                           ` Joy Chakraborty
2023-03-30  6:34 ` [PATCH v5 2/2] spi: dw: Add dma controller capability checks Joy Chakraborty
2023-04-11 12:18   ` Andy Shevchenko
2023-04-11 14:37     ` Serge Semin
2023-04-11 14:47       ` Serge Semin
2023-04-11 14:49       ` Andy Shevchenko [this message]
2023-04-11 15:00     ` Joy Chakraborty
2023-04-11 15:07       ` Joy Chakraborty
2023-04-11 15:15         ` Andy Shevchenko
2023-04-13 13:36           ` Serge Semin
2023-04-11 15:11       ` Andy Shevchenko
2023-04-11  5:12 ` [PATCH v5 0/2] spi: dw: DW SPI DMA Driver updates Serge Semin
2023-04-11 12:11   ` Andy Shevchenko

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=ZDVzYTWlaIN0PlCh@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=broonie@kernel.org \
    --cc=fancer.lancer@gmail.com \
    --cc=joychakr@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=manugautam@google.com \
    --cc=rohitner@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.