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@vger.kernel.org,
	linux-omap-open-source <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH RFC] OMAP: DMA: Cleanup of DMA Request Lines
Date: Mon, 10 Dec 2007 10:25:08 -0800	[thread overview]
Message-ID: <20071210182507.GE19104@atomide.com> (raw)
In-Reply-To: <010C7BAE6783F34D9AC336EE5A01A08804FE689E@dbde01.ent.ti.com>

* Gadiyar, Anand <gadiyar@ti.com> [071209 20:16]:
> Hi all,
> 
> I'm resending this patch with the #else removed. I'm also sending a few
> other ways in which we could do this.
> 
> Option 1:
> Same patch as the last time without the #else
> 
> This contains lots of #ifdef statements but there are no #elses

Yeah, not good..

> Option 2:
> No #ifdefs.
>
> Using OMAP242X_* for 2420 specific names
> OMAP243X_* for 2430 specific names/names present from 243X onwards
> OMAP24XX_* for names common to all 24XX, 34XX
> OMAP34XX_* for 34XX specific names
> 
> (or something similar could be worked out)

This is better on short term. It needs an associated patch to change
drivers to use new names.

> Option 3:
> 
> Name all possible names OMAP_* (or OMAP2_*) and use a runtime check to return
> the correct request line number.
> 
> I'm sending sample patches for all three options. Let me know what you think.

Hey, this looks like a good solution in the long run. Except, let's just
load the table for each processor that is compiled in to save memory.

You could load the associated processor dma request configuration from
devices_2420.c, devices_2430.c and devices_3430.c.

Regards,

Tony

      reply	other threads:[~2007-12-10 18:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10  4:15 [PATCH RFC] OMAP: DMA: Cleanup of DMA Request Lines Gadiyar, Anand
2007-12-10 18:25 ` Tony Lindgren [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=20071210182507.GE19104@atomide.com \
    --to=tony@atomide.com \
    --cc=gadiyar@ti.com \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=linux-omap@vger.kernel.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