From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: "Krzysztof Wilczyński" <kw@linux.com>
Cc: Siddharth Vadapalli <s-vadapalli@ti.com>, <lpieralisi@kernel.org>,
<vigneshr@ti.com>, <manivannan.sadhasivam@linaro.org>,
<robh@kernel.org>, <bhelgaas@google.com>, <rogerq@kernel.org>,
<linux-omap@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <srk@ti.com>
Subject: Re: [PATCH] PCI: j721e: Fix the value of linkdown_irq_regfield for J784S4
Date: Tue, 11 Mar 2025 10:48:06 +0530 [thread overview]
Message-ID: <20250311051806.smcu4o4dxpngimth@uda0492258> (raw)
In-Reply-To: <20250310210746.GA2377483@rocinante>
On Tue, Mar 11, 2025 at 06:07:46AM +0900, Krzysztof Wilczyński wrote:
> Hello,
>
> > Hence, set 'linkdown_irq_regfield' to the macro 'J7200_LINK_DOWN' which
> > expands to BIT(10) and was first defined for the J7200 SoC. Other SoCs
> > already reuse this macro since it accurately represents the link-state
> > field in their respective "PCIE_INTD_ENABLE_REG_SYS_2" register.
>
> Can you confirm for me that the following use the correct macro?
>
> 333-static const struct j721e_pcie_data j721e_pcie_rc_data = {
> 337: .linkdown_irq_regfield = LINK_DOWN,
>
> 341-static const struct j721e_pcie_data j721e_pcie_ep_data = {
> 343: .linkdown_irq_regfield = LINK_DOWN,
>
> 347-static const struct j721e_pcie_data j7200_pcie_rc_data = {
> 350: .linkdown_irq_regfield = J7200_LINK_DOWN,
>
> 362-static const struct j721e_pcie_data am64_pcie_rc_data = {
> 364: .linkdown_irq_regfield = J7200_LINK_DOWN,
>
> 369-static const struct j721e_pcie_data am64_pcie_ep_data = {
> 371: .linkdown_irq_regfield = J7200_LINK_DOWN,
>
> 375-static const struct j721e_pcie_data j784s4_pcie_rc_data = {
> 379: .linkdown_irq_regfield = LINK_DOWN,
>
> 383-static const struct j721e_pcie_data j784s4_pcie_ep_data = {
> 385: .linkdown_irq_regfield = LINK_DOWN,
>
> 389-static const struct j721e_pcie_data j722s_pcie_rc_data = {
> 391: .linkdown_irq_regfield = J7200_LINK_DOWN,
>
> I am asking as some use LINK_DOWN, so I wanted to make sure.
Yes, the above are accurate except for J784S4 which is fixed by this
patch. LINK_DOWN i.e. BIT(1) is applicable only to J721E which was the
first SoC after which the driver has been named. For all other SoCs, the
integration of the PCIe Controller into the SoC led to BIT(10) of the
register being used to indicate the link status.
>
> Tht said, the following has no .linkdown_irq_regfield property set:
>
> 355-static const struct j721e_pcie_data j7200_pcie_ep_data = {
> 356- .mode = PCI_MODE_EP,
> 357- .quirk_detect_quiet_flag = true,
> 358- .quirk_disable_flr = true,
> 359- .max_lanes = 2,
> 360-};
>
> Would this be a problem? Or is this as expected?
Thank you for pointing this out. This has to be fixed and the
"linkdown_irq_regfield" member has to be added to match
j7200_pcie_rc_data. I will post the fix for this.
Regards,
Siddharth.
next prev parent reply other threads:[~2025-03-11 5:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 13:20 [PATCH] PCI: j721e: Fix the value of linkdown_irq_regfield for J784S4 Siddharth Vadapalli
2025-03-10 21:07 ` Krzysztof Wilczyński
2025-03-11 5:18 ` Siddharth Vadapalli [this message]
2025-03-11 7:25 ` Krzysztof Wilczyński
2025-03-11 7:32 ` Siddharth Vadapalli
2025-03-11 15:21 ` Krzysztof Wilczyński
2025-03-11 15:29 ` Siddharth Vadapalli
2025-03-11 15:34 ` Krzysztof Wilczyński
2025-03-11 15:00 ` Krzysztof Wilczyński
2025-03-12 16:16 ` Bjorn Helgaas
2025-03-13 5:55 ` Siddharth Vadapalli
2025-03-13 16:02 ` Bjorn Helgaas
2025-03-14 4:17 ` Siddharth Vadapalli
2025-03-26 6:54 ` Krzysztof Wilczyński
2025-03-26 7:01 ` Siddharth Vadapalli
2025-03-26 7:08 ` Krzysztof Wilczyński
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=20250311051806.smcu4o4dxpngimth@uda0492258 \
--to=s-vadapalli@ti.com \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=srk@ti.com \
--cc=stable@vger.kernel.org \
--cc=vigneshr@ti.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