Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp630051rwr; Wed, 19 Apr 2023 10:47:54 -0700 (PDT) X-Google-Smtp-Source: AKy350YdM2lhaz8X3b4Nwaj1dhiUSLG/mMeJtq6JEkhYsAN5Fymfadxg+oAdT7NmxIDzIIPaUYX2 X-Received: by 2002:a05:6a20:6a1e:b0:f0:ac6b:379e with SMTP id p30-20020a056a206a1e00b000f0ac6b379emr5307593pzk.4.1681926474376; Wed, 19 Apr 2023 10:47:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681926474; cv=none; d=google.com; s=arc-20160816; b=ERk0MLrjD07tRY79JpZiANrzkRwXOGSLSfCktRvdUKT6P4F3qrSS5Up+SHwQOPNeUv gR4naxvAFY23lqhLaTt6LdUyDJkl4fzK3bQ1CRFASHwOJ0el6fC5T3FZ8Mt4Sv2WZNPK S9mEVuK5iyQUm7bT80WxJ0S3kKS6dxIAyYQQkOqyB7mPGR4w78lZkWDzz+7x+LDia2MY d5nbtqENx7KhzjgqDQcBTZcV+nc++b309Juedsm5QqBXdz9N7HGdPKWXPd3Ad1e0bBMx jqvm+W9mUM03M6iCg4bznZantb+yky/yk4uqXWgcw+YmYMpXd1rwg58/p1+EiObyPGGP ZOZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:organization:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=K6CdgErcQ4pnGGAkF90aoT3gyfB+SwEVIuKsFAqClPg=; b=Qsvd6duNVT4SBKEhxsj7jk5dEQ90lcVhKVGoykyU/qhZEB5+7KnMy9Q/81i5qS1Wqq CXTkZV2ZKtNi9e9Y9J5Un/bPhxY5Wmjys8+Yb6413ML2F0RykxnialFR8WSdrt1PzRpP j8ayR92AJtKOSjs6v0ezquNnMpC4rjJYxjm+R/jd7D3Pos5LsNNkJiBBc/w0ARoxgJSV GTFGiwDYcmKjwlP6KoemFRXG157UqLLahOExKH96TXpkVpQYuBjL3swdDoAAH1fFd2ji LCXHHmNQKpqRueqRBDiKlL1d/gVZYV5g/TikQTgsMhtKhelPSgV4FJnx1+fZzrjY/C0m iVdQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=oCDaDlKT; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w17-20020aa79a11000000b0063b754972f4si12875438pfj.159.2023.04.19.10.47.41; Wed, 19 Apr 2023 10:47:54 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=oCDaDlKT; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230032AbjDSRfO (ORCPT + 99 others); Wed, 19 Apr 2023 13:35:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43100 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229575AbjDSRfM (ORCPT ); Wed, 19 Apr 2023 13:35:12 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E268A6A6E; Wed, 19 Apr 2023 10:35:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1681925711; x=1713461711; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=4qXm5eWpcBEMDu4cseUDl5qOFRKxr2ED5XonItnH7PA=; b=oCDaDlKTEN/8FUQjfUg1Zqw8UKbZkDprPZyrUiIWy8zE0Zuh4zKDIENL u84UdS5xmiiSC+WwH+68n/7XTM9R920gBLcPkdB2Ls3V3x2aBGsjI05uY sAM74zSvmNkkwf5WArV4VRZeWpiqFYqfQOE/bAxi62XND6RUsjUpy6PfJ A0ox9j8WVUDYViqUV3oFMqkFOG90z0YiWdXC54z3dqAMCDjRHNRmv0Rnb 1Q3nSZLtMNUdci90IpmZTvd1ZDHUXivDBrzQ6kOVgowRYSyQUtRRmrZ0G 2CIBrINQvt0DYsZsDMewFRnUDVoWBBrb8L2UVapD1cl33BTj9hfTYTRqK A==; X-IronPort-AV: E=McAfee;i="6600,9927,10685"; a="342993840" X-IronPort-AV: E=Sophos;i="5.99,208,1677571200"; d="scan'208";a="342993840" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Apr 2023 10:35:11 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10685"; a="937755813" X-IronPort-AV: E=Sophos;i="5.99,208,1677571200"; d="scan'208";a="937755813" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga006.fm.intel.com with ESMTP; 19 Apr 2023 10:35:09 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1ppBhz-002KRH-2A; Wed, 19 Apr 2023 20:35:07 +0300 Date: Wed, 19 Apr 2023 20:35:07 +0300 From: Andy Shevchenko To: Joy Chakraborty Cc: Serge Semin , Mark Brown , linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, manugautam@google.com, rohitner@google.com Subject: Re: [PATCH v7 4/5] spi: dw: Add DMA address widths capability check Message-ID: References: <20230418052902.1336866-1-joychakr@google.com> <20230418052902.1336866-5-joychakr@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 19, 2023 at 06:18:04PM +0530, Joy Chakraborty wrote: > On Wed, Apr 19, 2023 at 5:19 PM Andy Shevchenko > wrote: > > On Wed, Apr 19, 2023 at 11:18:25AM +0530, Joy Chakraborty wrote: > > > On Tue, Apr 18, 2023 at 1:08 PM Andy Shevchenko > > > wrote: > > > > On Tue, Apr 18, 2023 at 05:29:01AM +0000, Joy Chakraborty wrote: ... > > > > > + /* > > > > > + * Assuming both channels belong to the same DMA controller hence the > > > > > + * address width capabilities most likely would be the same. > > > > > + */ > > > > > > > > I had a small comment on this In v6 thread. > > > > > > Sure, > > > > > > Your comment in V6 thread: > > > " > > > I would add something to explain the side of these address width, like > > > > > > * Assuming both channels belong to the same DMA controller hence > > > * the peripheral side address width capabilities most likely would > > > * be the same. > > > " > > > > > > I do not think the address width capabilities are dependent on the > > > side of generation like memory or peripheral. > > > > Yes, they are independent. Memory could do with 4 bytes, while peripheral with > > 1 byte and so on. > > > > > From what I understand, > > > address width capabilities are solely dependent on the transaction > > > generation capability of the DMA controller towards the system bus. > > > > What do you mean by a SB in the above? Memory? Peripheral? > > By system bus I mean anything that is connecting the Memory, DMA and > the peripheral. > Something like : > > +-----------+ +-------------------+ > | | | | > | DMA | | PERIPHERAL | > | | | | > +----^-+---+ +-----+--^---------+ > *** -->| | | | > | | | | > <------------+-v--------------------v---+-------------> > SYSTEM BUS > <---------------------+--^-----------------------------> > | | > | | > +----v--+-----+ > | | > | MEMORY | > | | > +--------------+ > *** : Address width capabilities should be the capability of the DMA > to generate transactions to the system bus on the marked interface > irrespective of whether it is destined for Peripheral or memory is > what I understand. That's misunderstanding. You used only one possible HW design, there may be more. For example we have Synopsys DesignWare DMA that has a lot of parameters to configure bus mastering. One of such a case, where it makes a lot of sense, is DesignWare SATA with the above mentioned DMA controller where it has two masters and they are connected towards memory and towards peripheral "buses". They have _different_ configurations. So, generally speaking what you are saying is not true. > > > What we intend to highlight here is the assumption that both tx and rx > > > channel would belong to the same DMA controller hence the transaction > > > generation capabilities would be the same both for read and write > > > (e.g. if the DMA controller is able to generate 32 bit sized reads > > > then it should also be able to generate 32 bit sized writes). > > > With this assumption we are doing a bitwise and of both tx and rx capabilities. > > > > > > Please let me know if you think otherwise. -- With Best Regards, Andy Shevchenko