devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Pierre Yves MORDRET <pierre-yves.mordret@st.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre TORGUE <alexandre.torgue@st.com>,
	Russell King <linux@armlinux.org.uk>,
	Dan Williams <dan.j.williams@intel.com>,
	M'boumba Cedric Madianga <cedric.madianga@gmail.com>,
	Fabrice GASNIER <fabrice.gasnier@st.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Fabien DESSENNE <fabien.dessenne@st.com>,
	Amelie DELAUNAY <amelie.delaunay@st.com>,
	"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/5] dmaengine: Add STM32 DMAMUX driver
Date: Wed, 2 Aug 2017 10:25:22 +0530	[thread overview]
Message-ID: <20170802045522.GU3053@localhost> (raw)
In-Reply-To: <e3a76a50-4160-d111-cce9-132b46b66c33@st.com>

On Tue, Aug 01, 2017 at 09:32:50AM +0000, Pierre Yves MORDRET wrote:
> 
> 
> On 07/31/2017 02:31 PM, Vinod Koul wrote:
> > On Wed, Jul 26, 2017 at 07:38:02AM +0000, Pierre Yves MORDRET wrote:
> >>>>>> +
> >>>>>> +#ifndef __DMA_STM32_DMAMUX_H
> >>>>>> +#define __DMA_STM32_DMAMUX_H
> >>>>>> +
> >>>>>> +#if defined(CONFIG_STM32_DMAMUX)
> >>>>>> +int stm32_dmamux_set_config(struct device *dev, void *route_data, u32 chan_id);
> >>>>>
> >>>>> Why do we need a custom API in this case?
> >>>>>
> >>>>
> >>>> This API is called by DMA when a slave is requested by client. DMA can work
> >>>> without DMAMUX this API has been put in place to configure DMAMUX whether client
> >>>> is requesting a DMAMUX Channel instead of a DMA one.
> >>>
> >>> You mean the dmaengine driver right?
> >>>
> >>
> >> Yes. The API is mainly called by "device_config" through out STM32 DMA Driver
> >> when a router is in place for client.
> >> Please refer to Patch 4/5 on this set.
> > 
> > Okay am thinking on why this can't be generic..? An optional router config
> > callback?
> > 
> 
> I would have liked to answer there is a callback within engine but unfortunately
> I didn't figure out one when I did my router's development. I've looked once
> more but again I can't find how to map chanID and request line without custom API.

Yes there is no callback for routers but we can add a generic callback
here to be used. I added Peter for his comments, isn't that something they
need too?

-- 
~Vinod

  reply	other threads:[~2017-08-02  4:55 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 12:20 [PATCH v3 0/5] Add STM32 DMAMUX support Pierre-Yves MORDRET
     [not found] ` <1499343623-5964-1-git-send-email-pierre-yves.mordret-qxv4g6HH51o@public.gmane.org>
2017-07-06 12:20   ` [PATCH v3 1/5] dt-bindings: Document the STM32 DMAMUX bindings Pierre-Yves MORDRET
     [not found]     ` <1499343623-5964-2-git-send-email-pierre-yves.mordret-qxv4g6HH51o@public.gmane.org>
2017-07-10  3:56       ` Rob Herring
2017-07-20  9:42   ` [PATCH v3 0/5] Add STM32 DMAMUX support Pierre Yves MORDRET
2017-07-06 12:20 ` [PATCH v3 2/5] dmaengine: Add STM32 DMAMUX driver Pierre-Yves MORDRET
     [not found]   ` <1499343623-5964-3-git-send-email-pierre-yves.mordret-qxv4g6HH51o@public.gmane.org>
2017-07-22  6:51     ` Vinod Koul
2017-07-24 13:55       ` Pierre Yves MORDRET
     [not found]         ` <2b916330-9b65-f4d5-817f-79b66cc236b3-qxv4g6HH51o@public.gmane.org>
2017-07-26  5:29           ` Vinod Koul
2017-07-26  7:38             ` Pierre Yves MORDRET
     [not found]               ` <f2908e38-dc4d-3886-4058-52a7ad845415-qxv4g6HH51o@public.gmane.org>
2017-07-31 12:31                 ` Vinod Koul
2017-08-01  9:32                   ` Pierre Yves MORDRET
2017-08-02  4:55                     ` Vinod Koul [this message]
2017-08-02  9:19                       ` Peter Ujfalusi
2017-08-02 13:11                         ` Pierre Yves MORDRET
2017-08-02 14:09                           ` Peter Ujfalusi
2017-08-02 14:28                             ` Pierre Yves MORDRET
2017-08-03  6:42                               ` Peter Ujfalusi
2017-08-03  9:00                                 ` Pierre Yves MORDRET
2017-08-03  9:48                                   ` Peter Ujfalusi
2017-08-04 12:50                                     ` Pierre Yves MORDRET
2017-08-04 14:21                                       ` Peter Ujfalusi
     [not found]                                         ` <6e8e19f1-8d0f-183b-e02f-1ec8c4dd57b3-l0cyMroinI0@public.gmane.org>
2017-08-21  9:34                                           ` Pierre Yves MORDRET
2017-08-24  5:47                                             ` Peter Ujfalusi
     [not found]                                               ` <d1cc3cbb-c4aa-2acc-91ff-1d6713cb8867-l0cyMroinI0@public.gmane.org>
2017-08-24 13:03                                                 ` Pierre Yves MORDRET
     [not found]                                                   ` <ea66ba14-fe18-cb83-5989-8ae7b3ab50c6-qxv4g6HH51o@public.gmane.org>
2017-08-28 11:48                                                     ` Peter Ujfalusi
2017-08-30  8:02                                                       ` Pierre Yves MORDRET
2017-07-06 12:20 ` [PATCH v3 3/5] dt-bindings: stm32-dma: Add property to handle STM32 DMAMUX Pierre-Yves MORDRET
2017-07-10  3:57   ` Rob Herring
2017-07-06 12:20 ` [PATCH v3 4/5] dmaengine: stm32-dma: Add support for " Pierre-Yves MORDRET
2017-07-06 12:20 ` [PATCH v3 5/5] ARM: configs: stm32: Add DMAMUX support in STM32 defconfig Pierre-Yves MORDRET

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=20170802045522.GU3053@localhost \
    --to=vinod.koul@intel.com \
    --cc=alexandre.torgue@st.com \
    --cc=amelie.delaunay@st.com \
    --cc=cedric.madianga@gmail.com \
    --cc=dan.j.williams@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=fabien.dessenne@st.com \
    --cc=fabrice.gasnier@st.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=pierre-yves.mordret@st.com \
    --cc=robh+dt@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).