From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] i2c: add DMA support for freescale i2c driver
Date: Thu, 3 Apr 2014 15:37:03 +0800 [thread overview]
Message-ID: <20140403073701.GL2801@dragon> (raw)
In-Reply-To: <201403260826.28114.marex@denx.de>
On Wed, Mar 26, 2014 at 08:26:27AM +0100, Marek Vasut wrote:
> > > I think we disconnected here, sorry. Why can you not use (i2c_imx->dma !=
> > > NULL) instead of (i2c_imx->use_dma == true) please ?
> >
> > But there are two judge conditions. But only the "i2c_imx->dma", but also
> > whether "i2c_imx_dma_request" success.
> >
> > "i2c_imx->use_dma == true" be equivalent to "i2c_imx->dma != NULL &&
> > !i2c_imx_dma_request()"
>
> + /* Init DMA config if support*/
> + i2c_imx->dma = devm_kzalloc(&pdev->dev, sizeof(struct imx_i2c_dma),
> + GFP_KERNEL);
> + if (!i2c_imx->dma) {
> + dev_info(&pdev->dev,
> + "can't allocate dma struct faild use dma.\n");
> + i2c_imx->use_dma = false;
> + } else if (i2c_imx_dma_request(i2c_imx, (dma_addr_t)phy_addr)) {
> + dev_info(&pdev->dev,
> + "can't request dma chan, faild use dma.\n");
> + i2c_imx->use_dma = false;
> + } else {
> + i2c_imx->use_dma = true;
> + }
>
> OK, looking at this one more time, why don't you wrap the allocation of i2c_imx-
> >dma into i2c_imx_dma_request() ? Even better, you can allocate *dma as a local
> variable in i2c_imx_dma_request() and then assign it into i2c_imx->dma only at
> the end of the i2c_imx_dma_request() function , at the point where you are sure
> nothing failed. Then you can check i2c_imx->dma != NULL throughout the code to
> check if the DMA is available, no ?
>
> Shawn, Wolfram, am I talking nonsense or am I just not connecting ?
I'm with you, Marek.
Shawn
next prev parent reply other threads:[~2014-04-03 7:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 1:47 [PATCH v3 0/2] i2c: add DMA support for freescale i2c driver Yuan Yao
2014-03-13 1:47 ` [PATCH v3 1/2] " Yuan Yao
2014-03-23 3:49 ` Marek Vasut
2014-03-26 3:08 ` Yao Yuan
2014-03-26 3:42 ` Marek Vasut
2014-03-26 5:56 ` Yao Yuan
2014-03-26 6:26 ` Marek Vasut
2014-03-26 7:08 ` Yao Yuan
2014-03-26 7:26 ` Marek Vasut
2014-04-03 7:37 ` Shawn Guo [this message]
2014-03-13 1:47 ` [PATCH v3 2/2] 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=20140403073701.GL2801@dragon \
--to=shawn.guo@linaro.org \
--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).