Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp3755341pxu; Sun, 11 Oct 2020 23:23:20 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwB6GBDJb50nL9BZC0rhKiUfPeKoSDaL02MKsdpHKoUfOGZNZnTa86YoBlpnCC0kAD/cuUK X-Received: by 2002:a50:cf8a:: with SMTP id h10mr12762477edk.43.1602483800274; Sun, 11 Oct 2020 23:23:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602483800; cv=none; d=google.com; s=arc-20160816; b=b7gKPujauqgsAkOfhbilK54meKEQ4Ey78j3GXMDVVyKHbyRXPSiHUehcxBg1ckCc/2 MJWwHjuFZIJWKBOGWOypDwMkMklAgI5H4fTdsAZ9WCmky+1CeDskruPVPw6EfbgiSJmu yUmwf29aIdI09gvAgvInKKOWx2pmyTG4BZi4PzBOfszLqNwkVroVnzNzuwWHsFfLhiwE As4qDdB7NzflGMKuMpDiSTtuoa8+XvDHNSDoh/3x1AZwvwTFwQWS/Pq4H83X9k3dL+13 fj6lMjxkFc/LPFtILalXudeurz22VEIXCkd7Ow41HShB9Mhpbnv5Fh9SyQ0hmuiA83Zs Rx0Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=86vHVTiB07/+uJYtB/yjSlmr18dz7V76y328MuwTcRY=; b=deGSpPDDX18JroNOAQIsq3ZiRCVTtG8fPx6Ijt9rMqYOZ1ec5GYqeYrJjCuHdxifzx yR3OmZmWHMDAyD7ofCld4cgy95PCidU3QGe1hUbKtOdxJ0kAdMd49zwPWJVh+ejAsGBc 5htG+O5O+QKJAEylcTY1UY7BkX1WPLvzCHsOX66S/cLHIcmOQAA7qxi3iuSdWu9el7L/ XMYtIjccqADOcTQFWfsel2aORerF8yGtLp9geBYFrx9q32NfHlwK0FakJyHpbfnuPciW 7ZnPb+lO2zVCpA1XKF5q7I7DJLcr/ykyLrFzFeAonBU8Yj3ssUbFwxR0JHMlCYYIwPYG cbug== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="prFNN/Lg"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w5si12263136edj.536.2020.10.11.23.22.57; Sun, 11 Oct 2020 23:23:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="prFNN/Lg"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727165AbgJLGJW (ORCPT + 99 others); Mon, 12 Oct 2020 02:09:22 -0400 Received: from mail.kernel.org ([198.145.29.99]:46330 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726337AbgJLGJV (ORCPT ); Mon, 12 Oct 2020 02:09:21 -0400 Received: from localhost (unknown [122.182.245.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 6BDB920757; Mon, 12 Oct 2020 06:09:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1602482961; bh=GPU8CP6xKnWURBquscB890UF3K7DVSENbbTjU0EOU3A=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=prFNN/Lgyqvvw6oyH5tHsdNyhvz7J9fnspEpav3BNtPSmXWEHte305llkJ9+etXiM 2Zvxj4RuV2Vc2NenmjoWKYzrHqTVnxkWVhxw/itvpB+3ymUqEHmZrdEcQkX6oU8+VR 1Gai7wI58vNqj1NZZm/xU2I3LEScUvfdsyQb0lLk= Date: Mon, 12 Oct 2020 11:39:16 +0530 From: Vinod Koul To: Peter Ujfalusi Cc: dmaengine@vger.kernel.org, Rob Herring , Bjorn Andersson , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 2/3] dmaengine: add peripheral configuration Message-ID: <20201012060916.GI2968@vkoul-mobl> References: <20201008123151.764238-1-vkoul@kernel.org> <20201008123151.764238-3-vkoul@kernel.org> <20201009103019.GD2968@vkoul-mobl> <20201009111515.GF2968@vkoul-mobl> <13fdee71-5060-83fc-d69d-8ec73f82fac4@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <13fdee71-5060-83fc-d69d-8ec73f82fac4@ti.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09-10-20, 14:29, Peter Ujfalusi wrote: > > > On 09/10/2020 14.15, Vinod Koul wrote: > >>> If for any any reason subsequent txn is for different direction, I would > >>> expect that parameters are set again before prep_ calls > >> > >> But in DEV_TO_DEV? > > > > Do we support that :D > > > >> If we have two peripherals, both needs config: > >> p1_config and p2_config > >> > >> What and how would one use the single peripheral_config? > > > > Since the config is implementation specific, I do not think it limits. > > You may create > > > > struct peter_config { > > struct p1_config; > > struct p2_config; > > }; > > The use case is: > MEM -DMA-> P1 -DMA-> P2 > or > P2 -DMA-> P1 -DMA-> MEM > or > MEM -DMA-> P2 > or > P2 -DMA-> MEM > or > MEM -DMA-> P1 -DMA-> MEM > > How would the DMA guess what it should do? How would the independent P1 > and P2 would know how to set up the config? As I said, we do not support DEV_TO_DEV yet :) Question is how would p1<-->p2 look, will p1 initiate a DMA txn or p2..? who will configure these.. Do you have a real world example in horizon... -- ~Vinod