From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753443AbbC3RY6 (ORCPT ); Mon, 30 Mar 2015 13:24:58 -0400 Received: from mga11.intel.com ([192.55.52.93]:51720 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752767AbbC3RY4 (ORCPT ); Mon, 30 Mar 2015 13:24:56 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,494,1422950400"; d="scan'208";a="700266939" Date: Mon, 30 Mar 2015 22:50:23 +0530 From: Vinod Koul To: Peter Ujfalusi Cc: tony@atomide.com, linux@arm.linux.org.uk, grant.likely@linaro.org, dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, robh+dt@kernel.org, nm@ti.com Subject: Re: [PATCH v2 1/7] dmaengine: of_dma: Support for DMA routers Message-ID: <20150330172023.GH7192@intel.com> References: <1426080210-841-1-git-send-email-peter.ujfalusi@ti.com> <1426080210-841-2-git-send-email-peter.ujfalusi@ti.com> <20150326105018.GJ32683@intel.com> <5513F77A.4030005@ti.com> <20150326153221.GM32683@intel.com> <55154C39.3030602@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55154C39.3030602@ti.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 27, 2015 at 02:25:29PM +0200, Peter Ujfalusi wrote: > On 03/26/2015 05:32 PM, Vinod Koul wrote: > >> I have added the DT binding document since this series adds support for > >> routers for platforms booting with DT: > >> > >> Documentation/devicetree/bindings/dma/dma.txt | 28 ++++++++ > > I meant the update to Documnetation/dmanegine/ for routers :) > > I see. In what form you think we should have the documentation? Is it adequate > to lift and adjust the text from the DT binding document here? Should we have > a separate file for the router description? > My concern was and this is why I did not wrote anything under here is that the > code I add is only covers the DT boot case and I'm not planning to add legacy > support. The ACPI binding can be done in a similar fashion as the DT so you > would have a translator driver with ACPI API. Not the binding part but more of a guideline on how to go about solving the DMA router design for drivers -- ~Vinod