From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: <vkoul@kernel.org>, <robh+dt@kernel.org>
Cc: <dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<dan.j.williams@intel.com>, <devicetree@vger.kernel.org>
Subject: Re: [RFC 3/3] dmaengine: Support for requesting channels preferring DMA domain controller
Date: Sun, 8 Sep 2019 10:46:05 +0300 [thread overview]
Message-ID: <a409fb40-c8d7-2f0d-20fb-1786b2cbe6fd@ti.com> (raw)
In-Reply-To: <20190906141816.24095-4-peter.ujfalusi@ti.com>
On 06/09/2019 17.18, Peter Ujfalusi wrote:
> In case the channel is not requested via the slave API, use the
> of_find_dma_domain() to see if a system default DMA controller is
> specified.
>
> Add new function which can be used by clients to request channels by mask
> from their DMA domain controller if specified.
>
> Client drivers can take advantage of the domain support by moving from
> dma_request_chan_by_mask() to dma_domain_request_chan_by_mask()
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> ---
> drivers/dma/dmaengine.c | 17 ++++++++++++-----
> include/linux/dmaengine.h | 9 ++++++---
> 2 files changed, 18 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/dma/dmaengine.c b/drivers/dma/dmaengine.c
> index 6baddf7dcbfd..087450eed68c 100644
> --- a/drivers/dma/dmaengine.c
> +++ b/drivers/dma/dmaengine.c
> @@ -640,6 +640,10 @@ struct dma_chan *__dma_request_channel(const dma_cap_mask_t *mask,
> struct dma_device *device, *_d;
> struct dma_chan *chan = NULL;
>
> + /* If np is not specified, get the default DMA domain controller */
> + if (!np)
> + np = of_find_dma_domain(NULL);
> +
> /* Find a channel */
> mutex_lock(&dma_list_mutex);
> list_for_each_entry_safe(device, _d, &dma_device_list, global_node) {
> @@ -751,19 +755,22 @@ struct dma_chan *dma_request_slave_channel(struct device *dev,
> EXPORT_SYMBOL_GPL(dma_request_slave_channel);
>
> /**
> - * dma_request_chan_by_mask - allocate a channel satisfying certain capabilities
> - * @mask: capabilities that the channel must satisfy
> + * dma_domain_request_chan_by_mask - allocate a channel by mask from DMA domain
> + * @dev: pointer to client device structure
> + * @mask: capabilities that the channel must satisfy
> *
> * Returns pointer to appropriate DMA channel on success or an error pointer.
> */
> -struct dma_chan *dma_request_chan_by_mask(const dma_cap_mask_t *mask)
> +struct dma_chan *dma_domain_request_chan_by_mask(struct device *dev,
> + const dma_cap_mask_t *mask)
> {
> struct dma_chan *chan;
>
> if (!mask)
> return ERR_PTR(-ENODEV);
>
> - chan = __dma_request_channel(mask, NULL, NULL, NULL);
if (dev)
> + chan = __dma_request_channel(mask, NULL, NULL,
> + of_find_dma_domain(dev->of_node));else
chan = __dma_request_channel(mask, NULL, NULL, NULL);
> if (!chan) {
> mutex_lock(&dma_list_mutex);
> if (list_empty(&dma_device_list))
> @@ -775,7 +782,7 @@ struct dma_chan *dma_request_chan_by_mask(const dma_cap_mask_t *mask)
>
> return chan;
> }
> -EXPORT_SYMBOL_GPL(dma_request_chan_by_mask);
> +EXPORT_SYMBOL_GPL(dma_domain_request_chan_by_mask);
>
> void dma_release_channel(struct dma_chan *chan)
> {
> diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
> index 3b2e8e302f6c..9f94df81e83f 100644
> --- a/include/linux/dmaengine.h
> +++ b/include/linux/dmaengine.h
> @@ -1438,7 +1438,8 @@ struct dma_chan *__dma_request_channel(const dma_cap_mask_t *mask,
> struct dma_chan *dma_request_slave_channel(struct device *dev, const char *name);
>
> struct dma_chan *dma_request_chan(struct device *dev, const char *name);
> -struct dma_chan *dma_request_chan_by_mask(const dma_cap_mask_t *mask);
> +struct dma_chan *dma_domain_request_chan_by_mask(struct device *dev,
> + const dma_cap_mask_t *mask);
>
> void dma_release_channel(struct dma_chan *chan);
> int dma_get_slave_caps(struct dma_chan *chan, struct dma_slave_caps *caps);
> @@ -1475,8 +1476,8 @@ static inline struct dma_chan *dma_request_chan(struct device *dev,
> {
> return ERR_PTR(-ENODEV);
> }
> -static inline struct dma_chan *dma_request_chan_by_mask(
> - const dma_cap_mask_t *mask)
> +static inline struct dma_chan *dma_domain_request_chan_by_mask(struct device *dev,
> + const dma_cap_mask_t *mask)
> {
> return ERR_PTR(-ENODEV);
> }
> @@ -1537,6 +1538,8 @@ struct dma_chan *dma_get_any_slave_channel(struct dma_device *device);
> __dma_request_channel(&(mask), x, y, NULL)
> #define dma_request_slave_channel_compat(mask, x, y, dev, name) \
> __dma_request_slave_channel_compat(&(mask), x, y, dev, name)
> +#define dma_request_chan_by_mask(mask) \
> + dma_domain_request_chan_by_mask(NULL, mask)
>
> static inline struct dma_chan
> *__dma_request_slave_channel_compat(const dma_cap_mask_t *mask,
>
- Péter
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2019-09-08 7:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 14:18 [RFC 0/3] dmaengine: Support for DMA domain controllers Peter Ujfalusi
2019-09-06 14:18 ` [RFC 1/3] dt-bindings: dma: Add documentation for DMA domains Peter Ujfalusi
2019-09-08 7:47 ` Peter Ujfalusi
2019-09-08 12:10 ` Vinod Koul
2019-09-09 6:30 ` Peter Ujfalusi
2019-09-12 17:03 ` Vinod Koul
2019-09-13 7:21 ` Peter Ujfalusi
2019-09-13 10:36 ` Vinod Koul
2019-09-13 12:19 ` Peter Ujfalusi
2019-09-13 13:33 ` Vinod Koul
2019-09-08 12:06 ` Vinod Koul
2019-09-09 6:00 ` Peter Ujfalusi
2019-09-06 14:18 ` [RFC 2/3] dmaengine: of_dma: Function to look up the DMA domain of a client Peter Ujfalusi
2019-09-08 12:12 ` Vinod Koul
2019-09-06 14:18 ` [RFC 3/3] dmaengine: Support for requesting channels preferring DMA domain controller Peter Ujfalusi
2019-09-08 7:46 ` Peter Ujfalusi [this message]
2019-09-08 12:15 ` Vinod Koul
2019-09-09 5:56 ` Peter Ujfalusi
2019-09-12 16:49 ` Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2019-09-06 14:17 [RFC 0/3] dmaengine: Support for DMA domain controllers Peter Ujfalusi
2019-09-06 14:17 ` [RFC 3/3] dmaengine: Support for requesting channels preferring DMA domain controller Peter Ujfalusi
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=a409fb40-c8d7-2f0d-20fb-1786b2cbe6fd@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).