From: mpa@pengutronix.de (Markus Pargmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] dma: imx-dma: Add oftree support
Date: Mon, 25 Feb 2013 17:53:24 +0100 [thread overview]
Message-ID: <20130225165324.GC32025@pengutronix.de> (raw)
In-Reply-To: <201302251624.52014.arnd@arndb.de>
On Mon, Feb 25, 2013 at 04:24:51PM +0000, Arnd Bergmann wrote:
> On Monday 25 February 2013, Markus Pargmann wrote:
> > Adding devicetree support for imx-dma driver. Use driver name for
> > function 'imx_dma_is_general_purpose' because the devicename for
> > devicetree initialized devices is different.
> >
> > Changes in V3:
> > - Create a imxdma translate function to pass the device object into the
> > filter function.
> >
> > Changes in V2:
> > - Change the driver to use generic DMA DT bindings.
> > - Add a imx-dma filter function that sets the dma request line in
> > private data.
> >
> > Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
> > Cc: Arnd Bergmann <arnd@arndb.de>
>
> Looks correct now,
>
> Reviewed-by: Arnd Bergmann <arnd@arndb.de>
>
> I have one idea for an optimization though:
>
> > +static bool imxdma_filter_fn(struct dma_chan *chan, void *param)
> > +{
> > + struct imxdma_filter_data *fdata = param;
> > + struct imx_dma_data *data;
> > +
> > + if (chan->device->dev != fdata->imxdma->dev)
> > + return false;
> > +
> > + data = kzalloc(sizeof(*data), GFP_KERNEL);
> > +
> > + if (!data)
> > + return false;
> > +
> > + data->dma_request = fdata->request;
> > + data->alloc_ctl_filter = true;
> > + chan->private = data;
> > +
> > + return true;
> > +}
>
> There is already a "dma_request" member in "struct imxdma_channel", so
> you could use that instead of allocating the imx_dma_data here.
>
> Then you don't need to keep track of freeing that memory again, but
> you might have to change a few other functions that look at data->dma_request
> rather than chan->dma_request at the moment and change them to
> use the latter instead. You can copy data->dma_request over in the
> alloc_chan_resources functions for the legacy case.
Thanks, that is much better than the current use of kzalloc. I updated it for v4.
Markus
>
> Arnd
--
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:[~2013-02-25 16:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 14:37 [PATCH] dma: imx-dma: Add oftree support Markus Pargmann
2013-02-22 14:46 ` Arnd Bergmann
2013-02-23 16:57 ` Markus Pargmann
2013-02-23 16:59 ` [PATCH V2] " Markus Pargmann
2013-02-23 22:16 ` Arnd Bergmann
2013-02-24 12:27 ` Markus Pargmann
2013-02-25 14:31 ` Arnd Bergmann
2013-02-25 16:04 ` [PATCH v3 1/2] " Markus Pargmann
2013-02-25 16:04 ` [PATCH v3 2/2] DMA: imx-dma: imxdma->dev used uninitialized Markus Pargmann
2013-02-25 16:24 ` [PATCH v3 1/2] dma: imx-dma: Add oftree support Arnd Bergmann
2013-02-25 16:53 ` Markus Pargmann [this message]
2013-02-28 6:30 ` Shawn Guo
2013-03-01 13:56 ` Markus Pargmann
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=20130225165324.GC32025@pengutronix.de \
--to=mpa@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).