Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp520028ybd; Sat, 22 Jun 2019 08:22:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqyGFBnEVrxUUxb5uWBEsl7KidTEPYaPKIJ3A/zJoTZo8HXzIVD/sNC1jax4Qw1tMA1n9Vih X-Received: by 2002:a17:902:a612:: with SMTP id u18mr6390125plq.181.1561216955628; Sat, 22 Jun 2019 08:22:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561216955; cv=none; d=google.com; s=arc-20160816; b=LAFyB85JEqSUj0Ocit/Blm9sccKjdNqGcI4GYPdOY0VXRR9wOTfb6WknwCqcJ9Fwy9 QIunoDtZthb8GmV0n9hX++gDUlzRGCxHXFLaViHGqVPe9+fODLmuO948XsSZjO+0tieg eC+NNjkaeVdtZMes3H8/QKrXQQj/IOWhKcOyIYxvAijXAW0hn76Bvc/19UcSE4FgvRf0 95BrQEioZXVh35GkzdsOM9ngaNtTAaAqaaaQZ/7I29tqkp2dtmqPoQs15QpRdXRp9Fu8 qEVL0jtcKrj2YIQatUIpzkSggB25Uq4xD8PHamGD2B3x9AjYYYFF1HE2tQC/DmsDsjeG QMaA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:dkim-signature:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=Gg6ynwqt5s5qIc9zttRBjajJzrIC+hXVHXW78gtZT6k=; b=sTXKsTNAp+qkI99ARlr9+hJT/lWFrfqj5soQ11mCAAqYnWVWN8aUxivp1F9PPbDOxw HDP/tBIT2t3wvvSPqCv+t1tfGFXsGdHVF4VG0Oe7Hd4mL1E2xcJoxni0t+3lJEkKl1xY fz8Sge46Q4Z5ZJm3/eLBU0saBd8rHvUPODMsChy8KeT1JphQCwp35VfGFUWWD/ZI0BVt f4qKtCyk1cm5nC6jXcfJ+Si90BrFwStMFEA4BJfovDrW/j2ssy97/r523/FpXgJ+gILR UQ8m1N0z1kzZCB5i7z+HKfduxsDONAvkK0nEkuRYxag8rBKKGUaobPL5ysrD7xZygl6q O8pg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=PnBlJaxJ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f8si5079183pgo.380.2019.06.22.08.22.19; Sat, 22 Jun 2019 08:22:35 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=PnBlJaxJ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726373AbfFVPU1 (ORCPT + 99 others); Sat, 22 Jun 2019 11:20:27 -0400 Received: from hqemgate15.nvidia.com ([216.228.121.64]:15570 "EHLO hqemgate15.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726138AbfFVPU1 (ORCPT ); Sat, 22 Jun 2019 11:20:27 -0400 Received: from hqpgpgate102.nvidia.com (Not Verified[216.228.121.13]) by hqemgate15.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Sat, 22 Jun 2019 08:20:27 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate102.nvidia.com (PGP Universal service); Sat, 22 Jun 2019 08:20:26 -0700 X-PGP-Universal: processed; by hqpgpgate102.nvidia.com on Sat, 22 Jun 2019 08:20:26 -0700 Received: from [10.25.72.60] (172.20.13.39) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sat, 22 Jun 2019 15:01:17 +0000 Subject: Re: [PATCH V6 2/3] PCI: dwc: Cleanup DBI read and write APIs To: Jingoo Han , "gustavo.pimentel@synopsys.com" , "lorenzo.pieralisi@arm.com" , "bhelgaas@google.com" , "Jisheng.Zhang@synaptics.com" , "thierry.reding@gmail.com" , "kishon@ti.com" CC: "linux-pci@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "kthota@nvidia.com" , "mmaddireddy@nvidia.com" , "sagar.tv@gmail.com" References: <20190621111000.23216-1-vidyas@nvidia.com> <20190621111000.23216-2-vidyas@nvidia.com> X-Nvconfidentiality: public From: Vidya Sagar Message-ID: <625ef12e-8986-b935-0b1b-a437c518ac29@nvidia.com> Date: Sat, 22 Jun 2019 20:31:14 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: X-Originating-IP: [172.20.13.39] X-ClientProxiedBy: HQMAIL107.nvidia.com (172.20.187.13) To HQMAIL107.nvidia.com (172.20.187.13) Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1561216828; bh=Gg6ynwqt5s5qIc9zttRBjajJzrIC+hXVHXW78gtZT6k=; h=X-PGP-Universal:Subject:To:CC:References:X-Nvconfidentiality:From: Message-ID:Date:User-Agent:MIME-Version:In-Reply-To: X-Originating-IP:X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=PnBlJaxJsQ2pdKDVSaXmZGLzacmfrdQdr7t8F8ZPGkdCZm/JejAkrFB5QeSG2dYU0 YsEyn/gy0z7d7uaYZ0TZ+nS95PBixeswFeTgGt5BaCevNhG7nTnNtZcs4mncXqyMU8 JUspGrgl7+nRB/dnTZbUfi0h3u0lK39N6KlRubcW2UzC3P7WlN8f2qqFHOevUo6jO6 CCpc51oJXo5LSS7dEsDGjfQP80JOlzX88YkGmcMl9tgFm85pFvlgEXNQfu71492FLW sB4+9Va81TiVBA/pP8LSqMAikiblnf6iCKIIr8V+SOBeb5QFR1auzPSFA0fXhmn0D2 n7wmVXzek6pnA== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/22/2019 10:56 AM, Jingoo Han wrote: > On 6/21/19, 8:10 PM, Vidya Sagar wrote: >> >> Cleanup DBI read and write APIs by removing "__" (underscore) from their >> names as there are no no-underscore versions and the underscore versions >> are already doing what no-underscore versions typically do. It also removes >> passing dbi/dbi2 base address as one of the arguments as the same can be >> derived with in read and write APIs. >> >> Signed-off-by: Vidya Sagar >> --- >> Changes from v5: >> * Removed passing base address as one of the arguments as the same can be derived within >> the API itself. >> * Modified ATU read/write APIs to call dw_pcie_{write/read}() API > > Unlike previous patches (v1~v5), you modified ATU read/write APIs from v6. > Why do you change ATU read/write APIs to call dw_pcie_{write/read}() API??? > It is not clean-up, but function change. Please add the reason to the commit message. > > Best regards, > Jingoo Han Reason is that, now dbi/dbi2 APIs don't take base address offset as one of the input arguments instead, those APIs derive that inside the API itself. So, for ATU read/write DBI read/write APIs can be used directly and hence I called dw_pcie_{write/read}() API directly. But, taking a second look at it, it may work for Tegra, but, may not for other implementations where accessing DBI space is not a simple read/write to DBI base + offset. Let me address address that too in next patch. Thanks, Vidya Sagar > >> >> Changes from v4: >> * This is a new patch in this series >> >> drivers/pci/controller/dwc/pcie-designware.c | 28 ++++++------- >> drivers/pci/controller/dwc/pcie-designware.h | 43 ++++++++++++-------- >> 2 files changed, 37 insertions(+), 34 deletions(-) > > ..... > >> static inline void dw_pcie_writel_atu(struct dw_pcie *pci, u32 reg, u32 val) >> { >> - __dw_pcie_write_dbi(pci, pci->atu_base, reg, 0x4, val); >> + int ret; >> + >> + ret = dw_pcie_write(pci->atu_base + reg, 0x4, val); >> + if (ret) >> + dev_err(pci->dev, "write ATU address failed\n"); >> } >> >> static inline u32 dw_pcie_readl_atu(struct dw_pcie *pci, u32 reg) >> { >> - return __dw_pcie_read_dbi(pci, pci->atu_base, reg, 0x4); >> + int ret; >> + u32 val; >> + >> + ret = dw_pcie_read(pci->atu_base + reg, 0x4, &val); >> + if (ret) >> + dev_err(pci->dev, "Read ATU address failed\n"); >> + >> + return val; >> } >> >> static inline void dw_pcie_dbi_ro_wr_en(struct dw_pcie *pci) >> -- >> 2.17.1 >