On Fri, Apr 26, 2013 at 10:41:23AM +0100, Russell King - ARM Linux wrote:
> On Fri, Apr 26, 2013 at 01:46:46PM +0530, Vinod Koul wrote:
> > On Fri, Apr 26, 2013 at 10:28:39AM +0200, Linus Walleij wrote:
> > > On Thu, Apr 25, 2013 at 4:11 PM, Arnd Bergmann wrote:
> > >
> > > > The dma engine drive
On Fri, Apr 26, 2013 at 11:39:20AM +0200, Arnd Bergmann wrote:
> On Friday 26 April 2013 13:46:46 Vinod Koul wrote:
> >
> > The mapping & unmapping of dma buffer (memcpy and memory buffer in this
> > txn) is
> > required to be performed by the client driver. The dmanegine or dmaengine
> > driver
On Fri, Apr 26, 2013 at 01:46:46PM +0530, Vinod Koul wrote:
> On Fri, Apr 26, 2013 at 10:28:39AM +0200, Linus Walleij wrote:
> > On Thu, Apr 25, 2013 at 4:11 PM, Arnd Bergmann wrote:
> >
> > > The dma engine driver must know the address in its dma space, while the
> > > slave driver has it availa
On Friday 26 April 2013 13:46:46 Vinod Koul wrote:
>
> The mapping & unmapping of dma buffer (memcpy and memory buffer in this txn)
> is
> required to be performed by the client driver. The dmanegine or dmaengine
> driver
> will not do that for you...
I've been wondering about this part: since
On Friday 26 April 2013 10:28:39 Linus Walleij wrote:
>
> However this rings a bell that there may be a possible relation to
> DMA-API, since that API syncs memory buffers to the DMA
> address space if there is some MMU inbetween the DMA and the
> (ordinary, non-device) memory.
>
> So if we think
On Fri, Apr 26, 2013 at 10:16 AM, Vinod Koul wrote:
>> OK I could cook a patch for that, but I think I need some input from
>> Vinod and/or Russell on this.
> the dma_slave_config is physical address that should be passed directly to the
> controller. Obviosuly it should phys_addr_t :)
OK! Sent
On Fri, Apr 26, 2013 at 10:28:39AM +0200, Linus Walleij wrote:
> On Thu, Apr 25, 2013 at 4:11 PM, Arnd Bergmann wrote:
>
> > The dma engine driver must know the address in its dma space, while the
> > slave driver has it available in physical space. These two are often the
> > same, but there is
On Thu, Apr 25, 2013 at 4:11 PM, Arnd Bergmann wrote:
> The dma engine driver must know the address in its dma space, while the
> slave driver has it available in physical space. These two are often the
> same, but there is no generic way to convert between the two, especially
> if the dma engine
On Thursday 25 April 2013, Lee Jones wrote:
> > > @@ -232,6 +236,7 @@ struct cryp_dma {
> > > */
> > > struct cryp_device_data {
> > > struct cryp_register __iomem *base;
> > > + phys_addr_t phybase;
> >
> > Use dma_addr_t. Maybe "phybase" is misleading,
> > "dmabase" is probably
On Thu, Apr 25, 2013 at 3:44 PM, Lee Jones wrote:
> On Thu, 25 Apr 2013, Linus Walleij wrote:
>> On Thu, Apr 18, 2013 at 12:27 PM, Lee Jones wrote:
>>
>> > The DMA controller currently takes configuration information from
>> > information passed though dma_channel_request(), but it shouldn't.
>>
On Thu, 25 Apr 2013, Linus Walleij wrote:
> On Thu, Apr 18, 2013 at 12:27 PM, Lee Jones wrote:
>
> > The DMA controller currently takes configuration information from
> > information passed though dma_channel_request(), but it shouldn't.
> > Using the API, the DMA channel should only be configur
On Thu, Apr 18, 2013 at 12:27 PM, Lee Jones wrote:
> The DMA controller currently takes configuration information from
> information passed though dma_channel_request(), but it shouldn't.
> Using the API, the DMA channel should only be configured during
> a dma_slave_config() call.
>
> Cc: Herber
The DMA controller currently takes configuration information from
information passed though dma_channel_request(), but it shouldn't.
Using the API, the DMA channel should only be configured during
a dma_slave_config() call.
Cc: Herbert Xu
Cc: David S. Miller
Cc: Andreas Westin
Cc: linux-crypto@
13 matches
Mail list logo
