From: Vinod Koul <vinod.koul@intel.com>
To: Stanimir Varbanov <stanimir.varbanov@linaro.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2] dmaengine: bam-dma: fix a warning about missing capabilities
Date: Thu, 5 Mar 2015 21:45:27 +0530 [thread overview]
Message-ID: <20150305161527.GH2613@intel.com> (raw)
In-Reply-To: <1425560584-3721-1-git-send-email-stanimir.varbanov@linaro.org>
On Thu, Mar 05, 2015 at 03:03:04PM +0200, Stanimir Varbanov wrote:
> Avoid the warning below triggered during dmaengine async device
> registration.
>
> WARNING: CPU: 1 PID: 1 at linux/drivers/dma/dmaengine.c:863
> dma_async_device_register+0x2a8/0x4b8()
> this driver doesn't support generic slave capabilities reporting
>
> To do that fill mandatory .directions bit mask,
> .src/dst_addr_widths and .residue_granularity dma_device fields
> with appropriate values.
>
Applied, thanks
--
~Vinod
> Signed-off-by: Stanimir Varbanov <stanimir.varbanov@linaro.org>
> ---
>
> v1 -> v2
>
> - the patch subject has been changed
> - now fill also .residue_granularity and src/dts_addr_widths
> - added the warning in patch description
>
> v1 can be found at https://lkml.org/lkml/2015/3/4/896
>
> drivers/dma/qcom_bam_dma.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/dma/qcom_bam_dma.c b/drivers/dma/qcom_bam_dma.c
> index c3113e3..9c914d6 100644
> --- a/drivers/dma/qcom_bam_dma.c
> +++ b/drivers/dma/qcom_bam_dma.c
> @@ -1143,6 +1143,10 @@ static int bam_dma_probe(struct platform_device *pdev)
> dma_cap_set(DMA_SLAVE, bdev->common.cap_mask);
>
> /* initialize dmaengine apis */
> + bdev->common.directions = BIT(DMA_DEV_TO_MEM) | BIT(DMA_MEM_TO_DEV);
> + bdev->common.residue_granularity = DMA_RESIDUE_GRANULARITY_SEGMENT;
> + bdev->common.src_addr_widths = DMA_SLAVE_BUSWIDTH_4_BYTES;
> + bdev->common.dst_addr_widths = DMA_SLAVE_BUSWIDTH_4_BYTES;
> bdev->common.device_alloc_chan_resources = bam_alloc_chan;
> bdev->common.device_free_chan_resources = bam_free_chan;
> bdev->common.device_prep_slave_sg = bam_prep_slave_sg;
> --
> 1.7.0.4
>
--
next prev parent reply other threads:[~2015-03-05 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 13:03 [PATCH v2] dmaengine: bam-dma: fix a warning about missing capabilities Stanimir Varbanov
2015-03-05 16:15 ` Vinod Koul [this message]
2015-03-05 16:29 ` Stanimir Varbanov
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=20150305161527.GH2613@intel.com \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stanimir.varbanov@linaro.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