From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] PCI: fix for quirk_e100_interrupt()
Date: Mon, 17 Dec 2007 13:57:33 -0800 [thread overview]
Message-ID: <4766F0CD.30908@intel.com> (raw)
In-Reply-To: <20071218003927.A3045@jurassic.park.msu.ru>
Ivan Kokshaysky wrote:
> Check that the e100 is in the D0 power state. If it's not, it won't
> respond to MMIO accesses and we end up with master-abort machine
> checks on some platforms.
>
> Signed-off-by: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
what kind of platform actually is doing this? It almost seems like something is
wrong with that platform's BIOS and I wonder if this workaround should not be more
general (IOW is it not just e100 that is affected but other components as well?)
Auke
> ---
> drivers/pci/quirks.c | 14 +++++++++++++-
> 1 files changed, 13 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index 26cc4dc..c8b2b9d 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -1406,9 +1406,10 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_NETMOS, PCI_ANY_ID, quirk_netmos);
>
> static void __devinit quirk_e100_interrupt(struct pci_dev *dev)
> {
> - u16 command;
> + u16 command, pmcsr;
> u8 __iomem *csr;
> u8 cmd_hi;
> + int pm;
>
> switch (dev->device) {
> /* PCI IDs taken from drivers/net/e100.c */
> @@ -1442,6 +1443,17 @@ static void __devinit quirk_e100_interrupt(struct pci_dev *dev)
> if (!(command & PCI_COMMAND_MEMORY) || !pci_resource_start(dev, 0))
> return;
>
> + /*
> + * Check that the device is in the D0 power state. If it's not,
> + * there is no point to look any further.
> + */
> + pm = pci_find_capability(dev, PCI_CAP_ID_PM);
> + if (pm) {
> + pci_read_config_word(dev, pm + PCI_PM_CTRL, &pmcsr);
> + if ((pmcsr & PCI_PM_CTRL_STATE_MASK) != PCI_D0)
> + return;
> + }
> +
> /* Convert from PCI bus to resource space. */
> csr = ioremap(pci_resource_start(dev, 0), 8);
> if (!csr) {
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2007-12-17 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 21:39 Ivan Kokshaysky
2007-12-17 21:57 ` Kok, Auke [this message]
2007-12-17 22:48 ` Ivan Kokshaysky
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=4766F0CD.30908@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=gregkh@suse.de \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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
all inboxes | Powered by JetHome®