From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH #upstream] ahci: update PCS programming
Date: Fri, 23 Nov 2007 19:57:01 -0500 [thread overview]
Message-ID: <474776DD.4090201@garzik.org> (raw)
In-Reply-To: <20071119070344.GD30919@htj.mynetwork.cxm>
Tejun Heo wrote:
> For intel ones, ahci unconditionally OR'd 0xf to PCS. This isn't
> correct for the following cases.
>
> * ich6/7m's which only implement P0 and P2 (0xf works fine tho)
>
> * ich8/9's which have six ports and needs 0x3f to enable all ports
>
> This patch updates PCS programming such that...
>
> * port_map determined by ahci_save_initial_config() is OR'd instead of 0xf
>
> * PCS is updated only if necessary (there are turned off enable bits)
>
> port_map is determined from PORTS_IMPL PCI register which is
> implemented as write or write-once register. If the register isn't
> programmed, ahci automatically generates it from number of ports,
> which is good enough for PCS programming. ICH6/7M are probably the
> only ones where non-contiguous enable bits are necessary && PORTS_IMPL
> isn't programmed properly but they're proven to work reliably with 0xf
> anyway.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> ---
> As there hasn't been any report of brokeness due to this, I think this
> change can wait and get tested till the next merge cycle. The reason
> why this doesn't really break anything (yet) is that BIOS programs PCS
> correctly during boot and the value is preserved over suspend-to-ram,
> which is interesting considering the default value for PCS is zero.
> Maybe SMM code reprograms it while resuming?
>
> drivers/ata/ahci.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
applied
prev parent reply other threads:[~2007-11-24 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 7:03 [PATCH #upstream] ahci: update PCS programming Tejun Heo
2007-11-24 0:57 ` Jeff Garzik [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=474776DD.4090201@garzik.org \
--to=jeff@garzik.org \
--cc=htejun@gmail.com \
--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).