From: poza@codeaurora.org
To: Ray Jui <ray.jui@broadcom.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <helgaas@kernel.org>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org,
linux-pci-owner@vger.kernel.org
Subject: Re: [PATCH INTERNAL 3/3] PCI: iproc: Disable MSI parsing in certain PAXC blocks
Date: Fri, 18 May 2018 14:53:41 +0530 [thread overview]
Message-ID: <ad41ea7f16414a83a2b3d7e6192bcf79@codeaurora.org> (raw)
In-Reply-To: <1526577692-21104-4-git-send-email-ray.jui@broadcom.com>
On 2018-05-17 22:51, Ray Jui wrote:
> The internal MSI parsing logic in certain revisions of PAXC root
> complexes does not work properly and can casue corruptions on the
> writes. They need to be disabled
>
> Signed-off-by: Ray Jui <ray.jui@broadcom.com>
> Reviewed-by: Scott Branden <scott.branden@broadcom.com>
> ---
> drivers/pci/host/pcie-iproc.c | 34 ++++++++++++++++++++++++++++++++--
> 1 file changed, 32 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/host/pcie-iproc.c
> b/drivers/pci/host/pcie-iproc.c
> index 3c76c5f..b906d80 100644
> --- a/drivers/pci/host/pcie-iproc.c
> +++ b/drivers/pci/host/pcie-iproc.c
> @@ -1144,10 +1144,22 @@ static int iproc_pcie_paxb_v2_msi_steer(struct
> iproc_pcie *pcie, u64 msi_addr)
> return ret;
> }
>
> -static void iproc_pcie_paxc_v2_msi_steer(struct iproc_pcie *pcie, u64
> msi_addr)
> +static void iproc_pcie_paxc_v2_msi_steer(struct iproc_pcie *pcie, u64
> msi_addr,
> + bool enable)
> {
> u32 val;
>
> + if (!enable) {
> + /*
> + * Disable PAXC MSI steering. All write transfers will be
> + * treated as non-MSI transfers
> + */
> + val = iproc_pcie_read_reg(pcie, IPROC_PCIE_MSI_EN_CFG);
> + val &= ~MSI_ENABLE_CFG;
> + iproc_pcie_write_reg(pcie, IPROC_PCIE_MSI_EN_CFG, val);
> + return;
> + }
> +
> /*
> * Program bits [43:13] of address of GITS_TRANSLATER register into
> * bits [30:0] of the MSI base address register. In fact, in all
> iProc
> @@ -1201,7 +1213,7 @@ static int iproc_pcie_msi_steer(struct iproc_pcie
> *pcie,
> return ret;
> break;
> case IPROC_PCIE_PAXC_V2:
> - iproc_pcie_paxc_v2_msi_steer(pcie, msi_addr);
> + iproc_pcie_paxc_v2_msi_steer(pcie, msi_addr, true);
Are you calling iproc_pcie_paxc_v2_msi_steer() anywhere else with
'false' ?
I see its getting called only from one place in current code
iproc_pcie_msi_steer().
> break;
> default:
> return -EINVAL;
> @@ -1427,6 +1439,24 @@ int iproc_pcie_remove(struct iproc_pcie *pcie)
> }
> EXPORT_SYMBOL(iproc_pcie_remove);
>
> +/*
> + * The MSI parsing logic in certain revisions of Broadcom PAXC based
> root
> + * complex does not work and needs to be disabled
> + */
> +static void quirk_paxc_disable_msi_parsing(struct pci_dev *pdev)
> +{
> + struct iproc_pcie *pcie = iproc_data(pdev->bus);
> +
> + if (pdev->hdr_type == PCI_HEADER_TYPE_BRIDGE)
> + iproc_pcie_paxc_v2_msi_steer(pcie, 0, false);
> +}
> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_BROADCOM, 0x16f0,
> + quirk_paxc_disable_msi_parsing);
> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_BROADCOM, 0xd802,
> + quirk_paxc_disable_msi_parsing);
> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_BROADCOM, 0xd804,
> + quirk_paxc_disable_msi_parsing);
> +
> MODULE_AUTHOR("Ray Jui <rjui@broadcom.com>");
> MODULE_DESCRIPTION("Broadcom iPROC PCIe common driver");
> MODULE_LICENSE("GPL v2");
next prev parent reply other threads:[~2018-05-18 9:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 17:21 [PATCH INTERNAL 0/3] Add Broadcom PAXC related quirks Ray Jui
2018-05-17 17:21 ` [PATCH INTERNAL 1/3] PCI: iproc: Activate PAXC bridge quirk for more devices Ray Jui
2018-05-17 17:21 ` [PATCH INTERNAL 2/3] PCI: iproc: Fix up corrupted PAXC root complex config registers Ray Jui
2018-05-18 9:19 ` poza
2018-05-30 17:27 ` Bjorn Helgaas
2018-05-30 17:43 ` Ray Jui
2018-06-12 0:18 ` Ray Jui
2018-05-17 17:21 ` [PATCH INTERNAL 3/3] PCI: iproc: Disable MSI parsing in certain PAXC blocks Ray Jui
2018-05-18 9:23 ` poza [this message]
2018-05-18 13:56 ` Lorenzo Pieralisi
2018-05-18 19:48 ` Ray Jui
2018-05-21 13:33 ` Lorenzo Pieralisi
2018-05-21 14:26 ` Robin Murphy
2018-05-22 16:48 ` Ray Jui
2018-05-22 16:52 ` Ray Jui
2018-07-04 15:13 ` Lorenzo Pieralisi
2018-07-04 15:44 ` Ray Jui
2018-05-17 17:23 ` [PATCH INTERNAL 0/3] Add Broadcom PAXC related quirks Ray Jui
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=ad41ea7f16414a83a2b3d7e6192bcf79@codeaurora.org \
--to=poza@codeaurora.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci-owner@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=ray.jui@broadcom.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).