From: Tejun Heo <htejun@gmail.com>
To: albertl@mail.com
Cc: Mark Lord <liml@rtr.ca>, Jeff Garzik <jeff@garzik.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux IDE <linux-ide@vger.kernel.org>,
Doug Maxey <dwm@enoyolf.org>
Subject: Re: [PATCH 8/10] libata: remove writing of tf->ctl from ata_tf_load()
Date: Thu, 05 Jul 2007 19:40:03 +0900 [thread overview]
Message-ID: <468CCA83.5020606@gmail.com> (raw)
In-Reply-To: <468C5ADD.9050700@tw.ibm.com>
Hello,
Albert Lee wrote:
>> At some point soon, I hope to piece together enough old hardware here
>> to reconnect my PCI-X sata_qstor card, and then fix the driver.
>>
>> It needs to have control over the nIEN bit, and currently that bit
>> is not behaving as it did way back in 2.6.11(?) when the driver was
>> first added.
>>
>> The qstor chip *requires* that nIEN be "1" during R/W commands.
>> Is there a nice way to accomplish that here?
>
> Does it mean that during the execution of PIO R/W commands, no interrupt
> will be generated? Currently the sata_qstor driver uses the
> ATA_FLAG_PIO_POLLING flag, does such polling pio fulfill the need of
> qstor? If not, maybe we could check what needs to be added and include
> them into consideration.
I'm not too familiar with how the qstor works but that sounds like
something which would fit very well into private ->qc_issue, no?
> Hmm, another consideration for qstor, irq_on/off do have their value for
> nIEN manipulation. The patchset maybe too far in scope. I will limit
> the scope of the patchset and leave irq_on/off alone (rather than
> integrate with thaw/freeze).
I like the idea of killing ->freeze/thaw. As you've just shown, they
provide almost the identical functionality as ->irq_off/on but just have
more cryptic names and with wide spread use of SATA, the meaning of NIEN
itself is diminishing, so I don't really see a point in keeping it for
the sake of controlling NIEN.
One way or the other, all we need is for the controller to not raise IRQ
during polling or when things look odd. If some controller and/or
device need specific handling of NIEN, it'll be actually easier to deal
with if we define ->irq_off as "whatever you do, just shut up".
So, I'm all for it.
--
tejun
next prev parent reply other threads:[~2007-07-05 10:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 8:38 [PATCH 0/10] libata: irq_on/off restructuring Albert Lee
2007-07-04 8:43 ` [PATCH 1/10] libata: remove irq_on from ata_bus_reset() and ata_std_postreset() Albert Lee
2007-07-05 10:18 ` Tejun Heo
2007-07-04 8:46 ` [PATCH 2/10] libata: add irq_off Albert Lee
2007-07-04 8:49 ` [PATCH 3/10] libata: implement ->irq_off in LLDDs Albert Lee
2007-07-04 8:52 ` [PATCH 4/10] libata: call irq_off from bmdma_freeze() Albert Lee
2007-07-04 8:57 ` [PATCH 5/10] libata: use freeze/thaw for polling Albert Lee
2007-07-04 8:59 ` [PATCH 6/10] libata: add freeze/thaw to old EH LLDDs Albert Lee
2007-07-04 9:01 ` [PATCH 7/10] libata: pdc_freeze() semantic change Albert Lee
2007-07-04 9:03 ` [PATCH 8/10] libata: remove writing of tf->ctl from ata_tf_load() Albert Lee
2007-07-04 19:09 ` Mark Lord
2007-07-05 2:43 ` Albert Lee
2007-07-05 10:40 ` Tejun Heo [this message]
2007-07-04 9:16 ` [PATCH 9/10] libata: Integrate freeze/thaw with irq_on/off Albert Lee
2007-07-04 9:29 ` [PATCH 10/10] libata: Integrate freeze/thaw with irq_on/off in LLDDs Albert Lee
2007-07-05 10:48 ` [PATCH 0/10] libata: irq_on/off restructuring Tejun Heo
2007-07-06 9:23 ` Albert Lee
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=468CCA83.5020606@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.com \
--cc=dwm@enoyolf.org \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--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).