linux-kernel - Re: [PATCH v3] dma: add driver for R-Car HPB-DMAC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.1309142327410.32052@axis700.grange>
Date:	Sat, 14 Sep 2013 23:31:27 +0200 (CEST)
From:	Guennadi Liakhovetski <g.liakhovetski@....de>
To:	Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
cc:	djbw@...com, vinod.koul@...el.com, linux-kernel@...r.kernel.org,
	linux-sh@...r.kernel.org, max.filippov@...entembedded.com
Subject: Re: [PATCH v3] dma: add driver for R-Car HPB-DMAC

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@...entembedded.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@...esas.com>.
> 
> > > Signed-off-by: Max Filippov <max.filippov@...entembedded.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@...entembedded.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/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/