public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "S, Venkatraman" <svenkatr@ti.com>
Cc: "linux-arm-kernel@lists.arm.linux.org.uk"
	<linux-arm-kernel@lists.arm.linux.org.uk>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Subject: Re: [RFC][PATCH 1/2] OMAP4: sDMA drvier: adding OMAP kConfig option CONFIG_OMAP_DMA_DESCRIPTOR_LOAD
Date: Wed, 12 Aug 2009 16:39:25 -0700	[thread overview]
Message-ID: <87k518ppoy.fsf@deeprootsystems.com> (raw)
In-Reply-To: <0680EC522D0CC943BC586913CF3768C003790C62AD@dbde02.ent.ti.com> (Venkatraman S.'s message of "Thu\, 13 Aug 2009 01\:31\:34 +0530")

"S, Venkatraman" <svenkatr@ti.com> writes:

> The hardware feature is available on OMAP4430 and also expected to be 
> in OMAP3630. Hence the feature flag will control the inclusion of the additional functions.
>
> Addition of omap kconfig option CONFIG_OMAP_DMA_DESCRIPTOR_LOAD.

Short version: (a.k.a caveman version)

- Compile-time option: bad.
- Run-time option: good.

Long version: 

Without looking at the docs, I would hope that the some revision reg
or similar would report whether this feature is available or not.  The
user configuring the kernel should not have to know whether his SoC
has this feature or not.

Kevin

  reply	other threads:[~2009-08-12 23:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12 20:01 [RFC][PATCH 1/2] OMAP4: sDMA drvier: adding OMAP kConfig option CONFIG_OMAP_DMA_DESCRIPTOR_LOAD S, Venkatraman
2009-08-12 23:39 ` Kevin Hilman [this message]
2009-08-18  4:03   ` Venkatraman S

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=87k518ppoy.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@ti.com \
    --cc=svenkatr@ti.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