Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932149Ab3DYM4m (ORCPT ); Thu, 25 Apr 2013 08:56:42 -0400 Received: from mail-oa0-f45.google.com ([209.85.219.45]:36510 "EHLO mail-oa0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756707Ab3DYM4k (ORCPT ); Thu, 25 Apr 2013 08:56:40 -0400 MIME-Version: 1.0 In-Reply-To: <20130425114931.GJ4623@gmail.com> References: <1366279934-30761-1-git-send-email-lee.jones@linaro.org> <1366279934-30761-31-git-send-email-lee.jones@linaro.org> <20130425114931.GJ4623@gmail.com> Date: Thu, 25 Apr 2013 14:56:40 +0200 Message-ID: Subject: Re: [PATCH 30/32] ARM: ux500: Supply MMC DMA configuration via Device Tree From: Linus Walleij To: Lee Jones Cc: "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Arnd Bergmann , Linus WALLEIJ Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1138 Lines: 29 On Thu, Apr 25, 2013 at 1:49 PM, Lee Jones wrote: > On Thu, 25 Apr 2013, Linus Walleij wrote: > >> On Thu, Apr 18, 2013 at 12:12 PM, Lee Jones wrote: >> >> > When requesting a channel, a DMA client needs to pass some pieces of >> > information such as; request channel, device type, channel type and >> > direction etc. Normally we do this in the form of platform data, but >> > when DT is enabled we need to pass it using the driver's bindings >> > instead. >> > >> > Signed-off-by: Lee Jones >> >> This requires that the pending MMCI patch get merged *first* right? > > No, it doesn't. There is no harm in applying this *before*. > > It will just lay dormant until it is. Ah yeah, right. But the patch stripping out the platform data (no 31) will wreak havoc if applied before the MMCI patch right? Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/