Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1355767
| From | Boris Brezillon <boris.brezillon@free-electrons.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users |
| Date | 2016-03-11 10:50 +0100 |
| Message-ID | <rbrRM-489-5@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <ra4Xf-4ss-5@gated-at.bofh.it> <raa6C-7JQ-5@gated-at.bofh.it> <rag2m-38j-21@gated-at.bofh.it> <raJnI-6qG-33@gated-at.bofh.it> <rboKd-1W9-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, 11 Mar 2016 11:54:52 +0530 Vinod Koul <vinod.koul@intel.com> wrote: > On Wed, Mar 09, 2016 at 11:14:34AM +0100, Boris Brezillon wrote: > > > > > > > + * struct sun4i_dma_chan_config - DMA channel config > > > > > > > + * > > > > > > > + * @para: contains information about block size and time before checking > > > > > > > + * DRQ line. This is device specific and only applicable to dedicated > > > > > > > + * DMA channels > > > > > > > > > > > > What information, can you elobrate.. And why can't you use existing > > > > > > dma_slave_config for this? > > > > > > > > > > Block size is related to the device FIFO size. I guess it allows the > > > > > DMA channel to launch a transfer of X bytes without having to check the > > > > > DRQ line (the line telling the DMA engine it can transfer more data > > > > > to/from the device). The wait cycles information is apparently related > > > > > to the number of clks the engine should wait before polling/checking > > > > > the DRQ line status between each block transfer. I'm not sure what it > > > > > saves to put WAIT_CYCLES() to something != 1, but in their BSP, > > > > > Allwinner tweak that depending on the device. > > > > > > we already have block size aka src/dst_maxburst, why not use that one. > > > > Okay, but then remains the question "how should we choose the real burst > > size?". The block size described in Allwinner datasheet is not the > > number of words you will transmit without being preempted by other > > master -> slave requests, it's the number of bytes that can be > > transmitted without checking the DRQ line. > > IOW, block_size = burst_size * X > > Thats fine, API expects words for this and also a width value. Client shoudl > pass both and for programming you should use bytes converted from words and > width. > Not sure I get what you mean. Are you suggesting to add new fields to the dma_slave_config struct to describe this block concept, or should we pass it through ->xxx_burstsize, and try to guess the real burstsize? In the latter case, you still haven't answered my question: how should we choose the burstsize? -- Boris Brezillon, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Boris Brezillon <boris.brezillon@free-electrons.com> - 2016-03-07 11:30 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Vinod Koul <vinod.koul@intel.com> - 2016-03-07 16:00 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Boris Brezillon <boris.brezillon@free-electrons.com> - 2016-03-07 16:10 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Maxime Ripard <maxime.ripard@free-electrons.com> - 2016-03-07 21:40 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Vinod Koul <vinod.koul@intel.com> - 2016-03-08 04:00 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Vinod Koul <vinod.koul@intel.com> - 2016-03-08 04:00 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Maxime Ripard <maxime.ripard@free-electrons.com> - 2016-03-08 09:00 +0100
Re: [linux-sunxi] Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Hans de Goede <hdegoede@redhat.com> - 2016-03-08 09:50 +0100
Re: [linux-sunxi] Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Vinod Koul <vinod.koul@intel.com> - 2016-03-08 11:10 +0100
Re: [linux-sunxi] Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Maxime Ripard <maxime.ripard@free-electrons.com> - 2016-03-09 12:20 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Boris Brezillon <boris.brezillon@free-electrons.com> - 2016-03-08 09:50 +0100
Re: [linux-sunxi] Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Priit Laes <plaes@plaes.org> - 2016-03-08 10:20 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Vinod Koul <vinod.koul@intel.com> - 2016-03-08 11:10 +0100
Re: [linux-sunxi] Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users LABBE Corentin <clabbe.montjoie@gmail.com> - 2016-03-09 11:10 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Vinod Koul <vinod.koul@intel.com> - 2016-03-08 11:00 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Boris Brezillon <boris.brezillon@free-electrons.com> - 2016-03-09 11:20 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Vinod Koul <vinod.koul@intel.com> - 2016-03-11 07:30 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Boris Brezillon <boris.brezillon@free-electrons.com> - 2016-03-11 10:50 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Vinod Koul <vinod.koul@intel.com> - 2016-03-11 11:10 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Boris Brezillon <boris.brezillon@free-electrons.com> - 2016-03-11 11:30 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Vinod Koul <vinod.koul@intel.com> - 2016-03-11 12:20 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Boris Brezillon <boris.brezillon@free-electrons.com> - 2016-03-09 12:30 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Vinod Koul <vinod.koul@intel.com> - 2016-03-11 07:30 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Boris Brezillon <boris.brezillon@free-electrons.com> - 2016-03-11 10:50 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Vinod Koul <vinod.koul@intel.com> - 2016-03-11 11:10 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Maxime Ripard <maxime.ripard@free-electrons.com> - 2016-03-11 12:00 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Vinod Koul <vinod.koul@intel.com> - 2016-03-11 12:20 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Maxime Ripard <maxime.ripard@free-electrons.com> - 2016-03-14 12:50 +0100
Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Vinod Koul <vinod.koul@intel.com> - 2016-03-16 04:20 +0100
Re: [linux-sunxi] [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Priit Laes <plaes@plaes.org> - 2016-03-07 16:40 +0100
Re: [linux-sunxi] [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Boris Brezillon <boris.brezillon@free-electrons.com> - 2016-03-07 17:00 +0100
Re: [linux-sunxi] [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users Emilio López <emilio@elopez.com.ar> - 2016-03-07 18:20 +0100
csiph-web