From: Ludovic Desroches <ludovic.desroches@atmel.com>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Vinod Koul <vinod.koul@intel.com>, <dmaengine@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Ludovic Desroches <ludovic.desroches@atmel.com>
Subject: Re: [PATCH RFC 1/2] dmaengine: Introduce scheduled DMA framework
Date: Mon, 23 Mar 2015 10:15:03 +0100 [thread overview]
Message-ID: <20150323091503.GE32259@odux.rfo.atmel.com> (raw)
In-Reply-To: <1426966927-30833-2-git-send-email-maxime.ripard@free-electrons.com>
On Sat, Mar 21, 2015 at 12:42:06PM -0700, Maxime Ripard wrote:
[...]
> +/*
> + * Besoin d'une fonction pour pusher un descriptor vers un pchan
> + *
> + * Flow normal:
> + * - Election d'un pchan (Framework)
> + * - Push d'un descripteur vers le pchan (Driver)
> + * - idle....
> + * - interrupt (driver)
> + * - Transfert terminé, notification vers le framework (driver)
> + * - Nouveau transfert dans la queue?
> + * + Si oui, on est reparti
> + * + Si non, on sort de l'interrupt, le pchan est libéré
> + */
As I am French too, I totally agree to translate comments in French but
I am not sure it will satisfy everyone :)
next prev parent reply other threads:[~2015-03-23 9:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 19:42 [PATCH RFC 0/2] dmaengine: Introduce Scheduled DMA sub-framework Maxime Ripard
2015-03-21 19:42 ` [PATCH RFC 1/2] dmaengine: Introduce scheduled DMA framework Maxime Ripard
2015-03-23 9:15 ` Ludovic Desroches [this message]
2015-03-23 16:55 ` Maxime Ripard
2015-03-23 13:25 ` Ludovic Desroches
2015-03-23 19:07 ` Maxime Ripard
2015-03-23 16:38 ` Vinod Koul
2015-03-23 21:51 ` Maxime Ripard
2015-03-24 16:20 ` Vinod Koul
2015-03-25 0:30 ` Maxime Ripard
2015-03-21 19:42 ` [PATCH RFC 2/2] dmaengine: sun6i: Convert to scheduled DMA Maxime Ripard
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=20150323091503.GE32259@odux.rfo.atmel.com \
--to=ludovic.desroches@atmel.com \
--cc=dmaengine@vger.kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=vinod.koul@intel.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
all inboxes | Powered by JetHome®