From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Brad Love <brad@nextdimension.cc>
Cc: linux-media@vger.kernel.org, markus.dobel@gmx.de,
alexdeucher@gmail.com, zzam@gentoo.org
Subject: Re: [PATCH v3] cx23885: only reset DMA on problematic CPUs
Date: Thu, 20 Dec 2018 11:43:25 -0200 [thread overview]
Message-ID: <20181220114325.39a0fcbc@coco.lan> (raw)
In-Reply-To: <1545239221-9393-1-git-send-email-brad@nextdimension.cc>
Em Wed, 19 Dec 2018 11:07:01 -0600
Brad Love <brad@nextdimension.cc> escreveu:
> It is reported that commit 95f408bbc4e4 ("media: cx23885: Ryzen DMA
> related RiSC engine stall fixes") caused regresssions with other CPUs.
>
> Ensure that the quirk will be applied only for the CPUs that
> are known to cause problems.
>
> A module option is added for explicit control of the behaviour.
>
> Fixes: 95f408bbc4e4 ("media: cx23885: Ryzen DMA related RiSC engine stall fixes")
>
> Signed-off-by: Brad Love <brad@nextdimension.cc>
Thanks!
Patch applied and sent upstream.
Regards,
Mauro
> ---
> Since v2:
> - Replaced sizeof with ARRAY_SIZE
> - Fixed column 80 checkpatch complaint
> Changes since v1:
> - Added module option for three way control
> - Removed '7' from pci id description, Ryzen 3 is the same id
>
> drivers/media/pci/cx23885/cx23885-core.c | 55 ++++++++++++++++++++++++++++++--
> drivers/media/pci/cx23885/cx23885.h | 2 ++
> 2 files changed, 55 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/pci/cx23885/cx23885-core.c b/drivers/media/pci/cx23885/cx23885-core.c
> index 39804d8..e2e3649 100644
> --- a/drivers/media/pci/cx23885/cx23885-core.c
> +++ b/drivers/media/pci/cx23885/cx23885-core.c
> @@ -23,6 +23,7 @@
> #include <linux/moduleparam.h>
> #include <linux/kmod.h>
> #include <linux/kernel.h>
> +#include <linux/pci.h>
> #include <linux/slab.h>
> #include <linux/interrupt.h>
> #include <linux/delay.h>
> @@ -41,6 +42,18 @@ MODULE_AUTHOR("Steven Toth <stoth@linuxtv.org>");
> MODULE_LICENSE("GPL");
> MODULE_VERSION(CX23885_VERSION);
>
> +/*
> + * Some platforms have been found to require periodic resetting of the DMA
> + * engine. Ryzen and XEON platforms are known to be affected. The symptom
> + * encountered is "mpeg risc op code error". Only Ryzen platforms employ
> + * this workaround if the option equals 1. The workaround can be explicitly
> + * disabled for all platforms by setting to 0, the workaround can be forced
> + * on for any platform by setting to 2.
> + */
> +static unsigned int dma_reset_workaround = 1;
> +module_param(dma_reset_workaround, int, 0644);
> +MODULE_PARM_DESC(dma_reset_workaround, "periodic RiSC dma engine reset; 0-force disable, 1-driver detect (default), 2-force enable");
> +
> static unsigned int debug;
> module_param(debug, int, 0644);
> MODULE_PARM_DESC(debug, "enable debug messages");
> @@ -603,8 +616,13 @@ static void cx23885_risc_disasm(struct cx23885_tsport *port,
>
> static void cx23885_clear_bridge_error(struct cx23885_dev *dev)
> {
> - uint32_t reg1_val = cx_read(TC_REQ); /* read-only */
> - uint32_t reg2_val = cx_read(TC_REQ_SET);
> + uint32_t reg1_val, reg2_val;
> +
> + if (!dev->need_dma_reset)
> + return;
> +
> + reg1_val = cx_read(TC_REQ); /* read-only */
> + reg2_val = cx_read(TC_REQ_SET);
>
> if (reg1_val && reg2_val) {
> cx_write(TC_REQ, reg1_val);
> @@ -2058,6 +2076,37 @@ void cx23885_gpio_enable(struct cx23885_dev *dev, u32 mask, int asoutput)
> /* TODO: 23-19 */
> }
>
> +static struct {
> + int vendor, dev;
> +} const broken_dev_id[] = {
> + /* According with
> + * https://openbenchmarking.org/system/1703021-RI-AMDZEN08075/Ryzen%207%201800X/lspci,
> + * 0x1451 is PCI ID for the IOMMU found on Ryzen
> + */
> + { PCI_VENDOR_ID_AMD, 0x1451 },
> +};
> +
> +static bool cx23885_does_need_dma_reset(void)
> +{
> + int i;
> + struct pci_dev *pdev = NULL;
> +
> + if (dma_reset_workaround == 0)
> + return false;
> + else if (dma_reset_workaround == 2)
> + return true;
> +
> + for (i = 0; i < ARRAY_SIZE(broken_dev_id); i++) {
> + pdev = pci_get_device(broken_dev_id[i].vendor,
> + broken_dev_id[i].dev, NULL);
> + if (pdev) {
> + pci_dev_put(pdev);
> + return true;
> + }
> + }
> + return false;
> +}
> +
> static int cx23885_initdev(struct pci_dev *pci_dev,
> const struct pci_device_id *pci_id)
> {
> @@ -2069,6 +2118,8 @@ static int cx23885_initdev(struct pci_dev *pci_dev,
> if (NULL == dev)
> return -ENOMEM;
>
> + dev->need_dma_reset = cx23885_does_need_dma_reset();
> +
> err = v4l2_device_register(&pci_dev->dev, &dev->v4l2_dev);
> if (err < 0)
> goto fail_free;
> diff --git a/drivers/media/pci/cx23885/cx23885.h b/drivers/media/pci/cx23885/cx23885.h
> index d54c7ee..cf965ef 100644
> --- a/drivers/media/pci/cx23885/cx23885.h
> +++ b/drivers/media/pci/cx23885/cx23885.h
> @@ -451,6 +451,8 @@ struct cx23885_dev {
> /* Analog raw audio */
> struct cx23885_audio_dev *audio_dev;
>
> + /* Does the system require periodic DMA resets? */
> + unsigned int need_dma_reset:1;
> };
>
> static inline struct cx23885_dev *to_cx23885(struct v4l2_device *v4l2_dev)
Thanks,
Mauro
next prev parent reply other threads:[~2018-12-20 13:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-21 13:45 [PATCH] Revert 95f408bb Ryzen DMA related RiSC engine stall fixes Markus Dobel
2018-12-05 11:07 ` Mauro Carvalho Chehab
2018-12-06 16:37 ` Brad Love
2018-12-06 17:18 ` Markus Dobel
2018-12-06 18:01 ` Mauro Carvalho Chehab
2018-12-06 18:36 ` Alex Deucher
2018-12-06 19:07 ` Mauro Carvalho Chehab
2018-12-06 19:32 ` Mauro Carvalho Chehab
2018-12-18 22:59 ` [PATCH v2] cx23885: only reset DMA on problematic CPUs Brad Love
2018-12-18 23:49 ` Alex Deucher
2018-12-19 17:26 ` Brad Love
2018-12-19 17:40 ` Brad Love
2018-12-19 11:08 ` Matthias Schwarzott
2018-12-19 17:09 ` Brad Love
2018-12-19 17:07 ` [PATCH v3] " Brad Love
2018-12-20 13:43 ` Mauro Carvalho Chehab [this message]
2018-12-16 10:37 ` [PATCH] Revert 95f408bb Ryzen DMA related RiSC engine stall fixes Markus Dobel
2018-12-16 14:23 ` Mauro Carvalho Chehab
2018-12-18 2:05 ` Alex Deucher
2018-12-18 6:32 ` Markus Dobel
2018-12-18 12:45 ` Mauro Carvalho Chehab
2018-12-18 23:11 ` Brad Love
2018-12-18 23:46 ` Alex Deucher
2018-12-19 0:05 ` Brad Love
2018-12-19 0:08 ` Brad Love
2018-12-19 19:07 ` Alex Deucher
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=20181220114325.39a0fcbc@coco.lan \
--to=mchehab@kernel.org \
--cc=alexdeucher@gmail.com \
--cc=brad@nextdimension.cc \
--cc=linux-media@vger.kernel.org \
--cc=markus.dobel@gmx.de \
--cc=zzam@gentoo.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).