From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] ahci: separate port number determination from host initialization
Date: Fri, 09 Mar 2007 09:07:05 -0500 [thread overview]
Message-ID: <45F16A09.3040904@garzik.org> (raw)
In-Reply-To: <20070309104709.GF32687@htj.dyndns.org>
Tejun Heo wrote:
> ahci used to reset controller then fetch cap value to be used for
> configuration. On some controller this misses some cap bits and ahci
> got modified to maintain cap and ports_impl values over reset, so
> there is no reason to reset the controller before fetching those
> register values.
>
> Separate out ahci_determine_nr_ports() from ahci_host_init() and it
> before starting to initialize probe_ent. This makes ahci's init_one
> more consistent to other drivers and eases conversion to new init
> model.
>
> Also, the initialization is more robust as it doesn't depend on
> ports_impl being writeable when HONOR_PI is set but the register
> itself is zero.
>
> Tested on ICH7 (no ports_impl) and 8 AHCI (w/ ports_impl).
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
I would rather make things explicit by creating an
ahci_read_bios_config() function, and associated data structures, which
reads all register values that are not preserved across reset. This
would also be the code point at which we would handle a
no-BIOS/uninitialized configuration.
After such a change, this patch will look smaller and nicer.
Jeff
prev parent reply other threads:[~2007-03-09 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 10:47 [PATCH] ahci: separate port number determination from host initialization Tejun Heo
2007-03-09 14:07 ` 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=45F16A09.3040904@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.