From: Steffen Liebergeld <steffen.liebergeld@kernkonzept.com>
To: linux-pci@vger.kernel.org
Cc: Bjorn Helgaas <bhelgaas@google.com>
Subject: [PATCH] PCI: quirks: Fix register location for UPDCR
Date: Tue, 17 Sep 2019 20:07:13 +0200 [thread overview]
Message-ID: <054ef65b-07de-7625-ebcb-f5ce64bc2726@kernkonzept.com> (raw)
According to documentation [0] the correct offset for the
Upstream Peer Decode Configuration Register (UPDCR) is 0x1014.
It was previously defined as 0x1114. This patch fixes it.
[0]
https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/4th-gen-core-family-mobile-i-o-datasheet.pdf
(page 325)
Signed-off-by: Steffen Liebergeld <steffen.liebergeld@kernkonzept.com>
---
drivers/pci/quirks.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
index 208aacf39329..7e184beb2aa4 100644
--- a/drivers/pci/quirks.c
+++ b/drivers/pci/quirks.c
@@ -4602,7 +4602,7 @@ int pci_dev_specific_acs_enabled(struct pci_dev
*dev, u16 acs_flags)
#define INTEL_BSPR_REG_BPPD (1 << 9)
/* Upstream Peer Decode Configuration Register */
-#define INTEL_UPDCR_REG 0x1114
+#define INTEL_UPDCR_REG 0x1014
/* 5:0 Peer Decode Enable bits */
#define INTEL_UPDCR_REG_MASK 0x3f
-- 2.11.0
next reply other threads:[~2019-09-17 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 18:07 Steffen Liebergeld [this message]
2019-09-18 10:42 ` [PATCH] PCI: quirks: Fix register location for UPDCR Andrew Murray
2019-09-18 12:02 ` Steffen Liebergeld
2019-09-18 12:09 ` Andrew Murray
2019-09-18 16:46 ` Alex Williamson
2019-09-18 22:04 ` Alex Williamson
2019-09-18 22:07 ` Raj, Ashok
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=054ef65b-07de-7625-ebcb-f5ce64bc2726@kernkonzept.com \
--to=steffen.liebergeld@kernkonzept.com \
--cc=bhelgaas@google.com \
--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;
as well as URLs for NNTP newsgroup(s).