linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Dorchain <joerg@dorchain.net>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Sergei Shtylyov <sshtylyov@mvista.com>, linux-ide@vger.kernel.org
Subject: Re: [Patch] Enable AHCI on certain ich chipsets
Date: Mon, 14 Feb 2011 08:41:36 +0100	[thread overview]
Message-ID: <20110214074136.GH5778@Redstar.dorchain.net> (raw)
In-Reply-To: <AANLkTimb3+yk2O2gFVi5_FB-rmf78h-ZRE6a7_KR_dkc@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]

On Sat, Feb 12, 2011 at 01:09:37PM +0100, Bartlomiej Zolnierkiewicz wrote:
> 
> > The second part just makes sure that the config space change is
> > kept after a resume. Otherwise it comes up as a different PCI
> > id, the AHCI driver finds nothing to work with, the harddisk is
> > gone after resume, not good.
> 
> Shouldn't therefore the quirk be applied also during resume (by
> additional use of DECLARE_PCI_FIXUP_RESUME_EARLY in addition to
> existing DECLARE_PCI_FIXUP_EARLY one)?

I have considered that, but just not touching the config space
for having the desired effect seems easier to me.

Actually this is a reason why I am looking for feedback from
other people with the chipsets listed in the patch. Is it only my
system for keeps pci config during suspend/resume or does it work
for others, too?
On the other hand, if I understand Sergei correctly, it could be
a more general effect with it, which is why I'd also appreciated
some review from an architectural perspective.

If not, DECLARE_PCI_FIXUP_RESUME_EARLY is fine with me. My main
objective is to use the ahci driver, and I hope others like to do
so as well.

Bye,

Joerg

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 267 bytes --]

      reply	other threads:[~2011-02-14  7:41 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
2011-02-12  6:27           ` Joerg Dorchain
2011-02-12 12:09             ` Bartlomiej Zolnierkiewicz
2011-02-14  7:41               ` Joerg Dorchain [this message]

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=20110214074136.GH5778@Redstar.dorchain.net \
    --to=joerg@dorchain.net \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=sshtylyov@mvista.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).