linux-kernel - Re: [PATCH 1/8] ARM i.MX dma: implement wrapper for dma functions

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 10 Aug 2010 14:34:26 +0200
From:	Sascha Hauer <s.hauer@...gutronix.de>
To:	Linus Walleij <linus.ml.walleij@...il.com>
Cc:	linux-arm-kernel@...ts.infradead.org,
	linux kernel <linux-kernel@...r.kernel.org>,
	Dan Williams <dan.j.williams@...el.com>
Subject: Re: [PATCH 1/8] ARM i.MX dma: implement wrapper for dma functions

Hi Linus,

On Tue, Aug 10, 2010 at 12:45:17AM +0200, Linus Walleij wrote:
> 2010/8/9 Sascha Hauer <s.hauer@...gutronix.de>:
> 
> > Currently there is only one i.MX DMA implementation in the tree,
> > the one for i.MX1/21/27. The SDMA support for i.MX25/31/35/51 can
> > be implemented similarly. This wrapper for the DMA is implemented
> > so that drivers do not have to care about the implementation
> > present and don't have to #ifdef DMA support
> >
> > Signed-off-by: Sascha Hauer <s.hauer@...gutronix.de>
> > (...)
> > +struct imx_dma_operations {
> > +       int (*config_channel)(int channel, struct imx_dma_config *cfg);
> > +       int (*setup_single)(int channel, dma_addr_t mem, int dma_length,
> > +               unsigned int dmamode);
> > +       int (*setup_sg)(int channel, struct scatterlist *sg,
> > +                       unsigned int sgcount, unsigned int dma_length,
> > +                       unsigned int dmamode);
> > +       void (*enable)(int channel);
> > +       void (*disable)(int channel);
> > +       int (*request)(enum imx_dma_prio);
> > +       void (*free)(int channel);
> > +       int num_channels;
> > +};
> 
> This is just getting *so* close to the drivers/dma dmaengine API.

I was afraid somewone would say this ;)

> 
> We decided to use the damengine for all our DMA drivers and we
> haven't regretted one bit.
> 
> There has been some noise about too many drivers stacking up
> below arch/arm instead of going to the apropriate subsystem, can't
> you atleast contemplate using the dmaengine and help us improve
> that subsystem?

The last time I looked into dmaengine I failed to see how this API
could help me. Looking at it again it seems that this is the way
to go. I will definitely have a closer look. I can't promise though that
this will be before the next merge window. The SDMA engine on the other
hand is of great value for the i.MX community, so if anyone is willing
to help here, please step forward.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
--
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/