public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <Yinghai.Lu@Sun.COM>
To: akpm@linux-foundation.org, greg@kroah.com
Cc: LKML <linux-kernel@vger.kernel.org>,
	ak@suse.de, hpa@zytor.com, mingo@elte.hu, tglx@linutronix.de
Subject: [PATCH] x86_64: AMD Family 10h enable ext config in quirk
Date: Tue, 22 Jan 2008 01:10:19 -0800	[thread overview]
Message-ID: <200801220110.19571.yinghai.lu@sun.com> (raw)
In-Reply-To: <200801220245.m0M2jDAs000524@imap1.linux-foundation.org>

need to be applied after
gregkh-pci-pci-make-pci-extended-config-space-a-driver-opt-in.patch
x86_64-set-cfg_size-for-amd-family-10h-in-case-mmconfig-is-used.patch

[PATCH] x86_64: AMD Family 10h enable ext config in quirk

because of changes of
gregkh-pci-pci-make-pci-extended-config-space-a-driver-opt-in.patch

need to call pci_enable_ext_config to enable mmconfig before set right cfg_size
even MCFG is there

Signed-off-by: Yinghai Lu <yinghai.lu@sun.com>

--- a/arch/x86/pci/fixup.c	2008-01-22 00:54:38.000000000 -0800
+++ b/arch/x86/pci/fixup.c	2008-01-22 00:55:06.000000000 -0800
@@ -498,10 +498,12 @@
  * access it.  Maybe we don't have a way to generate extended config space
  * accesses.   So check it
  */
-static void fam10h_pci_cfg_space_size(struct pci_dev *dev)
+static void fam10h_enable_pci_ext_cfg(struct pci_dev *dev)
 {
+	pci_enable_ext_config(dev);
+	/* recheck cfg_size without pcie_pcix checking */
 	dev->cfg_size = pci_cfg_space_size_ext(dev, 0);
 }
 
 DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_AMD, PCI_ANY_ID,
-			 fam10h_pci_cfg_space_size);
+			 fam10h_enable_pci_ext_cfg);


           reply	other threads:[~2008-01-22  9:04 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200801220245.m0M2jDAs000524@imap1.linux-foundation.org>]

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=200801220110.19571.yinghai.lu@sun.com \
    --to=yinghai.lu@sun.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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