From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: albertcc@tw.ibm.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/6] libata: separate out ata_dev_read_id()
Date: Tue, 28 Feb 2006 11:56:19 -0500 [thread overview]
Message-ID: <440480B3.8080609@gmail.com> (raw)
In-Reply-To: <43FA5845.1050800@pobox.com>
Jeff Garzik wrote:
> 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.
Hello, Jeff.
How is this going? Just checking as it's been more than a week.
--
tejun
next prev parent reply other threads:[~2006-02-28 2:54 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 ` [PATCH 1/6] libata: separate out ata_dev_read_id() Jeff Garzik
2006-02-28 16:56 ` Tejun Heo [this message]
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=440480B3.8080609@gmail.com \
--to=htejun@gmail.com \
--cc=albertcc@tw.ibm.com \
--cc=jgarzik@pobox.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.