From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] dmaengine: rcar-hpbdma: tidyup residue_granularity
Date: Wed, 21 Jan 2015 11:07:59 +0000 [thread overview]
Message-ID: <33068117.HPgfh8e0Et@avalon> (raw)
In-Reply-To: <87vbk0n3q3.wl%kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
Thank you for the patch.
On Wednesday 21 January 2015 04:42:22 Kuninori Morimoto wrote:
> From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>
> The driver doesn't support residue reporting at all.
> residue_granularity should be set to DMA_RESIDUE_GRANULARITY_DESCRIPTOR.
> Special thanks to Laurent
>
> Reported-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
I thought the plan was to fix this in v4 of "[PATCH v3] dmaengine:: rcar-
hpbdma: add dma_dev->directions" ?
> ---
> drivers/dma/sh/rcar-hpbdma.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma/sh/rcar-hpbdma.c b/drivers/dma/sh/rcar-hpbdma.c
> index 6fef1b9..749f26e 100644
> --- a/drivers/dma/sh/rcar-hpbdma.c
> +++ b/drivers/dma/sh/rcar-hpbdma.c
> @@ -600,7 +600,7 @@ static int hpb_dmae_probe(struct platform_device *pdev)
> dma_dev->src_addr_widths = widths;
> dma_dev->dst_addr_widths = widths;
> dma_dev->directions = BIT(DMA_MEM_TO_DEV) | BIT(DMA_DEV_TO_MEM);
> - dma_dev->residue_granularity = DMA_RESIDUE_GRANULARITY_BURST;
> + dma_dev->residue_granularity = DMA_RESIDUE_GRANULARITY_DESCRIPTOR;
>
> hpbdev->shdma_dev.ops = &hpb_dmae_ops;
> hpbdev->shdma_dev.desc_size = sizeof(struct hpb_desc);
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-01-21 11:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 4:42 [PATCH] dmaengine: rcar-hpbdma: tidyup residue_granularity Kuninori Morimoto
2015-01-21 11:07 ` Laurent Pinchart [this message]
2015-01-22 0:24 ` Kuninori Morimoto
2015-01-22 0:28 ` Laurent Pinchart
2015-01-26 6:38 ` Vinod Koul
2015-01-26 6:52 ` Kuninori Morimoto
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=33068117.HPgfh8e0Et@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.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