From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] dmaengine: mxs-dma: add dma support for i.MX23/28
Date: Wed, 9 Feb 2011 09:34:00 +0100 [thread overview]
Message-ID: <20110209083400.GK9041@pengutronix.de> (raw)
In-Reply-To: <20110208232833.GC6963@S2100-06.ap.freescale.net>
Shawn,
On Wed, Feb 09, 2011 at 07:28:34AM +0800, Shawn Guo wrote:
> > > +
> > > + if (direction == DMA_NONE) {
> > > + ccw = &mxs_chan->ccw[0];
> > > + pio = (u32 *) sgl;
> > > +
> > > + for (j = 0; j < sg_len;)
> > > + ccw->pio_words[j++] = *pio++;
> > > +
> > > + ccw->next = 0;
> > > + ccw->bits.chain = 0;
> > > + ccw->bits.irq = 1;
> > > + ccw->bits.dec_sem = 1;
> > > + ccw->bits.wait4end = flags;
> > > + ccw->bits.halt_on_terminate = 1;
> > > + ccw->bits.terminate_flush = 1;
> > > + ccw->bits.pio_num = sg_len;
> > > + ccw->bits.command = MXS_DMA_NO_XFER;
> >
> > Does this have a valid usecase? I would just return some error code
> > here. pio_num and pio_words are unused in the driver and I don't think
> > a dmaengine driver should have some kind of PIO fallback.
> >
> If you happen to have a look at mxs-mmc patch set, you could find it.
As Russell already pointed out, the (mmc-) driver should handle this.
> > > +
> > > + /*
> > > + * dmaengine clients have to use dma_device.dev_id to filter
> > > + * dma device between apbh and apbx, so need to ensure it is
> > > + * identical to mxs_dma_engine.dev_id.
> > > + */
> > > + if (mxs_dma->dma_device.dev_id != mxs_dma->dev_id) {
> > > + dev_err(&pdev->dev, "dev_id of dma_device %d differs from mxs_dma_engine %d\n",
> > > + mxs_dma->dma_device.dev_id, mxs_dma->dev_id);
> > > + goto err_init;
> > > + }
> >
> > I think it makes more sense to match against device names (apbh vs.
> > apbx) in the client's filter function than to rely on exact numbering.
> >
> I agree, if there is already a member like dev_name in dma_device.
> There is dev_id but no dev_name. Suggestion on how to use device
> name for matching?
Have a look at the implementation of imx_dma_is_general_purpose() and
imx_dma_is_ipu().
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2011-02-09 8:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 2:08 Add dma support for i.MX23/28 Shawn Guo
2011-02-05 2:08 ` [PATCH 1/5] dmaengine: mxs-dma: add " Shawn Guo
2011-02-04 18:17 ` Russell King - ARM Linux
2011-02-08 22:56 ` Shawn Guo
2011-02-08 16:38 ` Russell King - ARM Linux
2011-02-05 15:33 ` Russell King - ARM Linux
2011-02-08 22:59 ` Shawn Guo
2011-02-07 7:37 ` Lothar Waßmann
2011-02-08 23:09 ` Shawn Guo
2011-02-07 8:25 ` Sascha Hauer
2011-02-07 9:09 ` Russell King - ARM Linux
2011-02-08 23:28 ` Shawn Guo
2011-02-09 8:34 ` Sascha Hauer [this message]
2011-02-09 21:42 ` Shawn Guo
2011-02-07 14:13 ` Lothar Waßmann
2011-02-08 23:30 ` Shawn Guo
2011-02-07 14:31 ` Lothar Waßmann
2011-02-08 23:38 ` Shawn Guo
2011-02-08 14:41 ` Lothar Waßmann
2011-02-09 0:17 ` Shawn Guo
2011-02-09 8:06 ` Lothar Waßmann
2011-02-09 20:42 ` Shawn Guo
2011-02-09 13:13 ` Lothar Waßmann
2011-02-14 0:16 ` Shawn Guo
2011-02-09 9:09 ` Sascha Hauer
2011-02-09 21:02 ` Shawn Guo
2011-02-05 2:08 ` [PATCH 2/5] ARM: mxs: add dma channel definitions Shawn Guo
2011-02-05 2:08 ` [PATCH 3/5] ARM: mxs: dynamically allocate dma device for mx23/28 Shawn Guo
2011-02-07 8:09 ` Sascha Hauer
2011-02-09 0:22 ` Shawn Guo
2011-02-05 2:08 ` [PATCH 4/5] ARM: mxs/mx23evk: add dma device Shawn Guo
2011-02-05 2:08 ` [PATCH 5/5] ARM: mxs/mx28evk: " Shawn Guo
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=20110209083400.GK9041@pengutronix.de \
--to=s.hauer@pengutronix.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).