Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752881AbbFHNW5 (ORCPT ); Mon, 8 Jun 2015 09:22:57 -0400 Received: from devils.ext.ti.com ([198.47.26.153]:52915 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752574AbbFHNWt (ORCPT ); Mon, 8 Jun 2015 09:22:49 -0400 From: Peter Ujfalusi To: , Tony Lindgren CC: , , , Subject: [PATCH v2 0/2] dmaengine: ti-dma-crossbar: Support for eDMA Date: Mon, 8 Jun 2015 16:22:40 +0300 Message-ID: <1433769762-31827-1-git-send-email-peter.ujfalusi@ti.com> X-Mailer: git-send-email 2.4.2 MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1182 Lines: 35 Hi, Changes since v01: - Drop change in compatible for the crossbar driver and do the configuration based on the DT structure. The ti-dma-crossbar driver in it's current form can work when it is used with sDMA (omap-dma). On DRA7x class of devices we have both sDMA and eDMA available. The sDMA driver expects to get the DMA request line with offset 1. The eDMA stack does not need the offset. The crosbbar itself is identical for sDMA and eDMA. At probe time the driver will do a match to figure out which dma engine it is connected to and based on that information it will configure the offset needed by the DMA driver. Regards, Peter --- Misael Lopez Cruz (1): dmaengine: ti-dma-crossbar: Make idr xbar instance-specific Peter Ujfalusi (1): dmaengine: ti-dma-crossbar: Add support for eDMA drivers/dma/ti-dma-crossbar.c | 34 +++++++++++++++++++++++++++++----- 1 file changed, 29 insertions(+), 5 deletions(-) -- 2.4.2 -- 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/