From: Vidya Sagar <vidyas@nvidia.com>
To: Jingoo Han <jingoohan1@gmail.com>,
"gustavo.pimentel@synopsys.com" <gustavo.pimentel@synopsys.com>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"Jisheng.Zhang@synaptics.com" <Jisheng.Zhang@synaptics.com>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"kishon@ti.com" <kishon@ti.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kthota@nvidia.com" <kthota@nvidia.com>,
"mmaddireddy@nvidia.com" <mmaddireddy@nvidia.com>,
"sagar.tv@gmail.com" <sagar.tv@gmail.com>
Subject: Re: [PATCH V6 2/3] PCI: dwc: Cleanup DBI read and write APIs
Date: Sat, 22 Jun 2019 20:31:14 +0530 [thread overview]
Message-ID: <625ef12e-8986-b935-0b1b-a437c518ac29@nvidia.com> (raw)
In-Reply-To: <PSXP216MB0662399C169A6D944E7C6A8FAAE60@PSXP216MB0662.KORP216.PROD.OUTLOOK.COM>
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 <vidyas@nvidia.com>
>> ---
>> 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
>
next prev parent reply other threads:[~2019-06-22 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 11:09 [PATCH V6 1/3] PCI: dwc: Add API support to de-initialize host Vidya Sagar
2019-06-21 11:09 ` [PATCH V6 2/3] PCI: dwc: Cleanup DBI read and write APIs Vidya Sagar
2019-06-21 14:32 ` Lorenzo Pieralisi
2019-06-22 5:26 ` Jingoo Han
2019-06-22 15:01 ` Vidya Sagar [this message]
2019-06-21 11:10 ` [PATCH V6 3/3] PCI: dwc: Export APIs to support .remove() implementation Vidya Sagar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=625ef12e-8986-b935-0b1b-a437c518ac29@nvidia.com \
--to=vidyas@nvidia.com \
--cc=Jisheng.Zhang@synaptics.com \
--cc=bhelgaas@google.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=kishon@ti.com \
--cc=kthota@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mmaddireddy@nvidia.com \
--cc=sagar.tv@gmail.com \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox