From: Tejun Heo <htejun@gmail.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: ahaas@airmail.net, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata_piix: fix pio/mwdma programming (for testing, don't apply)
Date: Sat, 03 Feb 2007 10:40:00 +0900 [thread overview]
Message-ID: <45C3E7F0.6000506@gmail.com> (raw)
In-Reply-To: <20070202174235.14b13f3e@localhost.localdomain>
Alan wrote:
>> * Control bits in the timing register wasn't cleared properly while
>> programming PIO mode.
>
> Yep and if the BIOS programmed the slave into DMA that might not be ideal.
How so? The bit will be programmed by set_dmamode() right after
set_piomode() is complete.
>> * MWDMA mode programming cleared the wrong part of control bits. I
>> think this can fix your problem.
>
> Your change does nothing here.
>
> 0x0F + 1 * 0xE1 = 0xF0
>
> It's just a construct to avoid the use of the ugly C "?" operator. The
> rest of the code uses ? so the change makes sense for style, but it
> doesn't appear to be a bug.
(0x0F + 0xE1 * ap->port_no)
1. when ap->port_no == 0
(0x0f + 0xe1 * 0) == 0x0f
2. when ap->port-no == 1
(0x0f + 0xe1 * 1) == 0xf0
(ap->port_no ? 0x0f : 0xf0)
1. when ap->port_no == 0
(0 ? 0x0f : 0xf0) == 0xf0
2. when ap->port_no == 1
(1 ? 0x0f : 0xf0) == 0x0f
See the difference? Smart one liners are dangerous. ?* is _much_
better than cryptic arithmetic.
>> * MWDMA mode programming cleared udma_mask even when the controller
>> doesn't support UDMA. This doesn't matter for your case.
>
> Or on the actual hardware.
I was trying to make it more consistent with pio counterpart. We can
remove if() from set_piomode too. Let's just keep things in sync
between stuff including ide piix driver.
--
tejun
next prev parent reply other threads:[~2007-02-03 1:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 15:18 [PATCH] ata_piix: fix pio/mwdma programming (for testing, don't apply) Tejun Heo
2007-02-02 15:34 ` Sergei Shtylyov
2007-02-02 16:38 ` Jeff Garzik
2007-02-02 16:57 ` Mark Lord
2007-02-02 18:34 ` Sergei Shtylyov
2007-02-02 16:41 ` Tejun Heo
2007-02-02 18:49 ` Alan
2007-02-02 19:04 ` Sergei Shtylyov
2007-02-02 17:42 ` Alan
2007-02-03 1:40 ` Tejun Heo [this message]
2007-02-03 20:04 ` Alan
2007-02-04 2:47 ` Tejun Heo
2007-02-02 21:14 ` Art Haas
2007-02-03 2:09 ` Tejun Heo
2007-02-03 14:35 ` Art Haas
2007-02-03 19:47 ` Mark Lord
2007-02-06 9:11 ` Tejun Heo
2007-02-06 16:33 ` Art Haas
2007-02-07 2:53 ` Tejun Heo
2007-02-07 19:35 ` Art Haas
2007-02-07 19:51 ` Mark Lord
2007-02-07 20:37 ` [PATCH] libata: clear TF before IDENTIFYing Tejun Heo
2007-02-08 14:56 ` Mark Lord
2007-02-13 19:38 ` Art Haas
2007-02-15 23:08 ` Jeff Garzik
2007-04-30 18:29 ` [PATCH] Fix pio/mwdma programming on ata_piix.c Art Haas
2007-05-01 3:02 ` Tejun Heo
2007-05-24 19:59 ` Art Haas
2007-05-24 20:55 ` Jeff Garzik
2007-05-24 21:03 ` Tejun Heo
2007-05-25 17:16 ` [PATCH] ata_piix: fix pio/mwdma programming Tejun Heo
2007-05-25 18:05 ` Alan Cox
2007-05-28 13:02 ` 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=45C3E7F0.6000506@gmail.com \
--to=htejun@gmail.com \
--cc=ahaas@airmail.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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).