linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: at91: Error while registering DMA controller in 3.3-rc
Date: Thu, 01 Mar 2012 11:05:21 +0100	[thread overview]
Message-ID: <4F4F49E1.4020902@atmel.com> (raw)

Arnd, Olof,

We currently have a regression on 3.3-rc kernels about the DMA
controller registration.

http://article.gmane.org/gmane.linux.kernel.mmc/13014

This is due to the DMA driver having seen an update during the 3.3 merge
window  but the AT91 device files not having the corresponding
modifications.

Maybe you remember, those modifications where part of the famous AT91
board/device series that was postponed to 3.4 due to a flood of issues...

So now, I would like to know if it is possible to resolve this problem
by queuing the DMA related patches that we have already in
at91/device-board branch to mainline before 3.3-final?

The patches that I am talking about are:

bdad0b9 ARM: at91/dma: remove platform data from DMA controller
and
2756bf5 ARM: at91/dma: DMA controller registering with DT support

I do think it is pretty silly to try to resolve this issue by not taking
those two little patches and modifying source code to workaround this
issue. If we do this, we will get conflicts and need to rework the
already queued 3.4 material.

Do you want me to prepare a new at91-fixes branch with those two patches
or you can take them yourself?

Thanks for your help, best regards,
-- 
Nicolas Ferre

             reply	other threads:[~2012-03-01 10:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 10:05 Nicolas Ferre [this message]
2012-03-01 11:49 ` at91: Error while registering DMA controller in 3.3-rc Arnd Bergmann
     [not found]   ` <4F4F7254.9060306@atmel.com>
2012-03-01 14:03     ` [GIT PULL] at91: fixes for DMA registration (3.3-rc) Arnd Bergmann
2012-03-01 14:06       ` Nicolas Ferre

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=4F4F49E1.4020902@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --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).