From: Bjorn Helgaas <helgaas@kernel.org>
To: Steffen Liebergeld <steffen.liebergeld@kernkonzept.com>
Cc: linux-pci@vger.kernel.org, stable@vger.kernel.org,
Andrew Murray <andrew.murray@arm.com>,
Alex Williamson <alex.williamson@redhat.com>,
Ashok Raj <ashok.raj@intel.com>
Subject: Re: [PATCH v2] PCI: quirks: Fix register location for UPDCR
Date: Fri, 27 Sep 2019 07:54:57 -0500 [thread overview]
Message-ID: <20190927125457.GA34765@google.com> (raw)
In-Reply-To: <7a3505df-79ba-8a28-464c-88b83eefffa6@kernkonzept.com>
[+cc Andrew, Alex, Ashok]
Please cc people who commented on previous versions of a patch. I
added them for you here.
This is probably fine, but I'm waiting to see if Ashok gets a response
from the chipset folks. Hopefully he can ack this as a simple typo
fix.
On Wed, Sep 18, 2019 at 03:16:52PM +0200, Steffen Liebergeld wrote:
> According to documentation [0] the correct offset for the
> Upstream Peer Decode Configuration Register (UPDCR) is 0x1014.
> It was previously defined as 0x1114.
>
> Commit d99321b63b1f intends to enforce isolation between PCI
> devices allowing them to be put into separate IOMMU groups.
> Due to the wrong register offset the intended isolation was not
> fully enforced. This is fixed with this patch.
>
> Please note that I did not test this patch because I have
> no hardware that implements this register.
>
> [0]
> https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/4th-gen-core-family-mobile-i-o-datasheet.pdf
> (page 325)
>
> Fixes: d99321b63b1f ("PCI: Enable quirks for PCIe ACS on Intel PCH root ports")
> Reviewed-by: Andrew Murray <andrew.murray@arm.com>
> 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 prev parent reply other threads:[~2019-09-27 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 13:16 [PATCH v2] PCI: quirks: Fix register location for UPDCR Steffen Liebergeld
2019-09-27 12:54 ` Bjorn Helgaas [this message]
2019-09-27 15:26 ` Raj, Ashok
2019-09-30 22:05 ` 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=20190927125457.GA34765@google.com \
--to=helgaas@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=andrew.murray@arm.com \
--cc=ashok.raj@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=steffen.liebergeld@kernkonzept.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).