From: Artem Lapkin <email2tema@gmail.com>
To: narmstrong@baylibre.com
Cc: yue.wang@Amlogic.com, khilman@baylibre.com,
lorenzo.pieralisi@arm.com, robh@kernel.org, kw@linux.com,
jbrunet@baylibre.com, christianshewitt@gmail.com,
martin.blumenstingl@googlemail.com, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
art@khadas.com, nick@khadas.com, gouwa@khadas.com
Subject: [PATCH] PCI: dwc: meson add quirk
Date: Fri, 18 Jun 2021 14:38:21 +0800 [thread overview]
Message-ID: <20210618063821.1383357-1-art@khadas.com> (raw)
Device set same 256 bytes maximum read request size equal MAX_READ_REQ_SIZE
was find some issue with HDMI scrambled picture and nvme devices
at intensive writing...
[ 4.798971] nvme 0000:01:00.0: fix MRRS from 512 to 256
This quirk setup same MRRS if we try solve this problem with
pci=pcie_bus_perf kernel command line param
Signed-off-by: Artem Lapkin <art@khadas.com>
---
drivers/pci/controller/dwc/pci-meson.c | 27 ++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/drivers/pci/controller/dwc/pci-meson.c b/drivers/pci/controller/dwc/pci-meson.c
index 686ded034f22..e2d40e5c2661 100644
--- a/drivers/pci/controller/dwc/pci-meson.c
+++ b/drivers/pci/controller/dwc/pci-meson.c
@@ -466,6 +466,33 @@ static int meson_pcie_probe(struct platform_device *pdev)
return ret;
}
+static void meson_pcie_quirk(struct pci_dev *dev)
+{
+ int mrrs;
+
+ /* no need quirk */
+ if (pcie_bus_config != PCIE_BUS_DEFAULT)
+ return;
+
+ /* no need for root bus */
+ if (pci_is_root_bus(dev->bus))
+ return;
+
+ mrrs = pcie_get_readrq(dev);
+
+ /*
+ * set same 256 bytes maximum read request size equal MAX_READ_REQ_SIZE
+ * was find some issue with HDMI scrambled picture and nvme devices
+ * at intensive writing...
+ */
+
+ if (mrrs != MAX_READ_REQ_SIZE) {
+ dev_info(&dev->dev, "fix MRRS from %d to %d\n", mrrs, MAX_READ_REQ_SIZE);
+ pcie_set_readrq(dev, MAX_READ_REQ_SIZE);
+ }
+}
+DECLARE_PCI_FIXUP_ENABLE(PCI_ANY_ID, PCI_ANY_ID, meson_pcie_quirk);
+
static const struct of_device_id meson_pcie_of_match[] = {
{
.compatible = "amlogic,axg-pcie",
--
2.25.1
next reply other threads:[~2021-06-18 6:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 6:38 Artem Lapkin [this message]
2021-06-18 12:11 ` [PATCH] PCI: dwc: meson add quirk Martin Blumenstingl
2021-06-18 14:30 ` Rob Herring
2021-06-18 15:08 ` Neil Armstrong
2021-06-19 3:01 ` Art Nikpal
2021-06-18 18:29 ` kernel test robot
2021-06-18 23:01 ` 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=20210618063821.1383357-1-art@khadas.com \
--to=email2tema@gmail.com \
--cc=art@khadas.com \
--cc=christianshewitt@gmail.com \
--cc=gouwa@khadas.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=kw@linux.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=nick@khadas.com \
--cc=robh@kernel.org \
--cc=yue.wang@Amlogic.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).