From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: vinod.koul@intel.com, arnd@arndb.de, andy.shevchenko@gmail.com
Cc: linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
nsekhar@ti.com, tony@atomide.com
Subject: Re: [PATCH V02 3/5] dmaengine: core: Introduce new, universal API to request a channel
Date: Mon, 14 Dec 2015 22:39:38 +0200 [thread overview]
Message-ID: <566F290A.2060300@ti.com> (raw)
In-Reply-To: <1450092140-31602-4-git-send-email-peter.ujfalusi@ti.com>
On 12/14/2015 01:22 PM, Peter Ujfalusi wrote:
> /**
> + * struct dma_slave_map - associates slave device and it's slave channel with
> + * parameter to be used by a filter function
> + * @devname: name of the device
> + * @slave: slave channel name
> + * @param: opaque parameter to pass to struct dma_filter.fn
> + */
> +struct dma_slave_map {
> + const char *devname;
> + const char *slave;
> + void *param;
??? Tabs got replaced by spaces ???
> +};
> +
> +/**
> + * struct dma_filter - information for slave device/channel to filter_fn/param
> + * mapping
> + * @fn: filter function callback
> + * @mapcnt: number of slave device/channel in the map
> + * @map: array of channel to filter mapping data
> + */
> +struct dma_filter {
> + dma_filter_fn fn;
> + int mapcnt;
> + const struct dma_slave_map *map;
Here also.
--
Péter
WARNING: multiple messages have this Message-ID (diff)
From: peter.ujfalusi@ti.com (Peter Ujfalusi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V02 3/5] dmaengine: core: Introduce new, universal API to request a channel
Date: Mon, 14 Dec 2015 22:39:38 +0200 [thread overview]
Message-ID: <566F290A.2060300@ti.com> (raw)
In-Reply-To: <1450092140-31602-4-git-send-email-peter.ujfalusi@ti.com>
On 12/14/2015 01:22 PM, Peter Ujfalusi wrote:
> /**
> + * struct dma_slave_map - associates slave device and it's slave channel with
> + * parameter to be used by a filter function
> + * @devname: name of the device
> + * @slave: slave channel name
> + * @param: opaque parameter to pass to struct dma_filter.fn
> + */
> +struct dma_slave_map {
> + const char *devname;
> + const char *slave;
> + void *param;
??? Tabs got replaced by spaces ???
> +};
> +
> +/**
> + * struct dma_filter - information for slave device/channel to filter_fn/param
> + * mapping
> + * @fn: filter function callback
> + * @mapcnt: number of slave device/channel in the map
> + * @map: array of channel to filter mapping data
> + */
> +struct dma_filter {
> + dma_filter_fn fn;
> + int mapcnt;
> + const struct dma_slave_map *map;
Here also.
--
P?ter
WARNING: multiple messages have this Message-ID (diff)
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: <vinod.koul@intel.com>, <arnd@arndb.de>, <andy.shevchenko@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <dmaengine@vger.kernel.org>,
<linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <nsekhar@ti.com>,
<tony@atomide.com>
Subject: Re: [PATCH V02 3/5] dmaengine: core: Introduce new, universal API to request a channel
Date: Mon, 14 Dec 2015 22:39:38 +0200 [thread overview]
Message-ID: <566F290A.2060300@ti.com> (raw)
In-Reply-To: <1450092140-31602-4-git-send-email-peter.ujfalusi@ti.com>
On 12/14/2015 01:22 PM, Peter Ujfalusi wrote:
> /**
> + * struct dma_slave_map - associates slave device and it's slave channel with
> + * parameter to be used by a filter function
> + * @devname: name of the device
> + * @slave: slave channel name
> + * @param: opaque parameter to pass to struct dma_filter.fn
> + */
> +struct dma_slave_map {
> + const char *devname;
> + const char *slave;
> + void *param;
??? Tabs got replaced by spaces ???
> +};
> +
> +/**
> + * struct dma_filter - information for slave device/channel to filter_fn/param
> + * mapping
> + * @fn: filter function callback
> + * @mapcnt: number of slave device/channel in the map
> + * @map: array of channel to filter mapping data
> + */
> +struct dma_filter {
> + dma_filter_fn fn;
> + int mapcnt;
> + const struct dma_slave_map *map;
Here also.
--
Péter
next prev parent reply other threads:[~2015-12-14 20:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 11:22 [PATCH V02 0/5] dmaengine: New 'universal' API for requesting channel Peter Ujfalusi
2015-12-14 11:22 ` Peter Ujfalusi
2015-12-14 11:22 ` Peter Ujfalusi
2015-12-14 11:22 ` [PATCH V02 1/5] dmaengine: core: Skip mask matching when it is not provided to private_candidate Peter Ujfalusi
2015-12-14 11:22 ` Peter Ujfalusi
2015-12-14 11:22 ` Peter Ujfalusi
2015-12-14 11:22 ` [PATCH V02 2/5] dmaengine: core: Move and merge the code paths using private_candidate Peter Ujfalusi
2015-12-14 11:22 ` Peter Ujfalusi
2015-12-14 11:22 ` Peter Ujfalusi
2015-12-14 11:22 ` [PATCH V02 3/5] dmaengine: core: Introduce new, universal API to request a channel Peter Ujfalusi
2015-12-14 11:22 ` Peter Ujfalusi
2015-12-14 11:22 ` Peter Ujfalusi
2015-12-14 13:04 ` kbuild test robot
2015-12-14 13:04 ` kbuild test robot
2015-12-14 20:39 ` Peter Ujfalusi [this message]
2015-12-14 20:39 ` Peter Ujfalusi
2015-12-14 20:39 ` Peter Ujfalusi
2015-12-14 11:22 ` [PATCH V02 4/5] dmaengine: edma: Add support for DMA filter mapping to slave devices Peter Ujfalusi
2015-12-14 11:22 ` Peter Ujfalusi
2015-12-14 11:22 ` Peter Ujfalusi
2015-12-14 11:22 ` [PATCH V02 5/5] dmaengine: omap-dma: " Peter Ujfalusi
2015-12-14 11:22 ` Peter Ujfalusi
2015-12-14 11:22 ` Peter Ujfalusi
2015-12-14 11:32 ` [PATCH V02 0/5] dmaengine: New 'universal' API for requesting channel Arnd Bergmann
2015-12-14 11:32 ` Arnd Bergmann
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=566F290A.2060300@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=tony@atomide.com \
--cc=vinod.koul@intel.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.