From: Vidya Sagar <vidyas@nvidia.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: <lorenzo.pieralisi@arm.com>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <thierry.reding@gmail.com>,
<jonathanh@nvidia.com>, <kishon@ti.com>,
<catalin.marinas@arm.com>, <will.deacon@arm.com>,
<jingoohan1@gmail.com>, <gustavo.pimentel@synopsys.com>,
<mperttunen@nvidia.com>, <linux-pci@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <kthota@nvidia.com>,
<mmaddireddy@nvidia.com>, <sagar.tv@gmail.com>
Subject: Re: [PATCH V4 05/16] PCI: dwc: Move config space capability search API
Date: Wed, 24 Apr 2019 08:41:59 +0530 [thread overview]
Message-ID: <22c7a99b-2d6c-e49b-43b0-219c60f7e5e9@nvidia.com> (raw)
In-Reply-To: <20190423203244.GD14616@google.com>
On 4/24/2019 2:02 AM, Bjorn Helgaas wrote:
> On Tue, Apr 23, 2019 at 01:57:19PM +0530, Vidya Sagar wrote:
>> Move PCIe config space capability search API to common DesignWare file
>> as this can be used by both host and ep mode codes.
>>
>> Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
>> Acked-by: Gustavo Pimentel <gustavo.pimentel@synopsys.com>
>> ---
>> Changes from [v3]:
>> * Rebased to linux-next top of the tree
>>
>> Changes from [v2]:
>> * None
>>
>> Changes from [v1]:
>> * Removed dw_pcie_find_next_ext_capability() API from here and made a
>> separate patch for that
>>
>> drivers/pci/controller/dwc/pcie-designware.c | 33 ++++++++++++++++++++
>> drivers/pci/controller/dwc/pcie-designware.h | 2 ++
>
> You claim this is a "move", but I only see adds. Where did it move
> *from*?
These are supposed to be moved from pcie-designware-ep.c file. That was the case
with my old patches but when I rebased them onto ToT, I missed the change that
removes them from pcie-designware-ep.c file. Thanks for catching this. I'll
address it in the next patch.
>
> While you're at it, can you add a comment in the code about why we
> can't use the regular pci_find_capability() interface? It's really a
> shame to have to reimplement that.
Regular pci_find_capability() uses 'struct pci_dev *dev' pointer and can be used
only after device enumeration is done. Whereas, these APIs are used particularly
before link up and use 'struct dw_pcie *pci' pointer.
>
>> 2 files changed, 35 insertions(+)
>>
>> diff --git a/drivers/pci/controller/dwc/pcie-designware.c b/drivers/pci/controller/dwc/pcie-designware.c
>> index 8e0081ccf83b..6a98135244d6 100644
>> --- a/drivers/pci/controller/dwc/pcie-designware.c
>> +++ b/drivers/pci/controller/dwc/pcie-designware.c
>> @@ -20,6 +20,39 @@
>> #define PCIE_PHY_DEBUG_R1_LINK_UP (0x1 << 4)
>> #define PCIE_PHY_DEBUG_R1_LINK_IN_TRAINING (0x1 << 29)
>>
>> +static u8 __dw_pcie_find_next_cap(struct dw_pcie *pci, u8 cap_ptr,
>> + u8 cap)
>> +{
>> + u8 cap_id, next_cap_ptr;
>> + u16 reg;
>> +
>> + reg = dw_pcie_readw_dbi(pci, cap_ptr);
>> + next_cap_ptr = (reg & 0xff00) >> 8;
>> + cap_id = (reg & 0x00ff);
>> +
>> + if (!next_cap_ptr || cap_id > PCI_CAP_ID_MAX)
>> + return 0;
>> +
>> + if (cap_id == cap)
>> + return cap_ptr;
>> +
>> + return __dw_pcie_find_next_cap(pci, next_cap_ptr, cap);
>> +}
>> +
>> +u8 dw_pcie_find_capability(struct dw_pcie *pci, u8 cap)
>> +{
>> + u8 next_cap_ptr;
>> + u16 reg;
>> +
>> + reg = dw_pcie_readw_dbi(pci, PCI_CAPABILITY_LIST);
>> + next_cap_ptr = (reg & 0x00ff);
>> +
>> + if (!next_cap_ptr)
>> + return 0;
>> +
>> + return __dw_pcie_find_next_cap(pci, next_cap_ptr, cap);
>> +}
>> +
>> int dw_pcie_read(void __iomem *addr, int size, u32 *val)
>> {
>> if (!IS_ALIGNED((uintptr_t)addr, size)) {
>> diff --git a/drivers/pci/controller/dwc/pcie-designware.h b/drivers/pci/controller/dwc/pcie-designware.h
>> index 9ee98ced1ef6..35160b4ce929 100644
>> --- a/drivers/pci/controller/dwc/pcie-designware.h
>> +++ b/drivers/pci/controller/dwc/pcie-designware.h
>> @@ -248,6 +248,8 @@ struct dw_pcie {
>> #define to_dw_pcie_from_ep(endpoint) \
>> container_of((endpoint), struct dw_pcie, ep)
>>
>> +u8 dw_pcie_find_capability(struct dw_pcie *pci, u8 cap);
>> +
>> int dw_pcie_read(void __iomem *addr, int size, u32 *val);
>> int dw_pcie_write(void __iomem *addr, int size, u32 val);
>>
>> --
>> 2.17.1
>>
next prev parent reply other threads:[~2019-04-24 3:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 8:27 [PATCH V4 00/16] Add Tegra194 PCIe support Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 01/16] PCI: Add #defines for some of PCIe spec r4.0 features Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 02/16] PCI/PME: Export pcie_pme_disable_msi() & pcie_pme_no_msi() APIs Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 03/16] PCI: Export pcie_bus_config symbol Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 04/16] PCI: dwc: Perform dbi regs write lock towards the end Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 05/16] PCI: dwc: Move config space capability search API Vidya Sagar
2019-04-23 20:32 ` Bjorn Helgaas
2019-04-24 3:11 ` Vidya Sagar [this message]
2019-04-24 3:42 ` Oliver
2019-04-24 8:10 ` Gustavo Pimentel
2019-04-23 8:27 ` [PATCH V4 06/16] PCI: dwc: Add ext " Vidya Sagar
2019-04-23 20:35 ` Bjorn Helgaas
2019-04-24 3:12 ` Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 07/16] dt-bindings: PCI: designware: Add binding for CDM register check Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 08/16] PCI: dwc: Add support to enable " Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 09/16] Documentation/devicetree: Add PCIe supports-clkreq property Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 10/16] dt-bindings: PCI: tegra: Add device tree support for T194 Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 11/16] dt-bindings: PHY: P2U: Add Tegra 194 P2U block Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 12/16] arm64: tegra: Add P2U and PCIe controller nodes to Tegra194 DT Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 13/16] arm64: tegra: Enable PCIe slots in P2972-0000 board Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 14/16] phy: tegra: Add PCIe PIPE2UPHY support Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 15/16] PCI: tegra: Add Tegra194 PCIe support Vidya Sagar
2019-04-23 8:27 ` [PATCH V4 16/16] arm64: Add Tegra194 PCIe driver to defconfig 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=22c7a99b-2d6c-e49b-43b0-219c60f7e5e9@nvidia.com \
--to=vidyas@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=helgaas@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@ti.com \
--cc=kthota@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=mmaddireddy@nvidia.com \
--cc=mperttunen@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=sagar.tv@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=will.deacon@arm.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