From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: albertcc@tw.ibm.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/6] libata: separate out ata_dev_read_id()
Date: Mon, 20 Feb 2006 19:01:09 -0500 [thread overview]
Message-ID: <43FA5845.1050800@pobox.com> (raw)
In-Reply-To: <11404555313091-git-send-email-htejun@gmail.com>
Tejun Heo wrote:
> Separate out ata_dev_read_id() from ata_dev_identify(). This is the
> first half of splitting ata_dev_identify(). ata_dev_read_id() will
> also be used for revalidation. This patch does not make any behavior
> change.
>
> ata_dev_read_id() doesn't modify any of libata-internal data
> structures. It simply reads IDENTIFY page and returns error code on
> failure. INIT_DEV_PARAMS and EDD wrong class code are also handled by
> this function.
>
> Re-reading IDENTIFY after INIT_DEV_PARAMS is performed by jumping to
> retry: instead of calling ata_dev_reread_id(). This is done because
> 1. there's retry label anyway 2. ata_dev_reread_id() cannot be used
> anywhere else so there's no reason to keep it.
>
> This function is probably the place to set transfer mode to PIO0
> before IDENTIFY. However, reset -> identify -> init_dev_params order
> should be kept for pre-ATA4 devices so we cannot set transfer mode
> before IDENTIFY for them. How do we know if a device is post-ATA4
> before IDENTIFY?
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
applied 1-2, will get to the rest a bit later, after other work and some
testing of this work.
Jeff
next parent reply other threads:[~2006-02-21 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11404555313091-git-send-email-htejun@gmail.com>
2006-02-21 0:01 ` Jeff Garzik [this message]
2006-02-28 16:56 ` [PATCH 1/6] libata: separate out ata_dev_read_id() Tejun Heo
2006-02-28 3:15 ` Jeff Garzik
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=43FA5845.1050800@pobox.com \
--to=jgarzik@pobox.com \
--cc=albertcc@tw.ibm.com \
--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).