All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Mikko Vinni <mmvinni@yahoo.com>
Cc: linux-mmc@vger.kernel.org
Subject: Re: [PATCH resend] sdhci: work around broken dma boundary behaviour
Date: Mon, 14 Mar 2011 18:21:29 +0100	[thread overview]
Message-ID: <20110314172129.GA20654@pengutronix.de> (raw)
In-Reply-To: <727376.43956.qm@web161815.mail.bf1.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]

> > > intmask)
> > >            * boundaries, but as we can't disable the  feature
> > >           * we need to at least restart  the transfer.
> > >           */
> > > -         if (intmask & SDHCI_INT_DMA_END)
> > > -             sdhci_writel(host, sdhci_readl(host,  SDHCI_DMA_ADDRESS),
> > > -                 SDHCI_DMA_ADDRESS);
> > > +        if (intmask  & SDHCI_INT_DMA_END) {
> > > +             u32 dmastart, dmanow;
> > > +             dmastart = sg_dma_address(host->data->sg);
> > 
> > Consecutive transfers  won't work (I know you know ;)).
> 
> I assume you mean a single transfer that exceeds whatever is
> defined in SDHCI_DEFAULT_BOUNDARY_SIZE. As long as
> it is kept at 512K things should be fine, but adding the auxiliary
> variable to facilitate smaller values would make the patch
> more invasive. Being an mmc non-hacker, I would rather leave
> that kind of invasive patches for others :)

If you don't want to invest the effort, this is your decision, which is
fine. Other than that, I'd say you are not missing the required skills
for that change. (/me is just helping out here as well)

Cheers,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-03-14 17:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 20:40 [PATCH resend] sdhci: work around broken dma boundary behaviour Mikko Vinni
2011-03-08 20:12 ` Chris Ball
2011-03-08 22:12   ` Wolfram Sang
2011-03-12 21:43 ` Wolfram Sang
2011-03-14  9:23   ` Mikko Vinni
2011-03-14 10:18     ` Wolfram Sang
2011-03-14 13:00       ` Mikko Vinni
2011-03-14 15:28         ` Wolfram Sang
2011-03-14 15:58           ` Mikko Vinni
2011-03-14 17:21             ` Wolfram Sang [this message]
2011-03-29  8:53               ` [RFC] mmc: sdhci: work around broken dma boundary behavior Mikko Vinni
2011-04-11 21:05                 ` Chris Ball
2011-04-12  4:56                   ` Wolfram Sang
2011-04-12 17:29                 ` Chris Ball
2011-04-13  7:04                   ` Mikko Vinni

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=20110314172129.GA20654@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=linux-mmc@vger.kernel.org \
    --cc=mmvinni@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.