From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] i2c: add DMA support for freescale i2c driver
Date: Mon, 3 Mar 2014 12:14:12 +0100 [thread overview]
Message-ID: <201403031214.12605.marex@denx.de> (raw)
In-Reply-To: <3bbad0af0bc74f04bc386b141dadedb3@BL2PR03MB338.namprd03.prod.outlook.com>
On Monday, March 03, 2014 at 11:23:33 AM, Yao Yuan wrote:
> Hi, Marek
>
> Marek Vasut wrote:
> > On Thursday, February 27, 2014 at 07:05:14 AM, Yuan Yao wrote:
> >
> > [...]
> >
> > > +static void i2c_imx_dma_free(struct imx_i2c_struct *i2c_imx) {
> > > + struct imx_i2c_dma *dma = i2c_imx->dma;
> > > + struct dma_chan *dma_chan;
> > > +
> > > + dma_chan = dma->chan_tx;
> > > + dma->chan_tx = NULL;
> > > + dma->buf_tx = 0;
> > > + dma->len_tx = 0;
> > > + dma_release_channel(dma_chan);
> > > +
> > > + dma_chan = dma->chan_rx;
> > > + dma->chan_tx = NULL;
> > > + dma->buf_rx = 0;
> > > + dma->len_rx = 0;
> > > + dma_release_channel(dma_chan);
> >
> > You must make _DEAD_ _SURE_ this function is not ever called while the
> > DMA is still active. In your case, I have a feeling that's not handled.
>
> Thanks for your attention.
> This few days I look up the code for the realization of
> dma_release_channel(). I found that it will disable the dma request first.
> So it's may safe. And drivers hadn't check whether dma is still active
> before dma_release_channel() as a usually usage. Because it will be
> disabled automatic.
>
> The only problem is that, it will be forced to cancel the transfer which
> was not yet completed. Looking forward to hearing from you.
OK
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-03-03 11:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 6:05 [PATCH 0/3] i2c: add DMA support for freescale i2c driver Yuan Yao
2014-02-27 6:05 ` [PATCH 1/3] " Yuan Yao
2014-02-27 12:55 ` Shawn Guo
2014-02-27 13:21 ` Shawn Guo
2014-02-27 20:39 ` Marek Vasut
2014-02-28 2:13 ` Shawn Guo
2014-02-28 2:23 ` Shawn Guo
2014-02-28 8:57 ` Marek Vasut
2014-02-28 5:19 ` Yao Yuan
2014-02-28 9:04 ` Marek Vasut
2014-02-28 10:59 ` Lothar Waßmann
2014-02-28 12:00 ` Marek Vasut
2014-02-28 11:36 ` Yao Yuan
2014-02-28 12:03 ` Marek Vasut
2014-03-03 10:23 ` Yao Yuan
2014-03-03 11:14 ` Marek Vasut [this message]
2014-02-27 6:05 ` [PATCH 3/3] Documentation:add " Yuan Yao
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=201403031214.12605.marex@denx.de \
--to=marex@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).