Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp396527ybt; Fri, 10 Jul 2020 02:40:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwWv8gTGRMRML3Ok1n0pgv7d2R30LKg3SN7t0ptEjlMNH4EYWLFwS9LaRj0GZCmVUh2/N6C X-Received: by 2002:a50:f702:: with SMTP id g2mr77523398edn.348.1594374032752; Fri, 10 Jul 2020 02:40:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594374032; cv=none; d=google.com; s=arc-20160816; b=QLAJ2raB7WvtDtArlJ7Nv2dZgT6rT8F1KfBwL9qB5Tbd4zHj48tl/s1pQMaYu8maej yGknkylOMILKZOCFAtJKr591EUi+i4tXfTPlJDiS8q/p0e4Oc8BKWrtUQoZZaEj+Pm9m VZSOSw5SWs7hic5P5mGv8YiJV2+FZGXQJnzFgpMLjGNLXoo4GIEEeYm0anWllHbU7j05 4GhptIgHy0YnNwM+Xpch0WJYkg6UE8rlmuY+LufIKdpPOMaDApHNOJGTqdsUI+S9irYp ManaNwCiNpJ8rhs1I60oma9OmH9EBG7n525mLH8aBqo4Tm0lPupgenkHRf4baD/K+FxT cggg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=Gh4aKfip7Tfb9Mzon3+nkoCM5jyN9nORLAQXp8/m7Cg=; b=MrrCHsKKanW9SfQ/N43bEaK29JWzEpS2rdNSVvQytzpAiSbbhGO8y3IQu2c9Qf1a8H jmhn8oe0/UlWlWzOnlAgGBV9F1eXuPQaBd72at3+SKb+SXHfYWVCTqfIup267Vpt7sE4 WoXn/jCRaQ6puSWRKs8wTNJwLySv9ogbDXGqXUdv+qb+So02Xqn/i9D0BvO7o88r8eHv 19i7A3UE9lrbMzVCzGV4WgUDIpkrK/4kfO+4zWYkjqORGcivzO1m/DoGKXkF6GdNvPnz g8au/40Jb0mDjAb5XPcAZDT+J9cTJZtvWoOYWBkoyJY87/o9315ZlHyJabu63Wq6h67H bHYQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dj11si3997598edb.279.2020.07.10.02.40.09; Fri, 10 Jul 2020 02:40:32 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727814AbgGJJii (ORCPT + 99 others); Fri, 10 Jul 2020 05:38:38 -0400 Received: from mail.baikalelectronics.com ([87.245.175.226]:49904 "EHLO mail.baikalelectronics.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726288AbgGJJii (ORCPT ); Fri, 10 Jul 2020 05:38:38 -0400 Received: from localhost (unknown [127.0.0.1]) by mail.baikalelectronics.ru (Postfix) with ESMTP id D2ABA803202B; Fri, 10 Jul 2020 09:38:35 +0000 (UTC) X-Virus-Scanned: amavisd-new at baikalelectronics.ru Received: from mail.baikalelectronics.ru ([127.0.0.1]) by localhost (mail.baikalelectronics.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S5HEgB7Js0P8; Fri, 10 Jul 2020 12:38:35 +0300 (MSK) Date: Fri, 10 Jul 2020 12:38:34 +0300 From: Serge Semin To: Andy Shevchenko CC: Vinod Koul , Viresh Kumar , Dan Williams , Alexey Malahov , Thomas Bogendoerfer , Arnd Bergmann , Rob Herring , , , , Subject: Re: [PATCH v7 05/11] dmaengine: Introduce DMA-device device_caps callback Message-ID: <20200710093834.su3nsjesnhntpd6d@mobilestation> References: <20200709224550.15539-1-Sergey.Semin@baikalelectronics.ru> <20200709224550.15539-6-Sergey.Semin@baikalelectronics.ru> <20200710084503.GE3703480@smile.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20200710084503.GE3703480@smile.fi.intel.com> X-ClientProxiedBy: MAIL.baikal.int (192.168.51.25) To mail (192.168.51.25) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. -Sergey > > > -- > With Best Regards, > Andy Shevchenko > >