public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Pharaoh ." <pharaoh137@gmail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Query regarding omap_set_dma_transfer_params()
Date: Tue, 12 Jun 2007 06:43:00 -0700	[thread overview]
Message-ID: <20070612134259.GH28834@atomide.com> (raw)
In-Reply-To: <61445c750706110756k39f09613ge0e7eedd0befe51f@mail.gmail.com>

* Pharaoh . <pharaoh137@gmail.com> [070611 08:02]:
> Hi,
>
> I am trying to configure the DMA channels in my ALSA driver.  Functions 
> like
>
>
> void omap_set_dma_dest_params(int lch, int dest_port, int dest_amode,
>                              unsigned long dest_start,
>                              int dst_ei, int dst_fi)
> and omap_set_dma_src_params() are used for configuration.
>
> What the last two fields i.e dst_ie and dst_fi mean here?

See dma.h, ei = element index and fi = frame index. Some of these are
documented in the 2912 TRM pdf.

> I think this has to do something with interrupts etc but not sure about it.
> Also
> I couldn't see those fields being populated anywhere in source (they are 0
> everywhere).
> I am referring 2.6.19-omap1.
>
> Also, I think that these are unnecessarily exported, since the function
> omap_set_dma_params()
> is already exported and it calls the above mentioned functions.  And
> normally the sequence of
> configuring the DMA channel is like
>
> -set src params
> -set dest params
> -set transfer params

Well you can do it both ways, sometimes you just want to update the
source or destination between transfers.

Tony

      parent reply	other threads:[~2007-06-12 13:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 14:56 Query regarding omap_set_dma_transfer_params() Pharaoh .
2007-06-11 15:08 ` Pharaoh .
2007-06-12 13:43 ` Tony Lindgren [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070612134259.GH28834@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=pharaoh137@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox