From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: djbw@fb.com, vinod.koul@intel.com, linux-kernel@vger.kernel.org,
linux-sh@vger.kernel.org, max.filippov@cogentembedded.com
Subject: Re: [PATCH v3] dma: add driver for R-Car HPB-DMAC
Date: Sat, 14 Sep 2013 23:31:27 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.1309142327410.32052@axis700.grange> (raw)
In-Reply-To: <5234B33A.8040409@cogentembedded.com>
Hi Sergei
On Sat, 14 Sep 2013, Sergei Shtylyov wrote:
> Hello.
>
> On 09/14/2013 10:33 PM, Guennadi Liakhovetski wrote:
>
> > > From: Max Filippov <max.filippov@cogentembedded.com>
>
> > > Add support for HPB-DMAC found in Renesas R-Car SoCs, using 'shdma-base'
> > > DMA
> > > driver framework.
>
> > > Based on the original patch by Phil Edworthy <phil.edworthy@renesas.com>.
>
> > > Signed-off-by: Max Filippov <max.filippov@cogentembedded.com>
> > > [Sergei: removed useless #include, sorted #include's, fixed
> > > HPB_DMA_TCR_MAX,
> > > fixed formats and removed line breaks in the dev_dbg() calls, rephrased
> > > and
> > > added IRQ # to the shdma_request_irq() failure message, added
> > > MODULE_AUTHOR(),
> > > removed '__init'/'__exit' annotations from the probe()/remove() methods,
> > > removed
> > > '__initdata' annotation from 'hpb_dmae_driver', fixed guard macro name in
> > > the
> > > header file, fixed #define ASYNCRSTR_ASRST20, added #define
> > > ASYNCRSTR_ASRST24,
> > > added the necessary runtime PM calls to the probe() and remove() methods,
> > > handled errors returned by dma_async_device_register(), beautified
> > > comments
> > > and #define's.]
> > > Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> > > ---
>
> > [snip]
>
> > > Index: slave-dma/drivers/dma/sh/rcar-hpbdma.c
> > > ===================================================================
> > > --- /dev/null
> > > +++ slave-dma/drivers/dma/sh/rcar-hpbdma.c
> > > @@ -0,0 +1,655 @@
>
> > [snip]
>
> > > +static int hpb_dmae_chan_probe(struct hpb_dmae_device *hpbdev, int id)
> > > +{
> > > + struct shdma_dev *sdev = &hpbdev->shdma_dev;
> > > + struct platform_device *pdev =
> > > + to_platform_device(hpbdev->shdma_dev.dma_dev.dev);
> > > + struct hpb_dmae_chan *new_hpb_chan;
> > > + struct shdma_chan *schan;
> > > +
> > > + /* Alloc channel */
> > > + new_hpb_chan = devm_kzalloc(&pdev->dev,
> > > + sizeof(struct hpb_dmae_chan), GFP_KERNEL);
> > > + if (!new_hpb_chan) {
> > > + dev_err(hpbdev->shdma_dev.dma_dev.dev,
> > > + "No free memory for allocating DMA channels!\n");
> > > + return -ENOMEM;
> > > + }
> > > +
> > > + schan = &new_hpb_chan->shdma_chan;
>
> > A suggestion for an incremental patch - you might want to initialise the
> > max_xfer_len field like
>
> > schan->max_xfer_len = 64 * 1024 * 1024 - 1;
>
> IIRC, the HPB-DMAC's maximum transfer length is 16 MiB, without -1. You
> probably mixed it with LBSC-DMAC which is indeed capable of 64 MiB.
Sorry, no idea what the correct value for HPB DMAC is. This was just an
example.
Thanks
Guennadi
> > because if it isn't initialised your max transfer length will be 4k,
> > which will hurt your performance. I think you should get a better
> > throughput after that
>
> OK, note taken. We'll look into it.
>
> WBR, Sergei
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
prev parent reply other threads:[~2013-09-14 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-24 20:33 Sergei Shtylyov
2013-08-31 0:09 ` Sergei Shtylyov
2013-09-02 10:30 ` Vinod Koul
2013-09-14 18:33 ` Guennadi Liakhovetski
2013-09-14 19:04 ` Sergei Shtylyov
2013-09-14 21:31 ` Guennadi Liakhovetski [this message]
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=Pine.LNX.4.64.1309142327410.32052@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=djbw@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=max.filippov@cogentembedded.com \
--cc=sergei.shtylyov@cogentembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®