From: Mark Lord <liml@rtr.ca>
To: albertl@mail.com
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jeff@garzik.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: libata passthru: support PIO multi commands
Date: Wed, 13 Jun 2007 14:40:45 -0400 [thread overview]
Message-ID: <46703A2D.6000207@rtr.ca> (raw)
In-Reply-To: <466F5D11.7000404@tw.ibm.com>
Albert Lee wrote:
> ..
> It looks like the ATA passthru commands contain more information than
> what libata needs to execute a command.
>
> e.g. protocol number:
> libata could possibly infer the protocol from the command opcode.
>
> e.g. multi_count:
> libata caches dev->multi_count. Passing multi_count along with
> each passthru command looks useless for libata.
>
> e.g. t_dir:
> libata could possible infer the direction from the command opcode
> or from the protocol number (e.g. 4: PIO_IN / 5: PIO_OUT).
I wonder if the *intent* of the specification was that the low-level driver
should perform whatever setup is necessary to issue the command as given.
So if the command specifies a multcount of 8, then the LLD should issue the
appropriate initialization commands to use a multcount of 8, and then issue
the given R/W MULT command, and then perhaps reset the multcount back to
what it was normally (beforehand) ?
Ditto for the others.
I am *not* proposing that we actually do it this way,
but rather just suggesting a possible rationale.
What does the SAT spec say? Any further hints as to the intent?
Cheers
next prev parent reply other threads:[~2007-06-13 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200706112200.l5BM0qFn005767@hera.kernel.org>
[not found] ` <20070611233917.4bd8c6d7@the-village.bc.nu>
[not found] ` <466DE438.70108@garzik.org>
[not found] ` <20070612111621.10074408@the-village.bc.nu>
2007-06-12 15:18 ` libata passthru: support PIO multi commands Jeff Garzik
2007-06-12 16:05 ` Alan Cox
2007-06-13 2:57 ` Albert Lee
2007-06-13 18:40 ` Mark Lord [this message]
2007-06-13 18:55 ` Sergei Shtylyov
2007-06-13 18:55 ` 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=46703A2D.6000207@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).