linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Madhusudhan" <madhu.cr@ti.com>
To: 'Venkatraman S' <svenkatr@ti.com>,
	"'Shilimkar, Santosh'" <santosh.shilimkar@ti.com>
Cc: linux-omap@vger.kernel.org, linux-mmc@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk,
	'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: Wed, 5 May 2010 12:21:09 -0500	[thread overview]
Message-ID: <003901caec77$5a69d8b0$544ff780@am.dhcp.ti.com> (raw)
In-Reply-To: <v2i618f0c911005050919m600f069ex34ba1175315cde5a@mail.gmail.com>

<snip>

> >> +     if (cpu_is_omap44xx() || cpu_is_omap3630()) {
> > Can we avoid above by passing this part of platform data??
> > devices.c
> 
> 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 ?
> 

I don’t see why this capability needs to be passed from the platform data.
As this feature is dependant on omap it is okay to have a cpu check in the
driver as the patch is doing it.

> >> +             host->dma_ctrl_buf = dma_alloc_coherent(NULL,
> >> +                                     DMA_CTRL_BUF_SIZE,
> >> +                                     &host->dma_ctrl_buf_phy,
> >> +                                     0);
> >> +             if (host->dma_ctrl_buf != NULL)
> >> +                     host->dma_caps |= DMA_TYPE_SDMA_DLOAD;
> >> +     }
> >> +
> >>       /* Since we do only SG emulation, we can have as many segs
> >>        * as we want. */
> > Not your patch but above commenting style isn't right
> OK


  reply	other threads:[~2010-05-05 17:21 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 [this message]
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

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='003901caec77$5a69d8b0$544ff780@am.dhcp.ti.com' \
    --to=madhu.cr@ti.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=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).