linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vadim Lomovtsev <Vadim.Lomovtsev@caviumnetworks.com>
To: <tn@semihalf.com>, <David.Daney@cavium.com>,
	<bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	<Vadim.Lomovtsev@caviumnetworks.com>,
	<stemerkhanov@CAVIUMNETWORKS.onmicrosoft.com>
Subject: [PATCH] PCI: ACPI: Fix ThunderX PEM initialization
Date: Mon, 30 Jan 2017 08:25:52 -0800	[thread overview]
Message-ID: <1485793552-12614-1-git-send-email-Vadim.Lomovtsev@caviumnetworks.com> (raw)

This patch is to address PEM initialization issue
which causes network issues.

It is necessary to search for _HID:PNP0A08 while requesting
PEM resources via ACPI instead of "THRX0002".

Signed-off-by: Vadim Lomovtsev <Vadim.Lomovtsev@caviumnetworks.com>
---
 drivers/pci/host/pci-thunder-pem.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/pci/host/pci-thunder-pem.c b/drivers/pci/host/pci-thunder-pem.c
index af722eb..aec30b8 100644
--- a/drivers/pci/host/pci-thunder-pem.c
+++ b/drivers/pci/host/pci-thunder-pem.c
@@ -331,7 +331,7 @@ static int thunder_pem_acpi_init(struct pci_config_window *cfg)
 	if (!res_pem)
 		return -ENOMEM;
 
-	ret = acpi_get_rc_resources(dev, "THRX0002", root->segment, res_pem);
+	ret = acpi_get_rc_resources(dev, "PNP0A08", root->segment, res_pem);
 	if (ret) {
 		dev_err(dev, "can't get rc base address\n");
 		return ret;
-- 
2.4.11

             reply	other threads:[~2017-01-30 16:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 16:25 Vadim Lomovtsev [this message]
2017-01-30 17:39 ` [PATCH] PCI: ACPI: Fix ThunderX PEM initialization David Daney
2017-01-30 21:12 ` Bjorn Helgaas
2017-01-31 10:28   ` Vadim Lomovtsev
2017-01-31 14:25     ` Bjorn Helgaas
2017-01-31 14:57       ` Vadim Lomovtsev
2017-01-31 20:31         ` Bjorn Helgaas
2017-02-01 12:53           ` Vadim Lomovtsev
2017-02-01 15:18             ` Bjorn Helgaas
2017-02-01 15:34               ` Vadim Lomovtsev
2017-03-15 11:14               ` Jon Masters
2017-03-15 11:33                 ` Vadim Lomovtsev
2017-03-16 14:32                   ` Jon Masters
2017-03-16 16:25                     ` David Daney
2017-03-21 11:38                       ` Jon Masters
2017-03-21 13:47                         ` Bjorn Helgaas
2017-03-21 14:17                           ` Tomasz Nowicki
2017-03-21 14:56                             ` David Daney
2017-03-22 14:28                               ` Jon Masters
2017-03-22 14:48                                 ` Bjorn Helgaas
2017-03-22 16:25                                   ` Jon Masters
2017-03-22 16:34                                     ` Bjorn Helgaas
2017-03-23 22:14                                       ` Bjorn Helgaas
2017-03-23 22:16                                         ` Jon Masters
2017-03-21 17:45                             ` Bjorn Helgaas

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=1485793552-12614-1-git-send-email-Vadim.Lomovtsev@caviumnetworks.com \
    --to=vadim.lomovtsev@caviumnetworks.com \
    --cc=David.Daney@cavium.com \
    --cc=bhelgaas@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=stemerkhanov@CAVIUMNETWORKS.onmicrosoft.com \
    --cc=tn@semihalf.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;
as well as URLs for NNTP newsgroup(s).