From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Gowthami Thiagarajan <gthiagarajan@marvell.com>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] PCI : Fix pcie_flag_reg in set_pcie_port_type
Date: Mon, 16 Dec 2024 18:01:27 +0200 (EET) [thread overview]
Message-ID: <5047c4a8-dfce-a081-e4fa-c6da731eb01d@linux.intel.com> (raw)
In-Reply-To: <20241213070241.3334854-1-gthiagarajan@marvell.com>
On Fri, 13 Dec 2024, Gowthami Thiagarajan wrote:
> When an invalid PCIe topology is detected, the set_pcie_port_type function
> does not set the port type correctly. This issue can occur in
> configurations such as:
>
> Root Port ---> Downstream Port ---> Root Port
>
> In such cases, the topology is identified as invalid and due to the incorrect
> port type setting, the extended configuration space of the child device becomes
> inaccessible.
>
> Signed-off-by: Gowthami Thiagarajan <gthiagarajan@marvell.com>
> ---
> v1->v2:
> Updated commit description
>
> drivers/pci/probe.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> index 4f68414c3086..263ec21451d9 100644
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -1596,7 +1596,7 @@ void set_pcie_port_type(struct pci_dev *pdev)
> if (pcie_downstream_port(parent)) {
> pci_info(pdev, "claims to be downstream port but is acting as upstream port, correcting type\n");
> pdev->pcie_flags_reg &= ~PCI_EXP_FLAGS_TYPE;
> - pdev->pcie_flags_reg |= PCI_EXP_TYPE_UPSTREAM;
> + pdev->pcie_flags_reg |= PCI_EXP_TYPE_UPSTREAM << 4;
Use FIELD_PREP() please.
--
i.
> }
> } else if (type == PCI_EXP_TYPE_UPSTREAM) {
> /*
> @@ -1607,7 +1607,7 @@ void set_pcie_port_type(struct pci_dev *pdev)
> if (pci_pcie_type(parent) == PCI_EXP_TYPE_UPSTREAM) {
> pci_info(pdev, "claims to be upstream port but is acting as downstream port, correcting type\n");
> pdev->pcie_flags_reg &= ~PCI_EXP_FLAGS_TYPE;
> - pdev->pcie_flags_reg |= PCI_EXP_TYPE_DOWNSTREAM;
> + pdev->pcie_flags_reg |= PCI_EXP_TYPE_DOWNSTREAM << 4;
> }
> }
> }
>
prev parent reply other threads:[~2024-12-16 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 7:02 [PATCH v2] PCI : Fix pcie_flag_reg in set_pcie_port_type Gowthami Thiagarajan
2024-12-13 18:47 ` Bjorn Helgaas
2024-12-16 8:10 ` Mika Westerberg
2024-12-16 16:01 ` Ilpo Järvinen [this message]
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=5047c4a8-dfce-a081-e4fa-c6da731eb01d@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=gthiagarajan@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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