From: James Hogan <jhogan@kernel.org>
To: Tokunori Ikegami <ikegami@allied-telesis.co.jp>
Cc: "Chris Packham" <chris.packham@alliedtelesis.co.nz>,
"Rafał Miłecki" <zajec5@gmail.com>,
linux-mips@linux-mips.org
Subject: Re: [PATCH v5 1/1] MIPS: BCM47XX: Enable MIPS32 74K Core ExternalSync for BCM47XX PCIe erratum
Date: Tue, 5 Jun 2018 16:45:30 +0100 [thread overview]
Message-ID: <20180605154529.GA19361@jamesdev> (raw)
In-Reply-To: <20180603140201.10593-2-ikegami@allied-telesis.co.jp>
[-- Attachment #1: Type: text/plain, Size: 1768 bytes --]
On Sun, Jun 03, 2018 at 11:02:01PM +0900, Tokunori Ikegami wrote:
> The erratum and workaround are described by BCM5300X-ES300-RDS.pdf as below.
>
> R10: PCIe Transactions Periodically Fail
>
> Description: The BCM5300X PCIe does not maintain transaction ordering.
> This may cause PCIe transaction failure.
> Fix Comment: Add a dummy PCIe configuration read after a PCIe
> configuration write to ensure PCIe configuration access
> ordering. Set ES bit of CP0 configu7 register to enable
> sync function so that the sync instruction is functional.
> Resolution: hndpci.c: extpci_write_config()
> hndmips.c: si_mips_init()
> mipsinc.h CONF7_ES
>
> This is fixed by the CFE MIPS bcmsi chipset driver also for BCM47XX.
> Also the dummy PCIe configuration read is already implemented in the Linux
> BCMA driver.
> Enable ExternalSync in Config7 when CONFIG_BCMA_DRIVER_PCI_HOSTMODE=y
> too so that the sync instruction is externalised.
>
> Signed-off-by: Tokunori Ikegami <ikegami@allied-telesis.co.jp>
> Reviewed-by: Paul Burton <paul.burton@mips.com>
> Acked-by: Hauke Mehrtens <hauke@hauke-m.de>
> Cc: Chris Packham <chris.packham@alliedtelesis.co.nz>
> Cc: Rafał Miłecki <zajec5@gmail.com>
> Cc: linux-mips@linux-mips.org
I presume this patch is ready to apply now (thanks for the reviews
folks).
How far back does this need backporting to stable branches?
It applies easily back to 3.14 I think (commit 3c06b12b046e ("MIPS:
BCM47XX: fix position of cpu_wait disabling")), but you mentioned other
fixes too. Have those been backported too, and if not is there any point
backporting this?
Thanks
James
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2018-06-05 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 14:02 [PATCH v5 0/1] MIPS: BCM47XX: Apply BCM5300X PCIe erratum workaround Tokunori Ikegami
2018-06-03 14:02 ` [PATCH v5 1/1] MIPS: BCM47XX: Enable MIPS32 74K Core ExternalSync for BCM47XX PCIe erratum Tokunori Ikegami
2018-06-05 15:45 ` James Hogan [this message]
2018-06-05 23:27 ` IKEGAMI Tokunori
2018-10-16 15:00 ` IKEGAMI Tokunori
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=20180605154529.GA19361@jamesdev \
--to=jhogan@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=ikegami@allied-telesis.co.jp \
--cc=linux-mips@linux-mips.org \
--cc=zajec5@gmail.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