From: shawn.guo@linaro.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/3] serial: fsl_lpuart: add DMA support
Date: Tue, 11 Feb 2014 13:45:50 +0800 [thread overview]
Message-ID: <20140211054548.GC31484@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <c2b2798647d44d3c950ce17f23551555@DM2PR03MB349.namprd03.prod.outlook.com>
On Tue, Feb 11, 2014 at 05:34:49AM +0000, Yao Yuan wrote:
> Here I also have a confusion.
> IRQ is must. But DMA isn't very necessary.
> How to deal with if one board is need DMA but another is not need?
> You mean if DMA is be support once all of them must use dma as first?
That's the point. Why whether using DMA or not is a board decision?
The DMA resource should be defined at SoC level from the beginning
just like IO and interrupt resource. And using DMA or PIO should be a
decision made by device driver not device tree.
Shawn
prev parent reply other threads:[~2014-02-11 5:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 4:09 [PATCH v4 0/3] serial: fsl_lpuart: add DMA support Yuan Yao
2014-01-22 4:09 ` [PATCH v4 1/3] ARM: dts: vf610: lpuart: Add eDMA support Yuan Yao
2014-01-22 4:09 ` [PATCH v4 2/3] serial: fsl_lpuart: add DMA support Yuan Yao
2014-01-24 11:31 ` Mark Rutland
2014-01-22 4:09 ` [PATCH v4 3/3] serial: fsl_lpuart: documented the clock requirement Yuan Yao
2014-01-24 11:26 ` Mark Rutland
2014-01-27 7:50 ` [PATCH v4 0/3] serial: fsl_lpuart: add DMA support Shawn Guo
2014-02-11 1:50 ` Yao Yuan
2014-02-11 2:59 ` Shawn Guo
2014-02-11 5:34 ` Yao Yuan
2014-02-11 5:45 ` Shawn Guo [this message]
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=20140211054548.GC31484@S2101-09.ap.freescale.net \
--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