dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: Serge Semin <Sergey.Semin@baikalelectronics.ru>,
	dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	Viresh Kumar <vireshk@kernel.org>
Subject: Re: [PATCH v1 1/1] dmaengine: dw: Program xBAR hardware for Elkhart Lake
Date: Mon, 7 Jun 2021 15:30:12 +0300	[thread overview]
Message-ID: <YL4RVEIJrSMy+Slf@smile.fi.intel.com> (raw)
In-Reply-To: <YL4EYb35GOVYxdQO@vkoul-mobl>

On Mon, Jun 07, 2021 at 05:04:57PM +0530, Vinod Koul wrote:
> On 02-06-21, 11:56, Andy Shevchenko wrote:
> > Intel Elkhart Lake PSE DMA implementation is integrated with crossbar IP
> > in order to serve more hardware than there are DMA request lines available.
> > 
> > Due to this, program xBAR hardware to make flexible support of PSE peripheral.

...

> > -// Copyright (C) 2013,2018 Intel Corporation
> > +// Copyright (C) 2013,2018,2020 Intel Corporation
> 
> 2021..?

Actually 2020.
But I can add 2021.

...

> > +static unsigned int idma32_get_slave_devid(struct dw_dma_chan *dwc)
> > +{
> > +	struct device *slave = dwc->chan.slave;
> > +
> > +	if (!slave || !dev_is_pci(slave))
> > +		return 0;
> > +
> > +	return to_pci_dev(slave)->devfn;
> 
> so this return devfn.. maybe rename function to get_slave_devfn() ?

Will do in v2.

> > +}

...

> > +	switch (dwc->direction) {
> > +	case DMA_MEM_TO_MEM:
> > +		value |= CTL_CH_TRANSFER_MODE_D2D;
> > +		break;
> > +	case DMA_MEM_TO_DEV:
> > +		value |= CTL_CH_TRANSFER_MODE_D2S;
> > +		value |= CTL_CH_WR_NON_SNOOP_BIT;
> > +		break;
> > +	case DMA_DEV_TO_MEM:
> > +		value |= CTL_CH_TRANSFER_MODE_S2D;
> > +		value |= CTL_CH_RD_NON_SNOOP_BIT;
> > +		break;
> > +	case DMA_DEV_TO_DEV:
> > +	default:
> > +		value |= CTL_CH_WR_NON_SNOOP_BIT | CTL_CH_RD_NON_SNOOP_BIT;
> > +		value |= CTL_CH_TRANSFER_MODE_S2S;
> > +		break;
> 
> aha, how did you test this...

Not sure what the question is about. You are talking about last two cases
or the entire switch? Last two weren't tested, just filed for the sake of
being documented. First two were tested with SPI host controllers.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2021-06-07 12:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02  8:56 [PATCH v1 1/1] dmaengine: dw: Program xBAR hardware for Elkhart Lake Andy Shevchenko
2021-06-07 11:34 ` Vinod Koul
2021-06-07 12:30   ` Andy Shevchenko [this message]
2021-06-07 18:23     ` Vinod Koul

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=YL4RVEIJrSMy+Slf@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=Sergey.Semin@baikalelectronics.ru \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vireshk@kernel.org \
    --cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).