linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Venkatraman S <svenkatr@ti.com>
To: Nishanth Menon <nm@ti.com>,
	"Chikkature Rajashekar, Madhusudhan" <madhu.cr@ti.com>,
	"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
	kishore kadiyala <kishorek.kadiyala@gmail.com>
Subject: Re: [PATCH v8 2/2] omap hsmmc: adaptation of sdma descriptor autoloading feature
Date: Sat, 15 May 2010 00:13:06 +0530	[thread overview]
Message-ID: <AANLkTin4dO7az90uo3LPJeVnTOvNLPJmKddUAXfdEiCx@mail.gmail.com> (raw)
In-Reply-To: <4BE8056C.6080106@ti.com>

Nishanth Menon <nm@ti.com> wrote:
> On 05/10/2010 07:31 AM, Venkatraman S wrote:
>>
>> Nishanth Menon<menon.nishanth@gmail.com>  wrote:
>
>>>>> Please see [1] for SOC specific feature handling. any reasons we can't
>>>>> handle it by adding a new feature?
>>>>>
>>>>> [1]
>>>>>
>>>>>
>>>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=arch/arm/plat-omap/include/plat/cpu.h#l439
>>>>>
>>>>
>>>> Thanks. I can add a new feature here, but I see that the API is tied
>>>> to OMAP3, whereas the DMA feature is common
>>>> to 3630, OMAP4 and mostly everything after that. I can work on an
>>>> upgrade, but do you see that
>>>> as a dependency and done on the context of this patch ?
>>>> Regards,
>>>> Venkat.
>>>
>>> Yes, I am aware that the current APIs are tied to OMAP3, no reason that
>>> we
>>> cant introduce a OMAP version independent feature.. Yes, IMHO, this is an
>>> SOC specific feature that has no place in a platform data.. lets not
>>> misuse
>>> that.
>>> Regards,
>>> NM
>>

Just a note that I have updated my patch series based on all the
comments except that the 'features' framework has to be created to be
utilised by this patch series. That would be a separate patch, which I
am working on, and will post on monday.
Regards,
Venkat.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-05-14 18:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 17:35 [PATCH v8 2/2] omap hsmmc: adaptation of sdma descriptor autoloading feature Venkatraman S
2010-05-05  9:32 ` Shilimkar, Santosh
2010-05-05 16:19   ` Venkatraman S
2010-05-05 17:21     ` Madhusudhan
2010-05-06  7:49       ` Shilimkar, Santosh
2010-05-06  8:05     ` Shilimkar, Santosh
2010-05-06  8:56       ` Venkatraman S
2010-05-06  9:28         ` Shilimkar, Santosh
2010-05-06  9:02       ` kishore kadiyala
2010-05-06  9:38         ` Shilimkar, Santosh
2010-05-06 16:20           ` Madhusudhan
2010-05-07  4:52             ` Shilimkar, Santosh
2010-05-07 16:59               ` Madhusudhan
2010-05-07 19:26                 ` Nishanth Menon
2010-05-08  0:43                   ` Madhusudhan
2010-05-09 10:51                   ` Venkatraman S
2010-05-09 16:06                     ` Nishanth Menon
2010-05-10 12:31                       ` Venkatraman S
2010-05-10 13:09                         ` Nishanth Menon
2010-05-14 18:43                           ` Venkatraman S [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=AANLkTin4dO7az90uo3LPJeVnTOvNLPJmKddUAXfdEiCx@mail.gmail.com \
    --to=svenkatr@ti.com \
    --cc=kishorek.kadiyala@gmail.com \
    --cc=madhu.cr@ti.com \
    --cc=nm@ti.com \
    --cc=santosh.shilimkar@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;
as well as URLs for NNTP newsgroup(s).