From: b.zolnierkie@samsung.com (Bartlomiej Zolnierkiewicz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] DMA: PL330: add device tree property for DMA_MEMCPY capability
Date: Wed, 12 Dec 2012 16:04:18 +0100 [thread overview]
Message-ID: <201212121604.19112.b.zolnierkie@samsung.com> (raw)
In-Reply-To: <CABb+yY0FxsZyBy=scTF31+QMWgHzKf7bNz8vsPowtiMkve7igg@mail.gmail.com>
Hi,
On Wednesday 12 December 2012 08:36:14 Jassi Brar wrote:
> On Fri, Nov 30, 2012 at 4:26 PM, Bartlomiej Zolnierkiewicz
> <b.zolnierkie@samsung.com> wrote:
>
> > Thank you for explaining it. Here is a patch implementing the idea:
> >
> > From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> > Subject: [PATCH] DMA: PL330: add peripherals map to the device tree
> >
> > Add device tree (DT) property ("peri-map") for storing indices
> > of peripherals connected to DMAC and fix DT nodes of client
> > drivers to use 'dma peripheral id' instead of 'dma request id'.
> > Also instead of setting DMA_MEMCPY capability unconditionally in
> > pl330_probe() do it only when "peri-map" DT property is present
> > (idea from Jassi Brar). It fixes the issue on ARM EXYNOS
> > platforms using DT where pdma controller erroneously was used
> > for DMA_MEMCPY operations instead of mdma one (it seems to work
> > correctly but at the cost of worse performance).
> >
> Sorry, we need to change it as per new generic dma DT bindings
> http://git.infradead.org/users/vkoul/slave-dma.git/blob/refs/heads/next:/Documentation/devicetree/bindings/dma/dma.txt
>From looking at the new generic DMA DT bindings code it seems that:
- There is no way to specify different mappings of DMA request signals
for different DMA controllers using the same driver (cause different
of_dma_xlate translation functions would be needed in place of
"peri-map" DT properties).
- There is no way to distinguish DMA capabilities for different DMA
controllers using the same driver (i.e. differentiate between
DMA_MEMCPY and DMA_SLAVE controllers, which is what I really wanted
to fix in the first place; now it seems that in order to add this
relatively trivial change I would have to do a major rewrite of
the whole DT support for PL330, hmmm...).
Could you please describe how I should proceed with implementing
needed functionality in the PL330 driver or/and generic DMA DT layer?
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung Poland R&D Center
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121212/01eb2dcb/attachment-0001.html>
next prev parent reply other threads:[~2012-12-12 15:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 9:59 [PATCH 0/4] DMA: PL330 fixes Bartlomiej Zolnierkiewicz
2012-10-29 9:59 ` [PATCH 1/4] DMA: PL330: fix locking in pl330_free_chan_resources() Bartlomiej Zolnierkiewicz
2012-10-29 21:48 ` Jassi Brar
2012-11-30 10:59 ` Bartlomiej Zolnierkiewicz
2012-11-30 18:07 ` Vinod Koul
2012-12-12 15:08 ` Bartlomiej Zolnierkiewicz
2012-10-29 9:59 ` [PATCH 2/4] ARM: EXYNOS: PL330 MDMA1 fix for revision 0 of Exynos4210 SOC Bartlomiej Zolnierkiewicz
2012-10-29 17:24 ` Kukjin Kim
2012-10-30 8:56 ` Bartlomiej Zolnierkiewicz
2012-11-08 4:49 ` Kukjin Kim
2012-11-08 9:54 ` Bartlomiej Zolnierkiewicz
2012-11-09 10:19 ` Kukjin Kim
2012-11-20 12:23 ` Kukjin Kim
2012-10-29 9:59 ` [PATCH 3/4] ARM: dts: exynos4: add node for PL330 MDMA1 controller Bartlomiej Zolnierkiewicz
2012-11-22 10:57 ` Bartlomiej Zolnierkiewicz
2012-11-23 1:56 ` Kukjin Kim
2012-10-29 9:59 ` [PATCH 4/4] DMA: PL330: add device tree property for DMA_MEMCPY capability Bartlomiej Zolnierkiewicz
2012-10-29 21:45 ` Jassi Brar
2012-10-30 9:21 ` Bartlomiej Zolnierkiewicz
2012-11-09 6:11 ` Jassi Brar
2012-11-30 10:56 ` Bartlomiej Zolnierkiewicz
2012-12-12 7:36 ` Jassi Brar
2012-12-12 15:04 ` Bartlomiej Zolnierkiewicz [this message]
2012-10-29 10:05 ` [PATCH 0/4] DMA: PL330 fixes Tomasz Figa
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=201212121604.19112.b.zolnierkie@samsung.com \
--to=b.zolnierkie@samsung.com \
--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