Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754597Ab2HaQzr (ORCPT ); Fri, 31 Aug 2012 12:55:47 -0400 Received: from merlin.infradead.org ([205.233.59.134]:48177 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754040Ab2HaQzq (ORCPT ); Fri, 31 Aug 2012 12:55:46 -0400 Message-ID: <1346432577.15463.16.camel@vkoul-mobl4> Subject: Re: [PATCH v3 3/3] spi: spi-davinci: convert to DMA engine API From: Vinod Koul To: Sekhar Nori Cc: vinod.koul@intel.com, Matt Porter , Linux DaVinci Kernel List , Linux MMC List , Linux Kernel Mailing List , grant.likely@secretlab.ca, Linux SPI Devel List , cjb@laptop.org, Linux ARM Kernel List Date: Fri, 31 Aug 2012 22:32:57 +0530 In-Reply-To: <5040E6C7.6030106@ti.com> References: <1345684176-21472-1-git-send-email-mporter@ti.com> <1345684176-21472-4-git-send-email-mporter@ti.com> <503F75C0.1050507@ti.com> <20120830144307.GA26737@beef> <5040E00A.3080600@ti.com> <1346430709.15463.15.camel@vkoul-mobl4> <5040E6C7.6030106@ti.com> Organization: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 798 Lines: 22 On Fri, 2012-08-31 at 22:01 +0530, Sekhar Nori wrote: > >> Yes, this was the problem. Since the SPI driver now depends on > >> CONFIG_TI_EDMA for basic operation may be select CONFIG_TI_EDMA in > >> Kconfig if SPI is enabled? That should do until the fallback to PIO > is > >> implemented. > > Then this should be enabled for SPI. Care to send a patch > > By 'this' you mean the Kconfig select? Then there should be no need of > a > new patch for this. It can be part of this patch itself, no? Either way is okay for me. -- ~Vinod Koul Intel Corp. -- 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/