[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F4F49E1.4020902@atmel.com>
Date: Thu, 01 Mar 2012 11:05:21 +0100
From: Nicolas Ferre <nicolas.ferre@...el.com>
To: Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>
CC: Ludovic Desroches <ludovic.desroches@...el.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>,
Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: at91: Error while registering DMA controller in 3.3-rc
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists