Re: [RFC PATCH] dmaengine: sh: Correct src_addr_widths/dst_addr_widths bitmask setting

2017-10-12 Thread Brüns , Stefan
On Donnerstag, 12. Oktober 2017 16:18:12 CEST Vinod Koul wrote: > On Sun, Sep 17, 2017 at 04:45:39PM +0200, Stefan Brüns wrote: > > Obviously, the current value for the burst widths are wrong, and if this > > value is retrieved from some other subsystem using dma_get_slave_caps, > > it will wrongly

Re: [RFC PATCH] dmaengine: sh: Correct src_addr_widths/dst_addr_widths bitmask setting

2017-10-12 Thread Vinod Koul
On Sun, Sep 17, 2017 at 04:45:39PM +0200, Stefan Brüns wrote: > Obviously, the current value for the burst widths are wrong, and if this > value is retrieved from some other subsystem using dma_get_slave_caps, > it will wrongly assume burst width of e.g. 3 bytes are supported. > > Each bit in the

[RFC PATCH] dmaengine: sh: Correct src_addr_widths/dst_addr_widths bitmask setting

2017-09-17 Thread Stefan Brüns
Obviously, the current value for the burst widths are wrong, and if this value is retrieved from some other subsystem using dma_get_slave_caps, it will wrongly assume burst width of e.g. 3 bytes are supported. Each bit in the bitmask corresponds to a supported width, but it uses an encoding of BIT