From: Hein Tibosch <hein_tibosch@yahoo.es>
To: Hans-Christian Egtvedt <egtvedt@samfundet.no>
Cc: viresh kumar <viresh.kumar@linaro.org>,
spear-devel <spear-devel@list.st.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"ludovic.desroches" <ludovic.desroches@atmel.com>,
Havard Skinnemoen <havard@skinnemoen.net>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd.bergmann@linaro.org>
Subject: Re: [PATCH 1/2] dw_dmac: make driver endianness configurable
Date: Mon, 27 Aug 2012 16:47:40 +0800 [thread overview]
Message-ID: <503B342C.9060300@yahoo.es> (raw)
In-Reply-To: <20120827070323.GC28721@samfundet.no>
On 8/27/2012 3:03 PM, Hans-Christian Egtvedt wrote:
> I think the English in kconfig could use some brushing up.
>
>> +config DW_DMAC_BE
>
>
> This name isn't that long, so we could skip the abbreviation of big endian;
> DW_DMAC_BIG_ENDIAN_IO or something similar?
>
>> + bool "Synopsys DesignWare AHB DMA needs big endian access"
>>
> bool "Use big endian I/O register access"
Brushing up the config items:
+config DW_DMAC_BIG_ENDIAN_IO
+ bool "Use big endian I/O register access"
+ default y if AVR32
+ depends on DW_DMAC
+ help
+ Say yes here to use big endian I/O access when reading and writing
+ to the DMA controller registers. This is needed on some platforms,
+ like the Atmel AVR32 architecture.
+
+ If unsure, use the default setting.
And as I'd like to define the maximum memory transfer width in the same
Kconfig:
+config DW_DMAC_MEM_64_BIT
+ bool "Allow 64-bit memory transfers"
+ default y if !AVR32
+ depends on DW_DMAC
+ help
+ Say yes if the DMA controller may do 64-bit memory transfers
+ For AVR32, say no because only up to 32-bit transfers are
+ defined
Would this be better?
Thanks, Hein
next prev parent reply other threads:[~2012-08-27 9:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-26 20:53 [PATCH 1/2] dw_dmac: make driver endianness configurable Hein Tibosch
2012-08-27 7:03 ` Hans-Christian Egtvedt
2012-08-27 8:47 ` Hein Tibosch [this message]
2012-08-27 11:14 ` Hans-Christian Egtvedt
2012-08-27 14:58 ` Hein Tibosch
2012-08-28 3:23 ` Viresh Kumar
2012-08-28 6:55 ` Hein Tibosch
2012-08-28 7:05 ` Viresh Kumar
2012-08-28 7:39 ` Felipe Balbi
2012-09-03 7:50 ` Andy Shevchenko
2012-09-03 14:16 ` Felipe Balbi
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=503B342C.9060300@yahoo.es \
--to=hein_tibosch@yahoo.es \
--cc=akpm@linux-foundation.org \
--cc=arnd.bergmann@linaro.org \
--cc=egtvedt@samfundet.no \
--cc=havard@skinnemoen.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
--cc=spear-devel@list.st.com \
--cc=viresh.kumar@linaro.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