On Mon, Jan 28, 2013 at 10:06:03AM +, Vinod Koul wrote:
> On Mon, Jan 21, 2013 at 01:19:23PM -0500, Matt Porter wrote:
> > > b) Sg segment length and numbers: Well these are capabilities, so it tells
> > > you what is the maximum I can do. IMO it doesn't make sense to tie it
> > > down to
> >
On Mon, Jan 28, 2013 at 10:06:03AM +, Vinod Koul wrote:
On Mon, Jan 21, 2013 at 01:19:23PM -0500, Matt Porter wrote:
b) Sg segment length and numbers: Well these are capabilities, so it tells
you what is the maximum I can do. IMO it doesn't make sense to tie it
down to
burst,
On Mon, Jan 21, 2013 at 01:19:23PM -0500, Matt Porter wrote:
> > b) Sg segment length and numbers: Well these are capabilities, so it tells
> > you what is the maximum I can do. IMO it doesn't make sense to tie it down
> > to
> > burst, width etc. For that configuration you are checking maximum.
On Mon, Jan 21, 2013 at 01:19:23PM -0500, Matt Porter wrote:
b) Sg segment length and numbers: Well these are capabilities, so it tells
you what is the maximum I can do. IMO it doesn't make sense to tie it down
to
burst, width etc. For that configuration you are checking maximum. What
On Mon, Jan 21, 2013 at 03:15:23AM +, Vinod Koul wrote:
> On Sun, Jan 20, 2013 at 11:37:35AM -0500, Matt Porter wrote:
> > On Sun, Jan 20, 2013 at 12:37:34PM +, Vinod Koul wrote:
> > > On Thu, Jan 10, 2013 at 02:07:03PM -0500, Matt Porter wrote:
> > > > The call is implemented as follows:
On Mon, Jan 21, 2013 at 03:15:23AM +, Vinod Koul wrote:
On Sun, Jan 20, 2013 at 11:37:35AM -0500, Matt Porter wrote:
On Sun, Jan 20, 2013 at 12:37:34PM +, Vinod Koul wrote:
On Thu, Jan 10, 2013 at 02:07:03PM -0500, Matt Porter wrote:
The call is implemented as follows:
On Sun, Jan 20, 2013 at 11:37:35AM -0500, Matt Porter wrote:
> On Sun, Jan 20, 2013 at 12:37:34PM +, Vinod Koul wrote:
> > On Thu, Jan 10, 2013 at 02:07:03PM -0500, Matt Porter wrote:
> > > The call is implemented as follows:
> > >
> > > struct dmaengine_chan_caps
> > >
On Sun, Jan 20, 2013 at 12:37:34PM +, Vinod Koul wrote:
> On Thu, Jan 10, 2013 at 02:07:03PM -0500, Matt Porter wrote:
> > The call is implemented as follows:
> >
> > struct dmaengine_chan_caps
> > *dma_get_channel_caps(struct dma_chan *chan,
> > enum
On Thu, Jan 10, 2013 at 02:07:03PM -0500, Matt Porter wrote:
> The call is implemented as follows:
>
> struct dmaengine_chan_caps
> *dma_get_channel_caps(struct dma_chan *chan,
> enum dma_transfer_direction dir);
>
> The dma transfer direction parameter
On Thu, Jan 10, 2013 at 02:07:03PM -0500, Matt Porter wrote:
The call is implemented as follows:
struct dmaengine_chan_caps
*dma_get_channel_caps(struct dma_chan *chan,
enum dma_transfer_direction dir);
The dma transfer direction parameter may
On Sun, Jan 20, 2013 at 12:37:34PM +, Vinod Koul wrote:
On Thu, Jan 10, 2013 at 02:07:03PM -0500, Matt Porter wrote:
The call is implemented as follows:
struct dmaengine_chan_caps
*dma_get_channel_caps(struct dma_chan *chan,
enum
On Sun, Jan 20, 2013 at 11:37:35AM -0500, Matt Porter wrote:
On Sun, Jan 20, 2013 at 12:37:34PM +, Vinod Koul wrote:
On Thu, Jan 10, 2013 at 02:07:03PM -0500, Matt Porter wrote:
The call is implemented as follows:
struct dmaengine_chan_caps
*dma_get_channel_caps(struct
Changes since v1:
- Use the existing dma_transaction_type enums instead of
adding the mostly duplicated dmaengine_apis enums
This series adds a new dmaengine api, dma_get_channels_caps(), which
may be used by a driver to get channel-specific capabilities. This is
based on a
Changes since v1:
- Use the existing dma_transaction_type enums instead of
adding the mostly duplicated dmaengine_apis enums
This series adds a new dmaengine api, dma_get_channels_caps(), which
may be used by a driver to get channel-specific capabilities. This is
based on a
14 matches
Mail list logo
