Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932220AbbF0Oot (ORCPT ); Sat, 27 Jun 2015 10:44:49 -0400 Received: from mail-la0-f42.google.com ([209.85.215.42]:33712 "EHLO mail-la0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753538AbbF0Ook (ORCPT ); Sat, 27 Jun 2015 10:44:40 -0400 MIME-Version: 1.0 In-Reply-To: <20150627144054.GW19530@localhost> References: <1433831736-18253-1-git-send-email-appanad@xilinx.com> <20150622104932.GC19530@localhost> <20150627144054.GW19530@localhost> Date: Sat, 27 Jun 2015 17:44:38 +0300 Message-ID: Subject: Re: [PATCH v7] dma: Add Xilinx AXI Direct Memory Access Engine driver support From: Nicolae Rosia To: Vinod Koul Cc: Appana Durga Kedareswara Rao , "linux-kernel@vger.kernel.org" , Srikanth Thokala , Michal Simek , Soren Brinkmann , Anirudha Sarangi , "dmaengine@vger.kernel.org" , Punnaiah Choudary Kalluri , "dan.j.williams@intel.com" , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 761 Lines: 16 On Sat, Jun 27, 2015 at 5:40 PM, Vinod Koul wrote: [...] >> Please let me know if you are not clear. > No sorry am not... > > I asked how the device address in configured. For both MM2S S2MM you are > using sg for memory address, where are you getting device adress, are you > assuming/hardcoding or getting somehow, if so how? As the name says, one end is memory (MM) and the other end is an AXI4 Stream Bus (S) which has no concept of memory address. So yes, it is hardcoded at design time. -- 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/