From: Don Dutile <ddutile@redhat.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "Hao, Xudong" <xudong.hao@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Matthew Wilcox <matthew@wil.cx>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: [PATCH v6] Quirk for IVB graphics FLR errata
Date: Mon, 23 Apr 2012 17:44:50 -0400 [thread overview]
Message-ID: <4F95CD52.1030409@redhat.com> (raw)
In-Reply-To: <CAErSpo4Dm45uRsvdzSAfrvGNPPA_7QqvC_Se-JxpJErsasoTKw@mail.gmail.com>
On 04/23/2012 05:07 PM, Bjorn Helgaas wrote:
> On Fri, Apr 20, 2012 at 1:08 AM, Hao, Xudong<xudong.hao@intel.com> wrote:
>> Hi, Bjorn
>>
>> Do you have any other comments for this patch?
>
> What happened with the idea of adding a .reset hook in struct
> pci_driver? It would be better if all the device-related code could
> live in the device-specific driver, rather than having to put it in a
> quirk. Everybody pays the cost of a quirk, even on systems that don't
> include this device.
>
> Bjorn
>
Well, its possible to have a bad device that needs an FLR quirk w/o
its driver being loaded...
e.g., a device assigned to a KVM guest ... no driver in the host,
but will FLR the device when removed from the guest.
I basically agree with your point, just thought of this configuration/option.
>>> -----Original Message-----
>>> From: Hao, Xudong
>>> Sent: Monday, April 16, 2012 9:40 AM
>>> To: 'Bjorn Helgaas'
>>> Cc: 'linux-pci@vger.kernel.org'; 'Don Dutile'; 'Matthew Wilcox'
>>> Subject: [PATCH v6] Quirk for IVB graphics FLR errata
>>>
>>> For IvyBridge Mobile platform, a system hang may occur if a FLR(Function Level
>>> Reset) is asserted to internal graphics.
>>>
>>> This quirk patch is workaround for the IVB FLR errata issue.
>>> We are disabling the FLR reset handshake between the PCH and CPU display,
>>> then manually powering down the panel power sequencing and resetting the
>>> PCH display.
>>>
>>> Changes from v5:
>>> - clean up patch with Matthew's comments.
>>>
>>> Signed-off-by: Xudong Hao<xudong.hao@intel.com>
>>> Signed-off-by: Kay, Allen M<allen.m.kay@intel.com>
>>> Signed-off-by: Matthew Wilcox<willy@linux.intel.com>
>>> ---
>>> drivers/pci/quirks.c | 48
>>> ++++++++++++++++++++++++++++++++++++++++++++++++
>>> 1 files changed, 48 insertions(+), 0 deletions(-)
>>>
>>> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c index 4bf7102..213cad9
>>> 100644
>>> --- a/drivers/pci/quirks.c
>>> +++ b/drivers/pci/quirks.c
>>> @@ -29,6 +29,7 @@
>>> #include<linux/sched.h>
>>> #include<linux/ktime.h>
>>> #include<asm/dma.h> /* isa_dma_bridge_buggy */
>>> +#include<asm/io.h>
>>> #include "pci.h"
>>>
>>> /*
>>> @@ -3085,11 +3086,58 @@ static int reset_intel_82599_sfp_virtfn(struct
>>> pci_dev *dev, int probe)
>>> return 0;
>>> }
>>>
>>> +#include "../gpu/drm/i915/i915_reg.h"
>>> +#define MSG_CTL 0x45010
>>> +#define IGD_OPERATION_TIMEOUT 10000 /* set timeout 10 seconds */
>>> +
>>> +static int reset_ivb_igd(struct pci_dev *dev, int probe) {
>>> + void __iomem *mmio_base;
>>> + unsigned long timeout;
>>> + u32 val;
>>> +
>>> + if (probe)
>>> + return 0;
>>> +
>>> + mmio_base = ioremap_nocache(pci_resource_start(dev, 0),
>>> + pci_resource_len(dev, 0));
>>> + if (!mmio_base)
>>> + return -ENOMEM;
>>> +
>>> + /* Work Around */
>>> + writel(0x00000002, mmio_base + MSG_CTL);
>>> + /* Clobbering SOUTH_CHICKEN2 register is fine only if the next
>>> + * driver loaded sets the right bits. However, this's a reset and
>>> + * the bits have been set by i915 previously, so we clobber
>>> + * SOUTH_CHICKEN2 register directly here.
>>> + */
>>> + writel(0x00000005, mmio_base + SOUTH_CHICKEN2);
>>> + val = readl(mmio_base + PCH_PP_CONTROL)& 0xfffffffe;
>>> + writel(val, mmio_base + PCH_PP_CONTROL);
>>> + timeout = jiffies + msecs_to_jiffies(IGD_OPERATION_TIMEOUT);
>>> + while (time_before(jiffies, timeout)) {
>>> + val = readl(mmio_base + PCH_PP_STATUS);
>>> + if ((val& 0xB0000000) == 0)
>>> + break;
>>> + cpu_relax();
>>> + }
>>> + writel(0x00000002, mmio_base + 0xd0100);
>>> +
>>> + iounmap(pci_resource_start(dev, 0));
>>> + return 0;
>>> +}
>>> +
>>> #define PCI_DEVICE_ID_INTEL_82599_SFP_VF 0x10ed
>>> +#define PCI_DEVICE_ID_INTEL_IVB_M_VGA 0x0156
>>> +#define PCI_DEVICE_ID_INTEL_IVB_M2_VGA 0x0166
>>>
>>> static const struct pci_dev_reset_methods pci_dev_reset_methods[] = {
>>> { PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82599_SFP_VF,
>>> reset_intel_82599_sfp_virtfn },
>>> + { PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_IVB_M_VGA,
>>> + reset_ivb_igd },
>>> + { PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_IVB_M2_VGA,
>>> + reset_ivb_igd },
>>> { PCI_VENDOR_ID_INTEL, PCI_ANY_ID,
>>> reset_intel_generic_dev },
>>> { 0 }
>>> --
>>> 1.6.0.rc1
>>
next prev parent reply other threads:[~2012-04-23 21:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 7:08 [PATCH v6] Quirk for IVB graphics FLR errata Hao, Xudong
2012-04-23 21:07 ` Bjorn Helgaas
2012-04-23 21:44 ` Don Dutile [this message]
2012-04-24 3:06 ` Hao, Xudong
2012-04-25 17:51 ` Bjorn Helgaas
2012-04-26 3:19 ` Hao, Xudong
2012-04-26 23:14 ` Bjorn Helgaas
2012-04-27 1:26 ` Hao, Xudong
2012-04-27 17:41 ` Bjorn Helgaas
2012-05-02 0:37 ` Hao, Xudong
2012-05-02 16:03 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2012-04-16 1:39 Hao, Xudong
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=4F95CD52.1030409@redhat.com \
--to=ddutile@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=xiantao.zhang@intel.com \
--cc=xudong.hao@intel.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).