From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Joerg Dorchain <joerg@dorchain.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: [Patch] Enable AHCI on certain ich chipsets
Date: Fri, 11 Feb 2011 23:50:06 +0300 [thread overview]
Message-ID: <4D55A0FE.30505@ru.mvista.com> (raw)
In-Reply-To: <20110211173620.GF5778@Redstar.dorchain.net>
Hello.
Joerg Dorchain wrote:
>>> 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?
Yes, certainly.
>> 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.
They are solving two different issues, as far as I understand, hence should
be in two different patches. One issue per patch is the basic rule.
> 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 @@
[...]
> +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)) {
Still spaces at the start of line... run your patches thru
scripts/checkpatch.pl -- it notices such style violations.
WBR, Sergei
next prev parent reply other threads:[~2011-02-11 20:51 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
2011-02-11 20:50 ` Sergei Shtylyov [this message]
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=4D55A0FE.30505@ru.mvista.com \
--to=sshtylyov@mvista.com \
--cc=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).