Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp1266595ybh; Mon, 13 Jul 2020 13:57:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw2u90tZMF5yuJL7K37DwCppwZWMJqVtL66Q19K99X8Y1kBEjThsnGVjB3JdGLhUqY8i9HG X-Received: by 2002:aa7:d458:: with SMTP id q24mr1208945edr.25.1594673878841; Mon, 13 Jul 2020 13:57:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594673878; cv=none; d=google.com; s=arc-20160816; b=Jl1TqHsWn5FQMbnGoTieL8E6gzQjdD7mdKIS5O/xGYu7+MYRePtt/RasF/Z4R38sQ+ SGWlWG+JPAF2N/Eqa2/kbFERWAbdNLFUG9qV5EQFiNHeC7IgHFIb/mb0MVYyHn01HVdv zhX9JyimAFtufhDx2IrzXh22oVZJgJoR95UJHwH1EnUkhIb5xBuQuQRGBOjmGUxs+RnE oXlnV5bVvH3nUZ7eNB/GiCeSEnZCxDNJYRziGZfOjJz8wKv3swRtgnXHWSevbevov/4D veNIvzLKOSDHfyX7vmAB2fs2Z9pkKY+quzXIL7Qs4p+G0OD6K3R0/QwLFysYMDuV2GMV 4WVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:ironport-sdr:ironport-sdr; bh=q96RYsGslvrtThF7v8pdVyYkVN4ULkbxvY6gvT0X5Ro=; b=GCDXLiwuxf94DyKQ7CwEsZWXr+hfMqdn16ILvVx1o7xLc8r3S2wY7yRYhCCct7F+n0 MHHyo4tGAyCtamWZlFUwJuN1cf3OKkkNuJRX7oJ5uTA3OYjyc8/4lyFaQ/KXuQUg7dDU EMMi5oFr7cHCXAoVic3iaqNa7/hkNv2j7QM8er1dureLyZr+YWSp6wT8jSNyEO+JyocK a4MS+i5Kub2DPkoTOBqMPUZkCmxygxj1QpQePi/teDi2rmbZ62brCAdfNFG5DNX+sogg /7HDu+c4r6fsxlplFdFRaCm6e+1CLaaAPFPogpAWVP6qGlLMcm91mahhFtzMJLnBWN/6 lvrQ== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l13si9697121ejk.170.2020.07.13.13.57.35; Mon, 13 Jul 2020 13:57:58 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726742AbgGMUzR (ORCPT + 99 others); Mon, 13 Jul 2020 16:55:17 -0400 Received: from mga07.intel.com ([134.134.136.100]:49219 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726338AbgGMUzR (ORCPT ); Mon, 13 Jul 2020 16:55:17 -0400 IronPort-SDR: EbeLArq4HkKuXrlRxYpB/WS2qvAXL+eK3WEI4G9/favHK5tDRXMs139ILa9JUq6sYcrvGIBs++ dPhiTZl6KmIg== X-IronPort-AV: E=McAfee;i="6000,8403,9681"; a="213545772" X-IronPort-AV: E=Sophos;i="5.75,348,1589266800"; d="scan'208";a="213545772" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Jul 2020 13:55:16 -0700 IronPort-SDR: 7szJfcXPONfImWsDE0U1Og3oR6gRPzY9NXu27bBlEUhLsXyTzhLMHYMpnGwjaJkpOUSxedhjvm WmmYlkewsJUA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,348,1589266800"; d="scan'208";a="390288665" Received: from djiang5-mobl1.amr.corp.intel.com (HELO [10.212.172.11]) ([10.212.172.11]) by fmsmga001.fm.intel.com with ESMTP; 13 Jul 2020 13:55:15 -0700 Subject: Re: [PATCH v7 05/11] dmaengine: Introduce DMA-device device_caps callback To: Serge Semin , Andy Shevchenko Cc: Vinod Koul , Viresh Kumar , Dan Williams , Alexey Malahov , Thomas Bogendoerfer , Arnd Bergmann , Rob Herring , linux-mips@vger.kernel.org, devicetree@vger.kernel.org, dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org References: <20200709224550.15539-1-Sergey.Semin@baikalelectronics.ru> <20200709224550.15539-6-Sergey.Semin@baikalelectronics.ru> <20200710084503.GE3703480@smile.fi.intel.com> <20200710093834.su3nsjesnhntpd6d@mobilestation> From: Dave Jiang Message-ID: <07d4a977-1de6-b611-3d4f-7c7d6cd7fe5f@intel.com> Date: Mon, 13 Jul 2020 13:55:14 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <20200710093834.su3nsjesnhntpd6d@mobilestation> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/10/2020 2:38 AM, Serge Semin wrote: > On Fri, Jul 10, 2020 at 11:45:03AM +0300, Andy Shevchenko wrote: >> On Fri, Jul 10, 2020 at 01:45:44AM +0300, Serge Semin wrote: >>> There are DMA devices (like ours version of Synopsys DW DMAC) which have >>> DMA capabilities non-uniformly redistributed between the device channels. >>> In order to provide a way of exposing the channel-specific parameters to >>> the DMA engine consumers, we introduce a new DMA-device callback. In case >>> if provided it gets called from the dma_get_slave_caps() method and is >>> able to override the generic DMA-device capabilities. >> > >> In light of recent developments consider not to add 'slave' and a such words to the kernel. > > As long as the 'slave' word is used in the name of the dma_slave_caps > structure and in the rest of the DMA-engine subsystem, it will be ambiguous > to use some else terminology. If renaming needs to be done, then it should be > done synchronously for the whole subsystem. What about just calling it dma_device_caps? Consider this is a useful function not only slave DMA will utilize this. I can see this being useful for some of my future code with idxd driver. > > -Sergey > >> >> >> -- >> With Best Regards, >> Andy Shevchenko >> >>