linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mika.westerberg@iki.fi (Mika Westerberg)
To: linux-arm-kernel@lists.infradead.org
Subject: FW: [linux-cirrus] Fwd: Re: More about SD-Card problems
Date: Tue, 1 Feb 2011 10:41:59 +0200	[thread overview]
Message-ID: <20110201084158.GA2463@acer> (raw)
In-Reply-To: <4D471F71.4010806@bluewatersys.com>

On Tue, Feb 01, 2011 at 09:45:37AM +1300, Ryan Mallon wrote:
> On 02/01/2011 05:45 AM, H Hartley Sweeten wrote:
> > *From:* linux-cirrus-bounce at freelists.org
> > [mailto:linux-cirrus-bounce at freelists.org] *On Behalf Of *Martin Guy
> > *Sent:* Sunday, January 30, 2011 5:40 PM
> > *To:* sim1 at googlegroups.com; linux-cirrus at freelists.org
> > *Subject:* [linux-cirrus] Fwd: Re: More about SD-Card problems
> 
> The Cirrus mailing lists are effectively dead now. Can we please keep
> EP93xx related discussions on the Linux ARM kernel list (Cc'ed).

I'm confused - how did a private email to Martin end up in some Cirrus related
mailing list?

> > Da: "Mika Westerberg" <mika.westerberg@iki.fi
[...]
> > 
> > The M2M DMA patches are attached. Note that it is still in "hack" phase so
> > error handling etc. are not finalized at all. M2M DMA currently only
> > supports
> > SPI but I'm going to add that memory-to-memory support and possibly IDE,
> > let's
> > see. It currently doesn't use double buffering but that is going to be
> > added at
> > some point.
> > 
> > I've been developing on .38-rc2 kernel but since these patches touch
> > only ep93xx
> > stuff I believe that they should apply pretty easily to .36.
> 
> It would be good to get these patches applied to mainline. Some comments
> below. I also think we should look at integrating the EP93xx DMA into
> the existing dmaengine framework if applicable. If not, is it at least
> possible to reuse/combine some parts of the existing EP93xx M2P DMA code?

Well this patch set wasn't meant for public review. It's just a hack I'm working
on which was going to evolve into something which could be considered into
mainline.

I totally agree with you that we should try to use an existing framework. These
are now in a separate source files and have different API but I had a plan to
merge them later if they are similar enough. The patches which are attached are
not there yet (not even close).

It is certainly possible to reuse the existing EP93XX M2P DMA code. Current set
just implements everything on it's own because it was easier to me to get the
thing working with the SPI driver.

Anyway thanks for the review, I'll make sure that the version I'm going to send
to upstream incorporates your suggestions. And I'm hoping to either merge M2M
code into M2P code or look how it could be implemented with dmaengine.

Sorry for the noise.

Regards,
MW

      parent reply	other threads:[~2011-02-01  8:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0D753D10438DA54287A00B027084269764CEE3A4FE@AUSP01VMBX24.collaborationhost.net>
2011-01-31 20:45 ` FW: [linux-cirrus] Fwd: Re: More about SD-Card problems Ryan Mallon
     [not found]   ` <AANLkTik3HN3w5XadSFQ8UtDfYoc2CeFQfSYuKHLfGSvL@mail.gmail.com>
2011-02-01  2:10     ` Linux Cirrus List [was Re: FW: [linux-cirrus] Fwd: Re: More about SD-Card problems] Ryan Mallon
2011-02-01  8:41   ` Mika Westerberg [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=20110201084158.GA2463@acer \
    --to=mika.westerberg@iki.fi \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).