From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: John Crispin <blogic@openwrt.org>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH 1/4] MIPS: lantiq: adds 4dword burst length for dma
Date: Thu, 8 Aug 2013 11:49:42 +0200 [thread overview]
Message-ID: <20130808094942.GA21442@alpha.franken.de> (raw)
In-Reply-To: <1375952846-25812-1-git-send-email-blogic@openwrt.org>
On Thu, Aug 08, 2013 at 11:07:23AM +0200, John Crispin wrote:
> Comparing the upstream code with the Lantiq UGW kernel we see that burst length
> should be set to 4 bytes.
>
> Signed-off-by: John Crispin <blogic@openwrt.org>
> ---
> arch/mips/lantiq/xway/dma.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/mips/lantiq/xway/dma.c b/arch/mips/lantiq/xway/dma.c
> index 08f7ebd..ccf1451 100644
> --- a/arch/mips/lantiq/xway/dma.c
> +++ b/arch/mips/lantiq/xway/dma.c
> @@ -48,6 +48,7 @@
> #define DMA_IRQ_ACK 0x7e /* IRQ status register */
> #define DMA_POLL BIT(31) /* turn on channel polling */
> #define DMA_CLK_DIV4 BIT(6) /* polling clock divider */
> +#define DMA_4W_BURST BIT(2) /* 4 word burst length */
> #define DMA_2W_BURST BIT(1) /* 2 word burst length */
that's wrong, it's not BIT(x), but x itself.
1 means 2 word burst
2 means 4 word burst
3 means 8 word burst
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2013-08-08 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 9:07 [PATCH 1/4] MIPS: lantiq: adds 4dword burst length for dma John Crispin
2013-08-08 9:07 ` [PATCH 2/4] MIPS: lantiq: adds minimal dcdc driver John Crispin
2013-08-08 10:58 ` Sergei Shtylyov
2013-08-08 11:17 ` Florian Fainelli
2013-08-08 11:50 ` Lars-Peter Clausen
2013-08-08 12:04 ` Sergei Shtylyov
2013-08-08 9:07 ` [PATCH 3/4] MIPS: lantiq: falcon: add cpu-feature-override.h John Crispin
2013-08-08 9:07 ` [PATCH 4/4] MIPS: lantiq: falcon: fix asc clock definition John Crispin
2013-08-08 9:49 ` Thomas Bogendoerfer [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=20130808094942.GA21442@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=blogic@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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