public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 1/4] OMAP: DMA: Cleanup of DMA Request Lines
Date: Wed, 21 Nov 2007 09:06:03 -0800	[thread overview]
Message-ID: <20071121170603.GH8138@atomide.com> (raw)
In-Reply-To: <010C7BAE6783F34D9AC336EE5A01A08804DC0E4B@dbde01.ent.ti.com>

Hi,

* Gadiyar, Anand <gadiyar@ti.com> [071120 21:12]:
> Hi, 
> 
> > -----Original Message-----
> > From: Tony Lindgren [mailto:tony@atomide.com] 
> > Sent: Wednesday, October 31, 2007 6:41 PM
> 
> > > +#ifndef CONFIG_ARCH_OMAP3
> > >  #define OMAP24XX_DMA_CWT		8	/* S_DMA_7 */
> > > +#endif
> > > +
> > >  #define OMAP24XX_DMA_AES_TX		9	/* S_DMA_8 */
> > >  #define OMAP24XX_DMA_AES_RX		10	/* S_DMA_9 */
> > >  #define OMAP24XX_DMA_DES_TX		11	/* S_DMA_10 */
> > >  #define OMAP24XX_DMA_DES_RX		12	/* S_DMA_11 */
> > > +
> > > +#ifdef CONFIG_ARCH_OMAP3
> > > +#define OMAP34XX_DMA_SHA2MD5_RX		13	/* S_DMA_12 */
> > > +#else
> > >  #define OMAP24XX_DMA_SHA1MD5_RX		13	/* S_DMA_12 */
> > > +#endif
> > > +
> > > +#ifdef CONFIG_ARCH_OMAP2420
> > >  #define OMAP24XX_DMA_EXT_DMAREQ2	14	/* S_DMA_13 */
> > >  #define OMAP24XX_DMA_EXT_DMAREQ3	15	/* S_DMA_14 */
> > >  #define OMAP24XX_DMA_EXT_DMAREQ4	16	/* S_DMA_15 */
> > 
> > Let's remove the #ifdefs here, we want to be able to compile 
> > support for
> > 24xx and 34xx into the same kernel eventually. It's OK to 
> > have the same
> > DMA request channel defined in different way for 24xx and 34xx.
> 
> I've just started re-working this patch. Let me check if I have understood
> you correctly. Do you want me to remove only the #ifdefs around the
> OMAP34XX_DMA_SHA2MD5_RX/OMAP24XX_DMA_SHA1MD5_RX?

Yeah.

> If this is the case, then wouldn't we run into trouble when we try to use a
> request line with the same name but a different number - as is the case with
> OMAP24XX_DMA_SHA1MD5_RX (13 on 24XX and 69 on 34XX)

Then we should just define them as OMAP242X_DMA_ and OMAP34XX_DMA.

> Also when you say "we want to be able to compile support for 24xx and 34xx into
> the same kernel...", do you mean there will be a CONFIG_ARCH_OMAP2 as well as a
> CONFIG_ARCH_OMAP3 defined at the same time?

Yeah, that's already working for omap1. With -Wa gcc option we can
mix in assembly for ARMv7.

Regards,

Tony

  reply	other threads:[~2007-11-21 17:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24  7:04 [PATCH 1/4] OMAP: DMA: Cleanup of DMA Request Lines Gadiyar, Anand
2007-10-31 13:11 ` Tony Lindgren
2007-10-31 13:18   ` Woodruff, Richard
2007-10-31 13:26     ` Tony Lindgren
2007-11-21  5:12   ` Gadiyar, Anand
2007-11-21 17:06     ` Tony Lindgren [this message]
2007-11-15  1:55 ` Tony Lindgren
2007-11-15  1:57   ` Tony Lindgren
2007-11-15  4:04     ` Gadiyar, Anand

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=20071121170603.GH8138@atomide.com \
    --to=tony@atomide.com \
    --cc=gadiyar@ti.com \
    --cc=linux-omap-open-source@linux.omap.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