From: Joerg Dorchain <joerg@dorchain.net>
To: linux-ide@vger.kernel.org
Subject: Re: [Patch] Enable AHCI on certain ich chipsets
Date: Fri, 11 Feb 2011 18:36:20 +0100 [thread overview]
Message-ID: <20110211173620.GF5778@Redstar.dorchain.net> (raw)
In-Reply-To: <4D552B18.8030808@ru.mvista.com>
[-- Attachment #1: Type: text/plain, Size: 4497 bytes --]
On Fri, Feb 11, 2011 at 03:27:04PM +0300, Sergei Shtylyov wrote:
> >[Several formal corrections]
>
> >Should be addressed by this try.
Thank you for bearing with me. Next try is below.
>
> >During resume from suspend to ram, the kernel pci layer restores
> >the registers for the SATA controller once, then says okay, and
> >sets dev->state_saved = false. However, since the restore goes
> >from highest address (the BARs [base address registers]) to
> >lowest register, some of the higher registers are set as RO
> >because according to the lower registers controller is in PIIX
> >mode. This patch introduces a workaround for
> >this problem, hacking around the PCI API by setting pdev->state_saved = true
> >before we do the restore.
>
>
>
> This only describes drivers/ata/ahci.c change.
Well, the functionality of the patch to quirks.c is described in
the comments on the top of it. Should that be repeated?
> And looks like it
> should be in a patch of its own...
I need both parts in order to use the AHCI driver and having
suspend/resume work, hence they are together.
Bye,
Joerg
Signed-Off-By: joerg Dorchain<joerg@dorchain.net>
--- linux/drivers/pci/quirks.c.orig 2011-02-04 18:29:03.000000000 +0100
+++ linux/drivers/pci/quirks.c 2011-02-11 13:44:12.000000000 +0100
@@ -2684,6 +2684,74 @@
DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_HINT, 0x0020, quirk_hotplug_bridge);
/*
+ * Force ICH7/8/9 into AHCI mode. This is needed because some
+ * BIOSes do not make AHCI-mode operation available to the user.
+ * As the Intel documentation states that the OS should not carry
+ * out the operation - the user must force this on the kernel
+ * commandline using quirk_ich_force_ahci
+ *
+ * As this quirk gets called whilst the PCI subsystem is
+ * walking the PCI bus, we declare this quirk against the LPC
+ * (device 00:1f.0), so that we can frob 00:1f.2 before the PCI
+ * code has scanned it.
+ * Note: the pci id might change due to this (e.g. from 27c4 to 27c5)
+ *
+ */
+
+static bool ich_force_ahci_mode = false;
+
+static int __init ich789_force_ahci_mode_setup(char *str)
+{
+ ich_force_ahci_mode = true;
+ return 0;
+}
+early_param("quirk_ich_force_ahci", ich789_force_ahci_mode_setup);
+
+static void ich789_force_ahci_mode(struct pci_dev *pdev)
+{
+ u8 amrval;
+ u8 sclkgc;
+ const int ich89_address_map_reg = 0x90;
+ const int ich89_sata_clock_gen_config_reg = 0x9c;
+
+ if (!ich_force_ahci_mode)
+ return;
+
+ /* ICH8 datasheet section 12.1.33 */
+ if (!pci_bus_read_config_byte(pdev->bus, PCI_DEVFN(PCI_SLOT(pdev->devfn), 2),
+ ich89_address_map_reg, &amrval)) {
+
+ if (amrval & (BIT(6) | BIT(7))) {
+ dev_printk(KERN_DEBUG, &pdev->dev,
+ "ICH7/8/9 SATA controller not in IDE mode. Not modifying.\n");
+ return;
+ }
+ if (amrval & (BIT(0) | BIT(1)))
+ dev_printk(KERN_DEBUG, &pdev->dev,
+ "ICH7/8/9 in SATA/PATA combined mode. Untested.\n");
+ /* AHCI mode */
+ amrval |= BIT(6);
+ amrval &= ~BIT(7);
+ pci_bus_read_config_byte(pdev->bus, PCI_DEVFN(PCI_SLOT(pdev->devfn), 2),
+ ich89_sata_clock_gen_config_reg, &sclkgc);
+ dev_printk(KERN_DEBUG, &pdev->dev, "sclkgc is %#0x\n", sclkgc);
+ pci_bus_write_config_byte(pdev->bus, PCI_DEVFN(PCI_SLOT(pdev->devfn), 2),
+ ich89_address_map_reg, amrval);
+ dev_printk(KERN_DEBUG, &pdev->dev, "Forced ICH7/8/9 mode PIIX->AHCI\n");
+ }
+}
+/* ICH7 */
+DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x27b9, ich789_force_ahci_mode);
+/* ICH8 */
+DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ICH8_0, ich789_force_ahci_mode);
+/* ICH9R LPC */
+DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x2916, ich789_force_ahci_mode);
+/* ICH9M LPC */
+DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x2917, ich789_force_ahci_mode);
+/* ICH9M-E LPC */
+DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x2919, ich789_force_ahci_mode);
+
+/*
* This is a quirk for the Ricoh MMC controller found as a part of
* some mulifunction chips.
--- linux/drivers/ata/ahci.c.orig 2011-02-04 18:13:33.000000000 +0100
+++ linux/drivers/ata/ahci.c 2011-02-11 13:45:22.000000000 +0100
@@ -640,6 +640,11 @@
struct ata_host *host = dev_get_drvdata(&pdev->dev);
int rc;
+ /*
+ * override check to see if PCI config space is already
+ * restored in pci_restore_state
+ */
+ pdev->state_saved = true;
rc = ata_pci_device_do_resume(pdev);
if (rc)
return rc;
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 267 bytes --]
next prev parent reply other threads:[~2011-02-11 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 11:59 [Patch] Enable AHCI on certain ich chipsets Joerg Dorchain
2011-02-09 12:56 ` Sergei Shtylyov
2011-02-10 19:23 ` Joerg Dorchain
2011-02-11 12:27 ` Sergei Shtylyov
2011-02-11 17:36 ` Joerg Dorchain [this message]
2011-02-11 20:50 ` Sergei Shtylyov
2011-02-12 6:27 ` Joerg Dorchain
2011-02-12 12:09 ` Bartlomiej Zolnierkiewicz
2011-02-14 7:41 ` Joerg Dorchain
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=20110211173620.GF5778@Redstar.dorchain.net \
--to=joerg@dorchain.net \
--cc=linux-ide@vger.kernel.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).