From: Brett Russ <russb@emc.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, ric@emc.com
Subject: Re: [PATCH] Re: AHCI: support for tf_read (RFC)
Date: Mon, 07 Mar 2005 11:43:48 -0500 [thread overview]
Message-ID: <422C84C4.8090103@emc.com> (raw)
In-Reply-To: <421FB272.4030502@pobox.com>
Jeff Garzik wrote:
> Brett Russ wrote:
>
>> I coded this because ata_pass_thru_cc() (in the dev branch) and other
>> functions call tf_read() which is supported for most except ahci.
>> I've been unable to test because I'm leaving on vacation and am in a
>> last minute rush but wanted to get this out there for comments.
>>
>> Signed-off-by: Brett Russ <russb@emc.com>
>
>
> I checked the attached patch into a local repository, but haven't yet
> merged it into libata-dev-2.6, or tested it.
The reason I didn't just use ata_tf_from_fis() was because I didn't
think it was valid to overload tf->command with status and tf->feature
with error. It was commented as a host->device FIS translation, where
those fields would line up with the properly named tf fields.
As long as the overload is fine then this is certainly simpler than my
patch.
BR
<snip>
> +static void ahci_tf_read(struct ata_port *ap, struct ata_taskfile *tf)
> +{
> + struct ahci_port_priv *pp = ap->private_data;
> + u8 *d2h_fis = pp->rx_fis + RX_FIS_D2H_REG;
> +
> + ata_tf_from_fis(d2h_fis, tf);
> }
>
> static void ahci_fill_sg(struct ata_queued_cmd *qc)
next prev parent reply other threads:[~2005-03-07 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 23:24 [PATCH libata-2.6] AHCI: support for tf_read (RFC) Brett Russ
2005-02-24 23:33 ` Jeff Garzik
2005-02-25 23:19 ` [PATCH] " Jeff Garzik
2005-03-07 16:43 ` Brett Russ [this message]
2005-03-10 16:50 ` Brett Russ
2005-03-10 18:32 ` 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=422C84C4.8090103@emc.com \
--to=russb@emc.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=ric@emc.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).