From: kishore kadiyala <kishorek.kadiyala@gmail.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "S, Venkatraman" <svenkatr@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-arm-kernel@lists.arm.linux.org.uk"
<linux-arm-kernel@lists.arm.linux.org.uk>,
"Chikkature Rajashekar, Madhusudhan" <madhu.cr@ti.com>,
Adrian Hunter <adrian.hunter@nokia.com>,
"Kadiyala, Kishore" <kishore.kadiyala@ti.com>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH v8 2/2] omap hsmmc: adaptation of sdma descriptor autoloading feature
Date: Thu, 6 May 2010 14:32:22 +0530 [thread overview]
Message-ID: <v2n7f9d1ffb1005060202r91efbe3habb936f75227ffa6@mail.gmail.com> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02C5387398@dbde02.ent.ti.com>
<<snip>>
>> I am not clear about the method. The board files export the
>> omap_mmc_platform_data.
>> Does it imply that all board files have to change and export
>> the capability so that it can be queried ?
> No. You don't have to modify the board files. This would need
> change in devices.c which common for all omap boards.
>
> I don't have a strong opinion on this point but just put forth an
> alternate way to avoid such SOC specific check in drivers.
> You can take call on this
Agree. How about adding a flag in hsmmc.h & omap_mmc_platform_data,
that would take care of SDMA & SDMA_DLAOD in the driver instead going
with SOC check .
next prev parent reply other threads:[~2010-05-06 9:02 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 [this message]
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
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=v2n7f9d1ffb1005060202r91efbe3habb936f75227ffa6@mail.gmail.com \
--to=kishorek.kadiyala@gmail.com \
--cc=adrian.hunter@nokia.com \
--cc=kishore.kadiyala@ti.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=madhu.cr@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=svenkatr@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).