From: Manivannan Sadhasivam <mani@kernel.org>
To: Thippeswamy Havalige <thippeswamy.havalige@amd.com>
Cc: bhelgaas@google.com, lpieralisi@kernel.org, kw@linux.com,
manivannan.sadhasivam@linaro.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, michal.simek@amd.com,
bharat.kumar.gogada@amd.com
Subject: Re: [PATCH v2 2/2] PCI: xilinx-cpm: Add support for Versal Net CPM5NC Root Port controller
Date: Fri, 14 Feb 2025 21:25:36 +0530 [thread overview]
Message-ID: <20250214155536.ap7mjvutnuledkki@thinkpad> (raw)
In-Reply-To: <20250212055059.346452-3-thippeswamy.havalige@amd.com>
On Wed, Feb 12, 2025 at 11:20:59AM +0530, Thippeswamy Havalige wrote:
> The Versal Net ACAP (Adaptive Compute Acceleration Platform) devices
> incorporate the Coherency and PCIe Gen5 Module, specifically the
> Next-Generation Compact Module (CPM5NC).
>
> The integrated CPM5NC block, along with the built-in bridge, can function
> as a PCIe Root Port & supports the PCIe Gen5 protocol with data transfer
> rates of up to 32 GT/s, capable of supporting up to a x16 lane-width
> configuration.
>
> Bridge errors are managed using a specific interrupt line designed for
> CPM5N. Intx interrupt support is not available.
>
> Currently in this patch Bridge errors support is not added.
s/patch/commit,
>
> Signed-off-by: Thippeswamy Havalige <thippeswamy.havalige@amd.com>
> ---
> Changes in v2:
> - Update commit message.
> ---
> drivers/pci/controller/pcie-xilinx-cpm.c | 85 ++++++++++++++----------
> 1 file changed, 51 insertions(+), 34 deletions(-)
>
> diff --git a/drivers/pci/controller/pcie-xilinx-cpm.c b/drivers/pci/controller/pcie-xilinx-cpm.c
> index 81e8bfae53d0..c26ba662efd7 100644
> --- a/drivers/pci/controller/pcie-xilinx-cpm.c
> +++ b/drivers/pci/controller/pcie-xilinx-cpm.c
> @@ -84,6 +84,7 @@ enum xilinx_cpm_version {
> CPM,
> CPM5,
> CPM5_HOST1,
> + CPM5NC_HOST,
> };
>
> /**
> @@ -483,31 +484,33 @@ static void xilinx_cpm_pcie_init_port(struct xilinx_cpm_pcie *port)
> else
> dev_info(port->dev, "PCIe Link is DOWN\n");
>
> - /* Disable all interrupts */
> - pcie_write(port, ~XILINX_CPM_PCIE_IDR_ALL_MASK,
> - XILINX_CPM_PCIE_REG_IMR);
> -
> - /* Clear pending interrupts */
> - pcie_write(port, pcie_read(port, XILINX_CPM_PCIE_REG_IDR) &
> - XILINX_CPM_PCIE_IMR_ALL_MASK,
> - XILINX_CPM_PCIE_REG_IDR);
> -
> - /*
> - * XILINX_CPM_PCIE_MISC_IR_ENABLE register is mapped to
> - * CPM SLCR block.
> - */
> - writel(variant->ir_misc_value,
> - port->cpm_base + XILINX_CPM_PCIE_MISC_IR_ENABLE);
> + if (variant->version != CPM5NC_HOST) {
How about,
if (variant->version != CPM5NC_HOST)
return;
Btw, what is the reason to skip these register settings for this controller?
Especially the 'Bridge enable bit'.
> + /* Disable all interrupts */
> + pcie_write(port, ~XILINX_CPM_PCIE_IDR_ALL_MASK,
> + XILINX_CPM_PCIE_REG_IMR);
> +
> + /* Clear pending interrupts */
> + pcie_write(port, pcie_read(port, XILINX_CPM_PCIE_REG_IDR) &
> + XILINX_CPM_PCIE_IMR_ALL_MASK,
> + XILINX_CPM_PCIE_REG_IDR);
> +
> + /*
> + * XILINX_CPM_PCIE_MISC_IR_ENABLE register is mapped to
> + * CPM SLCR block.
Please make use of 80 column width.
> + */
> + writel(variant->ir_misc_value,
> + port->cpm_base + XILINX_CPM_PCIE_MISC_IR_ENABLE);
> +
> + if (variant->ir_enable) {
nit: you don't need braces here.
- Mani
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2025-02-14 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 5:50 [PATCH v2 0/2] Add support for Versal Net CPM5N Root Port controller Thippeswamy Havalige
2025-02-12 5:50 ` [PATCH v2 1/2] dt-bindings: PCI: xilinx-cpm: Add compatible string for CPM5NC Versal Net host Thippeswamy Havalige
2025-02-14 15:45 ` Manivannan Sadhasivam
2025-02-17 5:32 ` Havalige, Thippeswamy
2025-02-12 5:50 ` [PATCH v2 2/2] PCI: xilinx-cpm: Add support for Versal Net CPM5NC Root Port controller Thippeswamy Havalige
2025-02-14 15:55 ` Manivannan Sadhasivam [this message]
2025-02-17 5:38 ` Havalige, Thippeswamy
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=20250214155536.ap7mjvutnuledkki@thinkpad \
--to=mani@kernel.org \
--cc=bharat.kumar.gogada@amd.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=michal.simek@amd.com \
--cc=robh@kernel.org \
--cc=thippeswamy.havalige@amd.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