From: "Cousson, Benoit" <b-cousson@ti.com>
To: "G, Manjunath Kondaiah" <manjugk@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Kevin Hilman <khilman@deeprootsystems.com>,
Paul Walmsley <paul@pwsan.com>, Tony Lindgren <tony@atomide.com>,
"Sawant, Anand" <sawant@ti.com>,
"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
"Nayak, Rajendra" <rnayak@ti.com>,
"Basak, Partha" <p-basak2@ti.com>,
"Varadarajan, Charulatha" <charu@ti.com>
Subject: Re: [PATCH 05/11] OMAP4: DMA: HWMOD: update OMAP4 data base
Date: Thu, 29 Jul 2010 14:48:48 +0200 [thread overview]
Message-ID: <4C5178B0.40102@ti.com> (raw)
In-Reply-To: <1280397545-27323-6-git-send-email-manjugk@ti.com>
Some more comments about "dma_" prefix...
On 7/29/2010 11:58 AM, G, Manjunath Kondaiah wrote:
> The OMAP4 hwmod data base is updated with DMA controller attributes.
>
> Signed-off-by: Manjunatha GK<manjugk@ti.com>
> ---
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 19 ++++++++++++++-----
> 1 files changed, 14 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> index 20f5f8c..ee589c5 100644
> --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> @@ -22,6 +22,7 @@
>
> #include<plat/omap_hwmod.h>
> #include<plat/cpu.h>
> +#include<plat/dma.h>
>
> #include "omap_hwmod_common_data.h"
>
> @@ -750,12 +751,19 @@ static struct omap_hwmod_class omap44xx_dma_hwmod_class = {
> .sysc =&omap44xx_dma_sysc,
> };
>
> +/* dma attributes */
> +static struct omap_dma_dev_attr dma_dev_attr = {
> + .dma_dev_attr = DMA_LINKED_LCH | GLOBAL_PRIORITY |
> + IS_CSSA_32 | IS_CDSA_32 | IS_RW_PRIORIY,
> + .dma_lch_count = OMAP_DMA4_LOGICAL_DMA_CH_COUNT,
> +};
> +
> /* dma_system */
> static struct omap_hwmod_irq_info omap44xx_dma_system_irqs[] = {
> - { .name = "0", .irq = 12 + OMAP44XX_IRQ_GIC_START },
> - { .name = "1", .irq = 13 + OMAP44XX_IRQ_GIC_START },
> - { .name = "2", .irq = 14 + OMAP44XX_IRQ_GIC_START },
> - { .name = "3", .irq = 15 + OMAP44XX_IRQ_GIC_START },
> + { .name = "dma_0", .irq = 12 + OMAP44XX_IRQ_GIC_START },
> + { .name = "dma_1", .irq = 13 + OMAP44XX_IRQ_GIC_START },
> + { .name = "dma_2", .irq = 14 + OMAP44XX_IRQ_GIC_START },
> + { .name = "dma_3", .irq = 15 + OMAP44XX_IRQ_GIC_START },
"0", "1", "2", and "3" are maybe not very meaningful name, but what
information the dma_ prefix will bring us?
That name will only be used inside the dma driver, so there is no
namespace confusion. The shorter, the better.
Regards,
Benoit
> };
>
> static struct omap_hwmod_addr_space omap44xx_dma_system_addrs[] = {
> @@ -801,6 +809,7 @@ static struct omap_hwmod omap44xx_dma_system_hwmod = {
> .slaves_cnt = ARRAY_SIZE(omap44xx_dma_system_slaves),
> .masters = omap44xx_dma_system_masters,
> .masters_cnt = ARRAY_SIZE(omap44xx_dma_system_masters),
> + .dev_attr =&dma_dev_attr,
> .omap_chip = OMAP_CHIP_INIT(CHIP_IS_OMAP4430),
> };
>
> @@ -4789,7 +4798,7 @@ static __initdata struct omap_hwmod *omap44xx_hwmods[] = {
> /* counter class */
> &omap44xx_counter_32k_hwmod,
> /* dma class */
> -/* &omap44xx_dma_system_hwmod, */
> + &omap44xx_dma_system_hwmod,
> /* dmic class */
> /* &omap44xx_dmic_hwmod, */
> /* dsp class */
next prev parent reply other threads:[~2010-07-29 12:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 9:58 [PATCH 00/11] OMAP: DMA: HWMOD and DMA as platform driver Manjunatha GK
2010-07-29 9:58 ` [PATCH 01/11] OMAP: DMA: Introduce DMA device attributes Manjunatha GK
2010-07-29 12:35 ` Cousson, Benoit
2010-07-30 3:57 ` G, Manjunath Kondaiah
2010-08-04 10:13 ` Cousson, Benoit
2010-08-04 17:21 ` G, Manjunath Kondaiah
2010-08-04 18:13 ` Gadiyar, Anand
2010-07-29 9:58 ` [PATCH 02/11] OMAP2420: DMA: HWMOD: Add hwmod data structures Manjunatha GK
2010-07-29 9:58 ` [PATCH 03/11] OMAP2430: " Manjunatha GK
2010-07-29 9:58 ` [PATCH 04/11] OMAP3: " Manjunatha GK
2010-08-03 21:56 ` Kevin Hilman
2010-08-04 0:35 ` G, Manjunath Kondaiah
2010-08-04 10:08 ` Cousson, Benoit
2010-08-04 10:15 ` Shilimkar, Santosh
2010-08-04 10:23 ` Cousson, Benoit
2010-08-04 10:27 ` Shilimkar, Santosh
2010-08-04 10:36 ` Cousson, Benoit
2010-08-04 10:38 ` Shilimkar, Santosh
2010-08-04 17:24 ` G, Manjunath Kondaiah
2010-07-29 9:58 ` [PATCH 05/11] OMAP4: DMA: HWMOD: update OMAP4 data base Manjunatha GK
2010-07-29 12:48 ` Cousson, Benoit [this message]
2010-07-29 9:59 ` [PATCH 06/11] OMAP1: DMA: Introduce DMA driver as platform driver Manjunatha GK
2010-07-29 9:59 ` [PATCH 07/11] OMAP2/3/4: DMA: HWMOD: Device registration Manjunatha GK
2010-07-29 9:59 ` [PATCH 08/11] OMAP: DMA: Convert DMA library into DMA platform Driver Manjunatha GK
2010-07-29 9:59 ` [PATCH 09/11] OMAP: DMA: Implement generic errata handling Manjunatha GK
2010-07-29 9:59 ` [PATCH 10/11] OMAP: DMA: Use DMA device attributes Manjunatha GK
2010-07-29 9:59 ` [PATCH 11/11] sDMA: descriptor autoloading feature Manjunatha GK
2010-07-29 10:30 ` G, Manjunath Kondaiah
2010-08-11 7:43 ` [PATCH 00/11] OMAP: DMA: HWMOD and DMA as platform driver G, Manjunath Kondaiah
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=4C5178B0.40102@ti.com \
--to=b-cousson@ti.com \
--cc=charu@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@ti.com \
--cc=p-basak2@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=sawant@ti.com \
--cc=tony@atomide.com \
/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).